Claude integration
Claude attribution, no setup needed, from AI referral to closed deal
Analytics tools file Claude referrals under direct. LeadJourney names the source on arrival, then follows it through to leads and won 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
ClaudeWhere the visitor comes from- claude.ai
AI search tracking
LeadJourneyThe tracking script recognises the referrer on arrival, no setup- Own traffic source
- Leads
- Pipeline
- Won revenue
Claude 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
Claude cites your site. Your analytics files the visit under referral and direct.
When Claude searches the web, it cites its sources. A reader arrives from claude.ai, or from the app with no referrer at all, and GA4 files those as referral and direct. Neither says Claude.
Claude traffic in your analytics today
A referral row and a blank, neither of them named Claude
- A click from claude.ai in a browser is a referral in GA4, one row among every domain that ever linked to you, and it only exists once you scroll down to it.
- A click from the Claude desktop app on a Mac or a Windows laptop opens in the system browser with no referrer, and no referrer means direct.
- A click from the Claude app on iOS or Android arrives the same way, so the phone share of Claude traffic is direct too.
- GA4 records the visit in the browser, so an ad blocker or a declined cookie banner removes the session before Claude 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.
- Claude is a work tool for many of its users, on Team and Enterprise plans and in the desktop apps, so the buyers it sends are the ones with budget, and the desktop click is the one that lands in direct.
- Telling Claude apart means a custom channel group with a regex for claude.ai, maintained by hand, and it still never sees the app clicks and still stops at the session.
Claude with LeadJourney
One source, named on arrival, followed to revenue
- The tracking script recognises a claude.ai referral server-side as the page loads and reports it as one source called Claude, next to ChatGPT, Perplexity, Gemini and the other engines.
- Claude is lifted out of the referral list, where it was one row among hundreds, and reported as a channel with leads and revenue on it.
- 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.
- Claude sits in the same multi-touch model as Google Ads, Meta, LinkedIn, organic and the other AI engines, so a Claude first touch and a paid brand-search close are one journey, not two sessions.
- Nothing is sent to Anthropic and nothing is requested from it. Recognising the referral is reading a header the browser already sent.
- 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
Claude attribution in two steps: name the visit on arrival, then follow it to revenue
Both run on their own once the script is on the site: claude.ai becomes a source rather than a row, then the lead, the pipeline and the won revenue behind a citation.
1 Claude traffic tracking from the first page view
The referral becomes a source on the server, not in a channel group somebody maintains.
A reader asks Claude a question, Claude searches the web and cites your page as a source, and the reader clicks through from claude.ai.
The tracking script reads the referrer server-side on arrival and files the visit under Claude, a source of its own rather than one referring domain among hundreds.
The landing page, the pages read and every later visit join one anonymous first-party journey, so the same reader coming back through a brand search a week later is still one person.
When the reader fills in a form or books a call, the journey is stitched to the lead, and Claude is on record as the first touch.
2 Follow the lead through your CRM and compare Claude with every other channel
The citation cost nothing. The CRM says what it was worth.
With a two-way CRM connected, the journey is written onto the record: Claude as the source, the page it cited, and every touch 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.
Claude appears in the traffic channel report as its own line: visits, leads, pipeline and won revenue, next to a cost per lead that for Claude is zero.
The multi-touch models weigh Claude against Google Ads, Meta, LinkedIn, organic and the other AI engines, so you learn whether it opens deals, closes them, or both.
Your CRM closes the loop
Your CRM shows what the Claude visit was worth
Anthropic sells no ads, so there is no ad account, no spend and no conversions API behind a Claude visit. Its value only appears in the CRM, so LeadJourney follows every Claude lead there 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.
Won revenue on the Claude line
The Claude line in your reports carries won revenue from the CRM, so a source that sends a few readers a week and one large deal a quarter is visible for what it is.
Which engine sends buyers
You see how many Claude leads qualify, how many stall, and how that compares with ChatGPT, Gemini and Google organic, before deciding how much of your writing should be aimed at being cited.
No lookback window
A Claude visit in January that becomes a deal in April still credits Claude. The journey runs until the deal closes, not for a lookback period.
Reporting
The questions GA4 cannot answer about Claude
Each of these is a report filtered to the Claude source, not a custom channel group and an export. The Claude line simply exists now, and it runs all the way to revenue.
How many leads did Claude send us last month, and how many of them qualified?
How much won revenue started with a Claude citation this quarter?
Which of our pages does Claude cite, and which of those turn readers into leads?
Does Claude open deals that a brand search or a retargeting ad later closes, or does it close deals our content opened?
How does Claude compare with ChatGPT, Perplexity and Gemini on leads and average deal size?
How much of what we reported as direct and referral this year was Claude all along?
Watch it
Claude as its own channel
The AI engines separated out of direct traffic, each one measured through to booked meetings and closed revenue.
LeadJourney and Google Analytics 4
Where GA4 ends and LeadJourney starts
GA4 sorts sessions and key events into channel groups designed before assistants cited sources, and a CRM was never part of them.
| Capability |  Google Analytics 4 | With LeadJourney |
|---|---|---|
| Claude attribution | Google Analytics 4No Claude source. claude.ai is a referral row, and clicks from the Claude desktop and phone apps arrive as direct. | With LeadJourneyOne source called Claude, recognised server-side on arrival, reported next to ChatGPT, Gemini and the other engines. |
| 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 Claude 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 Claude click to closed won, however long the sales cycle. |
| Other touches | Google Analytics 4Data-driven attribution across the sessions GA4 can tie to one user, usually a browser cookie. A new device starts a new user. | With LeadJourneyClaude 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 Claude, so you see which pages Claude cites and which of those convert. |
| Setup | Google Analytics 4A custom channel group with a regex for claude.ai and every other AI domain, maintained by hand as new engines appear. | With LeadJourneyNothing. The script recognises Claude and the other AI engines and reports each as its own source. |
| 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. Give Claude a line with revenue on it.
GA4 stays where you read page behaviour. LeadJourney adds the source GA4 does not have and the revenue GA4 cannot see.
MCP server
Ask Claude about your Claude attribution data
Claude speaks MCP, so the assistant that sent the visitor is the one you can ask what the visitor was worth. Add the LeadJourney server as a connector and the answer is one question away.
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
Claude on its own line in about 21 minutes, with nothing to do on Anthropic's side
There is no Claude account to connect and no channel group to build. The time goes on the script and your CRM, and the first Claude visit after that is already on the right line.
- 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 Claude as its own source, with the referral list and the direct number corrected at the same time.
- 2About 10 minutes
Connect your CRM
Sign in to HubSpot, Salesforce, Pipedrive, Attio or Close and pick the pipelines in scope. From then on every Claude lead is followed through its stages, and won revenue lands on the Claude source.
- 3Same day
Ask the question, in LeadJourney or in Claude
Open the traffic channel report and Claude is a line with leads, pipeline and revenue on it. Or add the LeadJourney MCP server as a connector and ask Claude itself. Nothing was configured for Claude; 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 Claude line
If yours is not here, our team answers in the chat within a few minutes.
I can already see claude.ai in my GA4 referrals. What is missing?
Three things. The row only holds the clicks that carried a referrer, so everything from the Claude desktop and phone apps is sitting in direct instead. The row is a referral, not a channel, so it never appears next to Google Ads or organic in a channel report unless you build a custom channel group and keep its regex current. And it ends at the session: GA4 cannot tell you whether the reader became a lead, qualified or closed, because that happens in your CRM.
How does Claude attribution work?
The tracking script reads the referrer server-side as the page loads, recognises claude.ai, and files the visit under a source called Claude. The landing page and every later visit join one first-party journey, the journey is stitched to the lead at form submit, and the lead is followed through your CRM to closed won. Claude then appears in every report and every attribution model as a source of its own, with leads, pipeline and revenue on it.
Do I have to configure anything for Claude traffic tracking?
No. There is no Anthropic account to connect, no channel group to build and no regex to maintain. Once the LeadJourney script is on the site, Claude is reported as its own source from the first page view, alongside ChatGPT, Perplexity, Gemini, Copilot, Grok and DeepSeek.
What about clicks from the Claude desktop app or the phone app?
A link opened from the Claude app on a Mac, a Windows laptop or a phone opens in the system browser without a referrer, so it arrives as direct for every analytics tool, LeadJourney included. We say so rather than model a number for it. If that reader converts, the journey is stitched to the lead and followed to revenue like any other direct visit.
Claude sends us a handful of visits a month. Is that worth measuring?
The CRM decides that, not the session count. A Claude reader arrives having asked a specific question and clicked the source Claude cited for it, and a share of them are at work, researching a purchase. A source that sends a few dozen visits and one closed deal is worth more than one that sends thousands and none, and only revenue per source shows the difference. That is also the number to have before deciding how much content to write for AI search.
Can I see which of my pages Claude cites?
From the other end, yes. The landing page report filtered to Claude lists every page a reader arrived on after Claude cited it, with visits, leads and won revenue per page. It is not a list of every citation Claude ever made, only of the ones that were clicked, which is the list that matters for revenue.
Can I ask Claude itself how many leads it sent?
Yes. LeadJourney ships an MCP server, and Claude connects to it from its connectors settings. Once it is connected, ask Claude how many leads came from Claude last month, which pages they landed on, or what the deals they became were worth, and the answer is read from your workspace rather than guessed. The same works in ChatGPT, Gemini and any other client that speaks the protocol.
A Claude 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 Claude 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 Claude referrals GDPR compliant? Does anything go to Anthropic?
Yes, and no. 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 Anthropic and nothing is requested from it; recognising the referral is reading a header. The reader is only identified when they fill in your form, and 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 Claude 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?
Claude 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 Claude citation to closed deal
Put the leads Claude sends on their own line in LeadJourney
Add the script, connect your CRM, and Claude becomes a line in your reports with leads, pipeline and won revenue on it. Nothing to configure on Anthropic's side, and nothing sent there.
