CitadexDocs

Revenue Attribution: Connect AI Referral Visits to Orders, Deals and Revenue

Revenue Attribution shows the orders and revenue that follow AI referral visits, broken down by engine, market and landing page. This guide covers the page layout, the connection order (site script first, then revenue sources), how each source is connected, Attribution settings, confidence, source types, Orders, AI ads, recalculation and the data quality check.

Revenue Attribution12 min read

What this page does

Revenue Attribution in the sidebar connects visits that arrive from AI answers (AI referral visits) to orders, deals and revenue, and shows which engines, markets and landing pages AI-attributed revenue comes from, with the confidence of every number. It is available on every account.

The page has four tabs: Overview, Orders, AI ads and Experiments. The first time, click Attribution settings in the bar and follow its First-time setup; while there is no data yet, the Connect … button on Overview and Orders opens the recommended source directly (Shopify orders when your site is a Shopify store, for example). Revenue sources themselves are connected on Integrations in the sidebar. Experiments measures the incremental revenue of your optimizations; see the Incrementality experiments article.

On the right of the bar: Attribution settings and ⋯. Export CSV in ⋯ exports the current view: on Overview the table as switched (by engine, by market or by landing page), on Orders the order records, with the same filters as the page; Orders also has Export contacts.

Under the tabs is the Revenue from line: one chip per revenue source and the site script. Green means connected, amber one step left means a connection was started but not finished, and grey not connected marks the source recommended for your site; with none it reads No revenue source yet. Click a chip to open its connection dialog on the page; then come Manage connections (to Integrations) and Attribution settings.

Overview and Orders share one filter row: Market, Engine and Confidence, with the update time, the period and Compare to prior on the right. A filter that is set reads Market: Japan ✕; ✕ clears it.

At the bottom of the page is a question box: questions go to the AI Assistant, which answers with the numbers of the open tab. On Overview, up to three suggested questions based on the current data appear above it.

Overview

From top to bottom:

  • Conversion funnel: for a store, AI referral visits → AI-attributed orders → AI-attributed revenue, with conversion rate, average order value and verified share; with a CRM connected, leads → opportunities → won → revenue, plus open pipeline.
  • Weekly trend: switch between AI-attributed revenue, AI-attributed orders, AI referral visits and other metrics.
  • AI-attributed revenue by source: split by source type (see below).
  • Breakdown table: switch between By engine, By market and By landing page to list AI referral visits, AI-attributed orders, conversion rate, AI-attributed revenue, average order value and verified share. Click an engine row for its details; a market row filters the whole page to that market; a landing-page row opens its details, including the prompts whose AI answers cite that page.
  • Self-reported source: shown only once customers have answered "How did you hear about us?" in the CRM; listed separately and not added to AI-attributed revenue.
  • A line on how the numbers are computed at the bottom; Full method opens the definitions and measurement limits.

Connection order: site script first, then revenue sources

Stripe, HubSpot, Shopify and similar systems record who paid, not whether that person came from AI. The site script records visitors who arrive from AI and picks up their email when they sign up or submit a form. Matching the two by email is what attributes revenue to an AI engine. If you connect a revenue source without the script, revenue data arrives but cannot be attributed to AI.

The First-time setup at the top of the Attribution settings dialog lists five steps; the button next to each opens that connection dialog directly:

  1. 1

    Site script

    Open Site tracking snippet (the same as Integrations → Site tracking snippet), install the script as the dialog shows, then turn on Auto-capture form emails in the same dialog (off by default).

  2. 2

    Orders or deals

    Connect a store (Shopify, WooCommerce), Stripe or a CRM (HubSpot, Salesforce), or push data with Webhook / API. The guide recommends a source for your type of site, for example Connect Shopify orders for a Shopify store.

  3. 3

    Stage mapping

    Only for HubSpot: confirm which deal stages are open, won or lost, and how lifecycle stages map to the funnel.

  4. 4

    Window & currency

    Set Attribution window and Currency lower in the same dialog.

  5. 5

    Verify

    At least one AI-sourced contact identified and one attribution run. The guide then shows Setup complete; data connected.

