Grow or DieConnect my product

AI traffic analytics

AI Traffic Analytics: Crawlers, Referrals, Revenue

By · Updated

A crawler reading your pricing page, ChatGPT citing it, and a buyer clicking through are three different events. Grow or Die keeps them separate until evidence connects them.

Connect my productCheck visibility first
ServerCrawler request
AnalyticsHuman referral
PaymentRevenue outcome

The useful chain

Page read → person arrived → customer paid.

1. Observe crawler requests

The server hook records public GET and HEAD requests after the response finishes. API, admin, health, and private routes stay excluded.

2. Observe referrals

GA4 or PostHog supplies source, referrer, campaign, landing page, geography, and device where those fields were actually captured.

3. Join real revenue

A payment belongs to an AI source only when visitor, account, customer, and payment identities form a defensible chain. Unknown stays unassigned.

What you can decide

Find the pages AI reads—and the traffic that earns.

Which public pages attract AI crawlers?

Compare verified crawler requests by page and bot without interpreting requests as citations.

Which AI sources send people?

See observed referrers and landing pages; missing tagging remains missing instead of becoming direct traffic by assumption.

Which referred customers are profitable?

Subtract attributable AI model cost from observed payment contribution only after the customer identity is linked.

A traffic-to-revenue audit checklist

This traffic-to-revenue audit checklist starts with a strict separation: verified AI crawlers are machine requests, AI referrals are observed browser arrivals, and attributed payments require a verified identity relationship. A crawler's 200 response cannot be counted as a new customer.

  1. Separate internal tests, bots and duplicate events from external human sessions.
  2. Store normalized landing paths and safe campaign dimensions, not arbitrary query strings or personal data.
  3. Preserve missing or privacy-stripped referrers as unknown.
  4. Link visitors to accounts only on a verified application event.
  5. Use signed payment evidence, an explicit attribution window and the original currency.
  6. Subtract only complete, account-linked AI cost before claiming contribution profit.

For example, 20 crawler requests, 4 referred sessions and 1 linked payer are three separate observations, not a 25-person audience. A payment after the visit is an association; it does not prove incremental revenue caused by the citation.

Review the citation-to-revenue method and the native SDK acceptance checklist. GOD's own SDK collects native evidence; GA4 is an optional source, not a requirement for this method.

Related reading

AI visibility

Measure ChatGPT recommendations separately from the crawler requests on this page.

Grow or Die pricing

Starter is $20/month and Growth is $99/month per website after a 7-day trial.

Visibility is an input

Revenue is the outcome.

Use AI visibility to find attention. Use customer-level evidence to decide whether that attention is worth scaling.

Explore AI visibility