9 min read
How to attribute revenue to ChatGPT traffic
Trace one referral through signup and a USD 49 Stripe payment, including the identity links and missing evidence checks.
· Grometrics Team
To attribute revenue to ChatGPT, capture ChatGPT as the referral source on the first visit, preserve that source through signup and checkout, then connect the resulting payment, renewal, or refund to the same visitor. The result is revenue by AI referral, not just ChatGPT sessions or conversions.
The example below follows a single web visit into a confirmed Stripe payment. All identifiers and amounts are illustrative. They are not customer results or evidence that ChatGPT caused a purchase.
Follow one ChatGPT referral to USD 49
A reader follows a ChatGPT link to an example shop's pricing page, creates an account, and buys a one time product for USD 49 on the same day. Tracking was installed before the visit, the browser supplied a chatgpt.com referrer, and there are no other acquisition touches in this example.
| Step | Illustrative saved value | What connects it |
|---|---|---|
| Arrival | chatgpt.com to /pricing; visitor vis_example | The pageview supplies the referral and landing page for this visitor. |
| Signup | Application user user_example to visitor vis_example | Identify links the signed in application user to the tracked visitor. |
| Checkout | Customer cus_example; grometrics_visitor_id = vis_example | Checkout Session metadata carries the current Grometrics visitor ID. |
| Confirmed payment | Payment pi_example; USD 49; customer cus_example | Stripe confirms the payment. Grometrics matches its visitor metadata and saves provider customer and payment links. |
The signup user ID and Stripe customer ID identify different records. Calling identify connects user_example to the visitor. It does not send the visitor ID to Stripe. Checkout must carry that separate link before the payment can use this exact matching path.
CHATGPT REVENUE ATTRIBUTION
See which ChatGPT referrals become customers.
Track ChatGPT revenue →Connect signup identity and Stripe Checkout
- Install tracking before acquisition starts. Use the web tracking setup and confirm the initial pageview arrives.
- After successful signup or login, identify the user with the stable ID from your application. Follow the identity setup.
- Use the current visitor ID returned after identity linking. Send it to your own Checkout backend as tracking context, separately from the signed in account and price your server authorizes.
- Create the Stripe Checkout Session with grometrics_visitor_id in its metadata. Add grometrics_session_id if available. Follow the Stripe Checkout attribution instructions.
- Keep the Stripe customer on that Session. A returning customer must use the correct existing Stripe customer record for your application account.
const visitorId = await window.grometrics.identify(user.id);
if (visitorId) {
const trackingContext = {
grometrics_visitor_id: visitorId,
grometrics_session_id: window.grometrics.getSessionId()
};
// Send trackingContext to your authenticated Checkout endpoint.
}Confirm the payment, then verify the report
Connect the intended Stripe account through Integrations. Grometrics verifies Stripe's webhook signature and imports confirmed activity. A completed unpaid Checkout Session does not prove that money arrived. For delayed payment methods, wait for Stripe's payment success confirmation.
- In Stripe, locate pi_example and verify its successful USD 49 amount and cus_example customer. In a real review, use the actual payment and customer identifiers.
- Open Transactions for a date range containing the payment. Find that Stripe payment and check amount, currency, visitor, and attribution evidence.
- Open Attribution, select the same reporting period and first touch model, and inspect the ChatGPT referral source. The single eligible touch in this example receives USD 49.
- Use Visitors to inspect the linked journey and its original referral. Confirm the payment connects to that visitor rather than assuming matching amounts prove identity.
Stripe supplies 4900 minor units for this USD payment. Grometrics converts that to USD 49 and uses the payment identifier to avoid counting repeated delivery as another sale. One payment is not proof of an additional visit.
Keep missing identity and source evidence visible
- No captured ChatGPT referral: a typed address, copied link, blocked tracker, or missing referrer does not prove ChatGPT acquisition. Do not invent a source from the later payment.
- No exact visitor link: Grometrics can use previously saved provider links or eligible captured email identity. An email match is different evidence from an exact visitor match. If no usable match exists, the payment remains unattributed.
- Visitor matched but no recent touch: source allocation considers touches in the 30 days before the payment. Older acquisition history alone does not make this payment attributed to ChatGPT.
- Several captured touches: first touch, last touch, and linear allocation can produce different channel totals. Keep the selected model consistent when comparing reports.
- Another device or checkout domain: identifying the application user helps join known visits, but it cannot reconstruct an untracked referral. Preserve the visitor context through the checkout handoff.
- Renewals and refunds: inspect them as separate money events. Stored Stripe customer, subscription, and payment links can preserve visitor matching, but they do not create fresh acquisition touches or bypass the reporting window.
Use the evidence to make a channel decision
Before investing in more ChatGPT visibility, review captured referral visits, signups, matched payments, refunds, and unmatched revenue separately. A citation is visibility. A referral is a recorded visit. A confirmed matched payment is revenue evidence. These are different outcomes.
Use the Stripe attribution setup to establish collection and the worked Stripe revenue audit to reconcile money events. Keep the existing source and payment evidence available when deciding whether to change a landing page or acquisition budget.
FAQ: how to attribute revenue to ChatGPT traffic
How do you attribute revenue to ChatGPT traffic?
Capture the ChatGPT referral on the first visit, store it on the visitor or session, then match that visitor to the payment event from Stripe, RevenueCat, Gumroad, Paddle, PayPal, Shopify, or another provider.
Why does ChatGPT traffic disappear in normal analytics?
Many analytics tools stop at sessions or lose source context before checkout, signup, app install, or subscription conversion. Revenue attribution keeps the referral with the customer record long enough to prove whether the visit paid.
What report should you look at?
Start with revenue attribution analytics by source, then drill into Stripe analytics or payment-provider revenue to compare ChatGPT, Google, paid ads, referrals, and direct traffic by customers, revenue, renewals, and refunds.
Is ChatGPT traffic worth optimizing for?
Only if it creates customers. The point is not to increase AI referrals; it is to find whether ChatGPT-referred visitors reach checkout, pay, renew, or refund at a rate worth more content and product work.
CHATGPT REVENUE ATTRIBUTION
See which ChatGPT referrals become customers.
Track ChatGPT revenue →See the full page:
Revenue attribution analyticsRELATED POSTS