Grok integration
Grok attribution, no setup needed, from AI referral to closed deal
Your analytics cannot tell a Grok referral from direct traffic. LeadJourney can, and follows each one through to leads, deals and revenue.
- Reported as its own source
- No setup required
- 95%+ accuracy, first-party
Rated by the teams who connected their stack
How the data moves
GrokWhere the visitor comes from- x.com
- grok.com
AI search tracking
LeadJourneyThe tracking script recognises the referrer on arrival, no setup- Own traffic source
- Leads
- Pipeline
- Won revenue
Grok referrals used to land in direct. The tracking script separates them on arrival, so your reports show how many leads and how much revenue AI search actually produces.
Trusted by 100+ lead generation businesses, agencies and freelancers
The gap
Grok cites your site. Your analytics files the visit under X and direct.
Grok answers inside X as well as at grok.com, and links to its sources. GA4 sorts those clicks into organic social, referral and direct, so your social team gets the credit.
Grok traffic in your analytics today
A social click, a referral and a blank, none of them named Grok
- A click from a Grok answer inside X carries x.com as the referrer, and GA4 files x.com under organic social, next to every click on a post.
- A click from grok.com is a referral in GA4, one domain among every other site that ever linked to you.
- A click from the Grok app on a phone usually arrives with no referrer at all, and no referrer means direct.
- GA4 records the visit in the browser, so an ad blocker or a declined cookie banner removes the session before Grok gets any credit.
- GA4 counts sessions and key events, so the trail ends at the form. Whether the lead qualified or the deal closed is a question for the CRM.
- Grok reads X posts as well as the web, so it cites you to people already talking about your category, and that audience is being reported as your social team's work.
- A custom channel group can gather grok.com, but a regex on the source cannot split a Grok answer from a post when both arrive as x.com.
Grok with LeadJourney
One source, told apart from X on arrival, followed to revenue
- The tracking script recognises a Grok referral server-side as the page loads, from grok.com and from a Grok answer inside X, and reports it as one source called Grok.
- Grok is separated from your organic X posts and from direct, so the social number gets honest at the same time.
- The visit is recorded server-side and first-party, at 95%+ accuracy, past ad blockers and declined banners.
- The visit is stitched to the lead at form submit, and the journey follows the lead through your CRM, stage by stage, to closed won.
- A Grok click in the X app on a phone and a booking from a laptop a week later are one journey once the reader identifies, not two users.
- Grok sits in the same multi-touch model as Google Ads, Meta, LinkedIn, organic and the other AI engines, so you learn whether it opens deals or closes them.
- Nothing to configure. The source is on from the first page view, with no channel group, no regex and no filter to maintain.
How it works
Grok attribution in two steps: tell the visit apart from X, then follow it to revenue
Both run on their own once the script is on the site: the visit is read server-side, then the won revenue behind a Grok citation.
1 Grok traffic tracking from the first page view
The visit is recognised on the server, before it can be filed as a social click.
A reader asks Grok a question, in the Grok tab on X or at grok.com, Grok searches the web and X and cites your page, and the reader taps through.
The tracking script reads the referrer server-side on arrival and files the visit under Grok, not under X organic social and not under direct.
The landing page, the pages read and every later visit join one anonymous first-party journey, so the same reader returning on a laptop is not a new user.
When the reader fills in a form or books a call, the journey is stitched to the lead, and Grok is on record as the first touch.
2 Follow the lead through your CRM and compare Grok with every other channel
A tap in the X app was free. The question is what it turned into.
With a two-way CRM connected, the journey is written onto the record: Grok as the source, the page it cited, and the touches that followed.
Your CRM reports the outcome as it happens: qualified, opportunity, deal value and closed won, read back into the journey as the stages change.
Grok appears in the traffic channel report as its own line, next to X organic: visits, leads, pipeline and won revenue, so the two can finally be compared.
The multi-touch models weigh Grok against Google Ads, Meta, LinkedIn, organic and the other AI engines, so you learn whether it starts deals, finishes them, or both.
Your CRM closes the loop
Your CRM shows what the Grok visit was worth
Grok has no ad account, no click ID and no conversions API. A tap on a citation costs nothing and reports nothing, so LeadJourney follows every Grok lead into the CRM and reads the outcome back out.
- HubSpotTwo-way sync
Contacts and Deals, with stage, amount and close date, read as they change.
- SalesforceTwo-way sync
Leads, Contacts and Opportunities, including custom objects where your deals live elsewhere.
- PipedriveTwo-way sync
Persons and Deals, with pipeline stage and won value.
- AttioTwo-way sync
People, Companies and Deals from your workspace.
CloseTwo-way syncLeads and Opportunities, with status changes as they happen.
Grok and X, side by side, in revenue
The Grok line and the X organic line each carry won revenue from the CRM, so you can see whether the AI answer or the timeline is doing the work.
Lead quality by engine
You see how many Grok leads qualify, how many stall, and how that compares with ChatGPT, Perplexity and Google, before deciding whether the X audience is worth writing for.
No window to expire
A Grok tap in January that becomes a deal in April still credits Grok. The journey runs until the deal closes, not for a lookback period.
Reporting
The questions GA4 cannot answer about Grok
Each of these is a report filtered to the Grok source, not a channel group your social team argues with. The Grok line simply exists now, apart from X, and it runs all the way to revenue.
How many leads did Grok send us last month, and how many of them qualified?
How much won revenue started with a Grok answer this quarter?
How much of what we reported as X traffic was Grok rather than our own posts?
Which of our pages does Grok cite, and which of those turn readers into leads?
Does Grok send us the same kind of buyer as ChatGPT and Perplexity, or a different one?
Do Grok leads close faster or slower than Google organic leads, and at what deal size?
LeadJourney and Google Analytics 4
Where GA4 ends and LeadJourney starts
GA4 knows x.com as a social network, which was right until Grok started answering questions inside it.
| Capability |  Google Analytics 4 | With LeadJourney |
|---|---|---|
| Grok attribution | Google Analytics 4No Grok source. A Grok answer inside X is x.com organic social, grok.com is a referral, and the Grok app is direct. | With LeadJourneyOne source called Grok, recognised server-side on arrival, separated from your X posts and from direct. |
| Where the visit is recorded | Google Analytics 4In the browser, through the gtag.js tag, so ad blockers and declined consent remove the session. | With LeadJourneyServer-side and first-party, so the visit is recorded past blockers and banners, at 95%+ accuracy. |
| What is counted | Google Analytics 4Sessions, engaged sessions and the key events your site fires, per channel. | With LeadJourneyLeads, qualified leads, pipeline and won revenue, per source. |
| Revenue | Google Analytics 4Purchase and key event values passed at event time. Revenue that closes in the CRM weeks later never appears. | With LeadJourneyWon CRM revenue, attributed to the Grok visit that started the journey. |
| The attribution window | Google Analytics 4Lookback windows of up to 90 days on key events. A deal that closes later credits nothing. | With LeadJourneyNo window. The journey runs from the Grok tap to closed won, however long the sales cycle. |
| Devices | Google Analytics 4One user per browser cookie. The X app's in-app browser on a phone and the laptop the deal is booked from are two users. | With LeadJourneyOne journey per lead. The phone tap and the laptop booking are joined once the reader identifies, so Grok keeps the first touch. |
| Other touches | Google Analytics 4Data-driven attribution across the sessions GA4 can tie to that one cookie. | With LeadJourneyGrok weighed against Google Ads, Meta, LinkedIn, organic and the other AI engines in one multi-touch model, joined at the lead. |
| Landing pages | Google Analytics 4The landing page report shows sessions per page. Which cited page produced a lead is an exploration you build. | With LeadJourneyLeads and revenue per landing page, filtered to Grok, so you see which pages Grok cites and which of those convert. |
| Consent and GDPR | Google Analytics 4Needs consent to set its cookies. Consent mode models the sessions that declined. | With LeadJourneyFirst-party by design and processed in the EU, at 95%+ accuracy, with a DPA. |
Keep GA4. Stop paying your social team for Grok's work.
GA4 stays where you read page behaviour. LeadJourney adds the source it does not have, apart from X, and the revenue it cannot see.
MCP server
Chat with your Grok attribution data
The Grok source, the leads behind it and the revenue they closed are also served over MCP. Ask in Claude or ChatGPT, and the answer comes from your own numbers.
LeadJourney MCP connected, try any tab
Which campaigns produced our closed revenue last month?
Based on your LeadJourney data, 3 campaigns produced 148,200 EUR of closed revenue last month:
- Google Ads, Brand
- 38 leads, 9 closed deals, 61,400 EUR. Shortest path to signature.
- LinkedIn, Retargeting
- 21 leads, 6 closed deals, 48,900 EUR. Seven touchpoints on average.
- Meta, Lookalike DACH
- 54 leads, 5 closed deals, 37,900 EUR. Cheapest qualified lead.
Want this as a weekly summary in Slack?
Ask anything about your lead journeys
Where did our three biggest deals this quarter come from?
Your 3 largest deals this quarter all started somewhere the last click never showed you:
- 42,000 EUR
- First touch LinkedIn Ads, closed 63 days later after a webinar signup.
- 28,500 EUR
- First touch Google organic, paid click on day 11, demo on day 19.
- 21,800 EUR
- First touch a Meta video view, form filled from email six weeks on.
Want the full touchpoint list for any of them?
Ask anything about your closed deals
Which landing pages turn LinkedIn traffic into qualified leads?
3 pages take your LinkedIn traffic, and the qualified rate between them runs from 4% to 18%:
- /demo/attribution
- 18% qualified from 214 visits. Highest intent page on the site.
- /guide/server-side
- 9% qualified from 612 visits. Most journeys stall after the download.
- /pricing
- 4% qualified from 488 visits. Second most traffic, lowest intent.
Want the same breakdown for Google Ads traffic?
Ask anything about your landing pages
What did each channel cost per qualified lead last week?
3 channels spent budget last week. Cost per qualified lead ran from 41 EUR to 187 EUR:
- LinkedIn Ads
- 41 EUR per qualified lead. 2,300 EUR spent, 56 qualified.
- Google Ads
- 88 EUR per qualified lead. 4,400 EUR spent, 50 qualified.
- Meta Ads
- 187 EUR per qualified lead. 3,740 EUR spent, 20 qualified.
Want an alert the moment a channel passes 120 EUR?
Ask anything about your cost per lead
What do the journeys that close have in common?
3 signals show up in most of your closed deals and in almost none of the lost ones:
- Pricing page, 2+ visits
- In 71% of closed deals. In 12% of the ones that never closed.
- Demo within 14 days
- In 64% of closed deals. Median 9 days from the first click.
- Second contact
- In 58% of closed deals. A colleague of the lead arrives on site.
Want these three scored onto every lead in your CRM?
Ask anything about your lead journeys
Setup
Grok in your reports in about 21 minutes, none of them spent on Grok
There is no Grok account to connect and nothing to tell X. The time goes on the script and your CRM.
- 1About 5 minutes
Add a single line of code
Paste the LeadJourney script into your site or your GTM container. From the first page view it reads referrers server-side and reports Grok as its own source, with the X organic and direct numbers corrected at the same time.
- 2About 10 minutes
Connect your CRM
Sign in to Pipedrive, HubSpot, Salesforce, Attio or Close and pick the pipelines in scope. From then on every Grok lead is followed through its stages, and won revenue lands on the Grok source.
- 3Same day
Ask the question
Open the traffic channel report and Grok is a line next to X organic with leads, pipeline and revenue on it, or ask Atlas in plain words. Nothing was configured for Grok. It was recognised from the first visit.
Original reviews
What our customers wrote, word for word
4.9 out of 5 across 11 public reviews. Quoted as they were left, shortened only by dropping whole sentences.
- 5 out of 5 starsGoogle
“Before LeadJourney, we had no reliable tracking concept for our five-figure ad spend. We were manually building spreadsheet and CRM reports, inaccurate and time-consuming. Within two days, everything was set up. For the first time, I know exactly what I pay per lead and which campaigns actually bring in the best-qualified prospects.”
Florian BuckCEO, Klickkraft GmbH “With LeadJourney we are able to track all our leads and connect them with sales and attribution data to make better decisions. In the first month of using it we scaled from 0 to 100k revenue from paid ads only.”
GetreachBacklinks Marketplace (SaaS)- 5 out of 5 starsG2
“LeadJourney finally fixed my Marketing Analytics. It goes way beyond basic Ad Tracking Software. The Customer Journey Report saves hours of digging, and capturing everything from Offline Conversions to AI Search Tracking makes it the Best B2B Attribution Platform available.”
Sascha LenzMarketing Manager
- 5 out of 5 starsTrustpilot
“Connected LeadJourney for 2 clients, setup took literally 20 minutes each. The data became more accurate, the reports actually make sense. Now clients look at the dashboard and the 'why don't the numbers match?' questions are gone.”
Alexander SamarPerformance Marketing Agency - 5 out of 5 starsGoogle
“With LeadJourney, we have finally found a tool that provides us with the data we need to scale our performance marketing campaigns. The most important KPI is no longer lead price but cost per qualified lead.”
Steffen SiesingCEO, Bilanzmanufaktur GmbH
- 5 out of 5 starsG2
“The ability to track both online and offline conversions in one unified dashboard has given us insights we never had before. Our ROI has improved dramatically since we started integrating LeadJourney with our CRM. We're finally able to see the full customer journey, and it's been a game changer for our strategy.”
Andre WitzelFounder, Trading.de - 5 out of 5 starsTrustpilot
“The ability to seamlessly integrate data from multiple channels and see real-time insights has significantly improved our campaign results. We now focus on metrics that truly matter, like ROI and qualified leads.”
Nikita YatsunCEO, RLV Media GmbH
Read the reviews where they were left
FAQ
What marketers ask before trusting the Grok line
If yours is not here, our team answers in the chat within a few minutes.
Why does GA4 show my Grok traffic as X social and direct?
Because GA4 classifies by referrer, and a Grok answer inside X sends x.com, the same referrer as a click on a post. GA4 has always filed x.com under organic social, so the Grok click lands there too. A click from the Grok app usually carries no referrer, and no referrer is direct. Only grok.com shows up as itself, and only as a referral row. Nothing is broken; GA4 has no Grok bucket.
How does Grok attribution work when the answer was inside X?
The tracking script reads the referrer server-side as the page loads and recognises a Grok answer inside X as well as a visit from grok.com, then files both under Grok rather than under X organic social. The rest of the journey works as for any other source: the visit is stitched to the lead at form submit and followed through your CRM to revenue.
Do I have to configure anything for Grok traffic tracking?
No. There is no Grok account to connect, nothing to set up on X, no channel group to build and no regex to maintain. Once the LeadJourney script is on the site, Grok is reported as its own source from the first page view, alongside ChatGPT, Perplexity, Claude, Gemini, Copilot and DeepSeek.
Does LeadJourney tell a Grok answer apart from a post on X?
Yes, that is the point of the Grok source: a tap on a citation in a Grok answer is reported as Grok, a tap on a link in a post stays X organic. Your social team keeps the credit for the timeline and Grok gets the credit for the answers, which is the first time the two have been separable in a report.
Most of our Grok clicks come from a phone. Does that matter?
It matters in GA4, where the in-app browser on a phone and the laptop the reader books from a week later are two users, so the Grok first touch is lost. In LeadJourney the journey is joined once the reader identifies, so the phone tap and the laptop booking are one lead and Grok keeps the first touch. A click from the Grok app itself, with no referrer at all, arrives as direct for everybody, LeadJourney included; we say so rather than model a number for it.
Can I see which of my pages Grok cites?
Yes. The landing page report filtered to Grok lists every page a Grok reader arrived on, with visits, leads and won revenue per page. Grok searches X as well as the web, so the pages it cites are often the ones people are already linking to in posts, and the revenue column tells you which of those deserve more of your writing time.
A Grok visit turns into a deal three months later. Is it still attributed?
Yes. The journey has no window, so the deal is credited to the Grok visit that started it however long the cycle takes. GA4's lookback windows would have dropped the connection weeks earlier, which is one reason AI search looks smaller in GA4 than it is.
Is tracking Grok referrals GDPR compliant?
Yes. LeadJourney reads the referrer the browser already sends, on servers in the EU, first-party, so consent decisions are respected rather than worked around. Nothing is sent to xAI or to X, and the lead is only identified when the reader fills in your form. A data processing agreement is part of every plan.
Do I need a developer?
No. The script is one line in your site or your GTM container, the CRM connection is an OAuth sign in, and Grok itself needs nothing. Most accounts are live in about 21 minutes, and our team will do the setup with you on a call if you prefer.
What does it cost?
Grok tracking is part of the platform rather than a paid add on. Plans are priced on tracked events instead of seats, so your whole team and your agency can share one workspace, and every plan starts with a 14 day free trial without a credit card.
More integrations
More AI search integrations
Connected the same way, attributed in the same dashboard. The rest of your stack reports right next to this one.
95%+ accuracy, from Grok citation to closed deal
Count the deals Grok starts in LeadJourney, not as another X click
Add the script, connect your CRM, and Grok becomes a line in your reports next to X organic, with leads, pipeline and won revenue on it. Nothing to configure on xAI's side.