If you connect a revenue source before the script is installed, the dialog explains why first. Install the tracking script opens the snippet in the same dialog; or choose It’s installed, continue.

The Attribution settings dialog also holds:

  • Attribution data quality: see below.
  • Currency, Attribution window and Recalculate. After you dismiss the guide, Show setup guide brings it back.
  • Change log: collapsed by default; expand it to see who changed what, and when.

The data sources

Every source has a card on Integrations in the sidebar (revenue sources in the Revenue attribution group, the site tracking snippet under AI traffic, Google under Search and analytics), and every card opens the same centered dialog: an overview and where it is used on the left, its own settings on the right. The dialog has Step-by-step (the full click path) and Guided setup with the AI Assistant, which opens the AI Assistant to guide you, and once connected Recent sync runs, Disconnect, Change secret, Disable or Regenerate. On Revenue Attribution, the chips in the Revenue from line open the same dialog.

CardHow to connect
Google (GA4)Integrations → Google: click Connect Google and pick a property; the same authorization also covers Search Console. Only the workspace owner can authorize.
Site tracking snippetIntegrations → Site tracking snippet: add the script as the dialog shows. With Auto-capture form emails on, the email from a form submit is linked to the visitor.
HubSpotIntegrations → HubSpot CRM: Connect HubSpot takes three steps: (1) create a service key in HubSpot with the 6 read-only scopes listed in the dialog, copy the key (starts with pat-), paste it under Access token and click Verify and connect; (2) Stage mapping → Save and start sync; (3) done. The first sync backfills 12 months, then syncs every 30 minutes. Once connected, the dialog has Sync now, Stage mapping and Disconnect.
SalesforceIntegrations → Salesforce: create a Connected App in Salesforce, paste its Consumer key and Consumer secret, and click Authorize Salesforce. For a sandbox tick Connect a sandbox (test.salesforce.com). Backfills 12 months, then syncs every 30 minutes.
StripeIntegrations → Stripe: click Generate webhook endpoint, add an endpoint with that URL in Stripe, select checkout.session.completed, invoice.paid and charge.succeeded, paste the endpoint's signing secret (whsec_…) back and click Save secret. Use live mode, not test mode. New payments arrive automatically; past payments are not imported.
ShopifyIntegrations → Shopify orders: in Shopify admin → Settings → Notifications → Webhooks, create a webhook for the order payment event, format JSON, with the URL from the dialog. Paste the signing secret from the bottom of that page into the dialog and click Save secret.
WooCommerceIntegrations → WooCommerce: in WooCommerce → Settings → Advanced → Webhooks add one with topic Order updated and the URL from the dialog as delivery URL. Paste that webhook's Secret into the dialog and click Save secret.
Webhook / APIIntegrations → Webhook / API: for an in-house CRM, Pipedrive, Zoho and similar. Click Generate endpoint, then set your CRM or Zapier / Make to POST JSON to it when a lead is created, an opportunity changes or a deal is won. The format is under Example. Send one test: when the counts in the dialog go up, it works. Regenerate stops the old URL at once; Disable turns it off.

Shopify order channels

When someone orders directly inside an AI chat (for example store checkout in ChatGPT or Google AI Mode), the order never touches your site. The Integrations → Shopify orders dialog lists the Order channels it has received with their order counts. AI channels are recognised by name, and you can correct them: tick Bought inside AI and choose the AI platform in the dropdown (Other AI if it is not listed). Untick to stop counting a channel as AI.

Confidence

Every AI-attributed order has a confidence level, which you can filter with Confidence at the top of the page:

  • Verified: checkable order by order or reported by the platform, such as a form email matched to the visitor, a purchase reported by Google Analytics or Shopify, or an order from an order channel you confirmed as AI.
  • Likely: linked by a match that is usually right, such as an AI order channel recognised by name, a match at company level, or a manual link.
  • Modeled: computed by a model or an experiment.

The Confidence filter applies to amounts and order counts alike (and to leads and pipeline with a CRM). AI referral visits come from the site script or platform data and do not change with it.

