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.
AI traffic analytics
AI Traffic Analytics: Crawlers, Referrals, Revenue
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.
Bot requestObserved in your server middleware after a verified crawler identity check.
Human referralObserved by GA4 or PostHog when a person arrives from an AI source.
Payment outcomeObserved in Stripe, Lemon Squeezy, or Polar and joined through a stable identity.
The useful chain
Page read → person arrived → customer paid.
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.
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.