LEADSTORE
Get your score
Attribution

How to Track AI Assistant Referrals with Referrers and UTMs

A practical guide to measuring ChatGPT, Perplexity, Claude, Gemini, and other AI assistant traffic without overclaiming proof.
7 min read
Updated 2026-06-09
Referrers can identify assistant clicks when they survive the redirect path.
UTMs help separate campaigns from organic assistant referrals.
Leadstore Tag ties these signals to pages, devices, countries, and content performance.
AI interface and robotics lab, representing answer tracking and assistant visibility
·
Unsplash
AI assistant referrals are often visible through referrer domains or UTM fields, but they should be labeled as inferred or observed signals unless supported by stronger evidence.

What to capture

■
Landing page URL and query string.
■
Referrer URL and referrer domain.
■
utm_source, utm_medium, and utm_campaign.
■
Language, country, device, viewport, and browser context.
■
Event type, timestamp, and sample weight.
■
Content identifier for Content Autopilot posts when available.

How to classify AI referrals

A visit from a domain such as chatgpt.com, perplexity.ai, claude.ai, or gemini.google.com should be treated as an AI assistant referral signal.
That signal is useful for attribution, but it is not the same as verified crawler proof. Leadstore keeps assistant clicks and crawler verification separate so users understand what the data can support.

Why UTMs still matter

UTMs help separate paid campaigns, owned campaigns, partner links, content experiments, and organic assistant referrals. When a user publishes Content Autopilot content, UTMs can also help connect a content launch to downstream traffic.

Leadstore reporting model

■
by_ai_tool for assistant referral domains.
■
by_campaign for UTM campaign performance.
■
by_channel for source and medium rollups.
■
top_pages for page-level content performance.
■
verified_bots for request-level crawler proof where available.

How this fits into the three Leadstore stages

■
Stage 1, account + site added: users get the audit reward before any tag or key - four core channel scores, top fixes, readiness, generated llms.txt and llm-data.json, and the Leadstore Tag snippet to install.
■
Stage 2, tag installed: users get the live telemetry reward with no key required - AI-crawler activity by engine, verified-bot counts, human traffic, top sources, top pages, devices and geography.
■
Stage 3, key connected: users add answer tracking on top of the audit and telemetry layers - Visibility Score, SAIV, Brand Monitor, share of voice, citations, competitors and hallucination checks.
Next step
Use Leadstore Tag to capture the referrer, UTM, page, and device fields needed for assistant referral analytics.