Source types

AI-attributed revenue by source assigns each order to one source type only, checked in this order:

  • Bought inside AI: the customer ordered inside an AI chat (for example store checkout in ChatGPT or Google AI Mode) without visiting your site.
  • AI agent order (Beta): the order carries a verified AI agent marker; set up Agentic order marker under Integrations → Shopify.
  • AI ad referral: the customer arrived through an ad in an AI interface and ordered (the ad click id was kept).
  • AI organic referral: the customer arrived from an organic AI answer and ordered.
  • AI-assisted conversion: AI was on the purchase path but not the first source.

The five add up to AI-attributed revenue. Incremental revenue (experiment) comes from a completed experiment on Experiments, is shown separately and is never added to the five.

Orders

Orders lists AI-attributed orders, newest first, with the columns time, order, source type, engine, amount, confidence and basis. View basis shows the order's source type, confidence, the rule applied, how the buyer was linked and the timeline; a wrong record can be marked as wrong or linked to an engine manually. Estimate records (estimated influence only, never revenue) are hidden by default; tick Show estimates to see them.

AI ads

The AI ads tab covers ChatGPT ads:

  • Ad spend and return: ad spend, AI ad referral revenue (ChatGPT) and ROAS. Revenue uses the same definition as AI ad referral in AI-attributed revenue by source; ad spend and ROAS need a connected ChatGPT Ads account.
  • How often ads appear next to your tracked prompts (share across samples, against the previous period and the market average).
  • Prompts to review: competitor ad and you not recommended; your ad and you not recommended; recommended and still advertising; competitor ad and competitor not recommended.
  • Brand comparison: each brand's ad share next to its organic recommendation share; every advertiser with its ad copy, landing pages and first and last seen.
  • Check landing pages: whether your ad landing pages keep ChatGPT's click parameter (oppref) and include tracking.
  • Connecting your ChatGPT Ads account: click Connect your ChatGPT Ads account or open Integrations → ChatGPT Ads and paste an Advertiser API key created in Ads Manager settings; sync now and disconnect are in the same dialog.

Measurement limits: ads are sampled from logged-out sessions, so audience-targeted ads are not observed. To be notified when ads change, turn on Automations → Ad watch.

Recalculation

Attribution runs automatically every hour. To see the effect of a stage-mapping, currency or window change right away, click Recalculate in the Attribution settings dialog. Manual recalculation is available once an hour; the dialog shows how many minutes remain.

Attribution data quality

Attribution data quality in the Attribution settings dialog lists anything that affects the results; Check now on the right of its title runs the check immediately. Each finding is marked Info, Warning or Error; click it for the cause and the fix:

FindingWhat to do
Won deals without an amountAdd the amount in the CRM; the next sync picks it up
Unmatched CRM contacts (90 d)Turn on form email capture so more contacts match
Possible duplicate dealsMerge or delete the duplicate in the CRM
Unrecognised AI-like referrersTell us the site and we add it
Stale or failing connectorOpen that source on Integrations and click Sync now; if it still fails, disconnect and connect again
Amounts without FX conversionUsually fixed by the next run
Page views without a sessionOpen Integrations → Site tracking snippet and check the script is fully installed
Attribution conflicts (multiple engines)The customer used several AIs; results are usable as they are

FAQ

I connected Stripe but see no AI-attributed revenue. Check that the site script is installed and Auto-capture form emails is on. The customer has to arrive from AI and leave an email first, then pay with the same email, for the order to be attributed to AI.

The guide is stuck on Verify. Attribution has run but no AI-sourced contact has been identified yet. This requires a visitor arriving from an AI answer who leaves an email in a form or places an order, or a CRM lead whose source is AI.

Why is there no customer count in the funnel? The same customer can order with different emails or as a guest, so buyers cannot be de-duplicated reliably; the funnel counts orders.

Does disconnecting HubSpot delete data? You choose: keep or delete the imported data.

I can't find a setting in the vendor's admin. Open that source on Integrations and click Guided setup with the AI Assistant in its dialog; the assistant guides you step by step.

Was this article helpful?