CitationGraph AI Attribution vs. GA4 Default Channel Grouping

Standard GA4 channel rules were designed for browser Referer headers and UTM tags — leaving client-stripped AI clicks buried in Direct and Google AI Overviews blended into Organic.

Google Analytics 4 is essential for general web conversion events and Google Ads linking, but out-of-the-box GA4 executes only in client JavaScript (missing 100% of non-JS AI crawlers) and misclassifies referrer-stripped desktop/mobile AI app clicks into Direct. CitationGraph adds the missing server-side and deterministic AI attribution layer.

CitationGraph adds critical visibility when

  • ✓You see unexplained spikes in GA4 'Direct' traffic on deep documentation, comparison, or product pages
  • ✓You need to correlate server-side AI bot crawls (which never execute GA4 gtag.js) with subsequent human AI referrals
  • ✓Compliance teams require zero-cookie, GDPR-friendly first-party telemetry without third-party ad-tracker scripts
  • ✓You want unified visibility across ChatGPT (`utm_source=chatgpt.com`), Perplexity, Claude, Gemini, Copilot, DeepSeek, Kimi, and Doubao

Standard GA4 alone is sufficient when

  • •Your business relies purely on UTM-tagged paid campaigns and has no strategic focus on organic AI search citations
  • •You only need native Google Ads audience export and standard e-commerce checkout funnel events without crawler telemetry

Attribution & Telemetry Comparison

Verification DimensionCitationGraph + GA4 ContextStandalone GA4 Default Setup
Non-JS AI Crawler Visibility100% captured at server/edge middleware (GPTBot, ClaudeBot, PerplexityBot, GoogleOther)0% captured (AI crawlers do not execute client-side gtag.js)
AI Referral Classification RulesDeterministic 7-layer rule engine covering global & APAC AI assistants (auditable taxonomy)Default regex misses emerging AI hosts or lumps stripped-referrer app clicks into Direct
Google AI Overview DisaggregationCross-checks GSC query-page shifts + AI crawler bursts + landing behavior patternsBlended indistinctly into standard Google Organic Search traffic
Cookie & Consent FootprintZero-cookie (~2 KB) privacy-preserving first-party collectionDepends on client cookies and Consent Mode v2 banner opt-in rates
Native Google Ads Bid Audience SyncComplements ad platforms (or pairs with GravityAds True ROAS for order-level profit)Native one-click audience & conversion sync with Google Ads
Markdown (.md) Endpoint TelemetryTracks AI agent fetches on explicit .md URLs and Accept: text/markdown rewritesInvisible to GA4 because .md responses do not load HTML script tags
Setup OverheadLightweight Next.js/edge runtime hook + read-only GSC/GA4 connectorAlready installed on most marketing sites

3-Step Attribution Upgrade

  1. Keep GA4 active for standard Google Ads conversion linking and broad UI funnel events.
  2. Install CitationGraph runtime tracking so both HTML routes and `.md` / `llms.txt` machine endpoints emit server-side events.
  3. Connect read-only GSC & GA4 exports into CitationGraph to view crawl → citation → referral → conversion in one ledger.

Related Technical Comparisons

Test Your Domain Against Static GEO Readiness Checks

Run an instant static scan on your public URL or request an invite to inspect server-side AI crawler and referral telemetry.

Methodology & Scope Note: All matrices compare publicly documented product architectures, protocol capabilities, and billing models as of 2026-11-20. External product features evolve; verify current commercial terms on each vendor's official website or contact analytics@gravity.dev for factual updates.

Common questions

Why can't GA4 see requests to `/llms.txt` or `/*.md` endpoints?

GA4 relies on browser JavaScript (`gtag.js`) embedded in HTML pages. Plain-text `llms.txt` and `text/markdown` responses contain no JavaScript and are fetched by headless HTTP clients, making server/edge telemetry mandatory.

Does CitationGraph slow down Core Web Vitals when run alongside GA4?

No. Server/edge bot tracking runs asynchronously via `waitUntil` off the critical render path, and the optional client beacon is ~2 KB with zero third-party cookies.