Do-it-yourself game plans · No. 14 / 22
How do you connect AI visibility to traffic, pipeline and revenue?
Last updated

Use three separate evidence streams: observed answers, measured visits and customer-reported discovery. Do not attribute all three to one intervention merely because they moved in the same month.
1. Configure traffic reporting
Ask marketing operations to:
- Inspect GA4’s AI Assistant channel, then drill into source/medium and landing pages. Its documented scope excludes Google AI Overviews and AI Mode. (support.google.com)
- Maintain source-level reporting rather than relying only on a channel total. Google documents source and medium as distinct traffic-source dimensions. (support.google.com)
- Check actual ChatGPT referral URLs and whether tracking parameters survive redirects. OpenAI says ChatGPT includes
utm_source=chatgpt.comin referral URLs. (help.openai.com) - Report agreed events such as completed demo requests, qualified trials or sales-accepted leads—not merely page views.
- Preserve the organisation’s existing consent, internal-traffic and data-quality rules.
Do not reclassify unexplained direct traffic as AI traffic. Google documents direct traffic as traffic without available referral information; that absence does not identify the missing source. (support.google.com)
2. Use native visibility reports carefully
Export the Google and Bing views relevant to your scope, and keep their definitions separate from your prompt-panel metrics.
For Search Console, preserve the report context: Google warns that some unavailable values displayed as ~ or - become zeros in downloaded data. A missing generative-AI report can also reflect insufficient impressions rather than establish universal absence. (support.google.com)
Check known reporting anomalies before explaining a change. For example, Google documents a generative-AI impression logging issue affecting 13–17 August 2026. Annotate affected historical comparisons rather than attributing every movement to your work. (support.google.com)
3. Ask customers without leading them
Add an optional open-ended discovery question, such as:
“What first put us on your shortlist?”
Then, where appropriate, ask separately whether an AI assistant played a role and which one. Record prompted and unprompted answers separately. Never ask customers to disclose sensitive conversations merely to complete your attribution spreadsheet.
4. Keep the commercial report modest
Use four rows in the monthly readout:
| Evidence | Appropriate statement |
|---|---|
| Controlled prompt panel | “Recommendation frequency changed within our fixed test set.” |
| Native visibility reports | “Our pages recorded these platform-defined impressions or citations.” |
| Analytics and CRM | “These identifiable assistant-referred visits produced these recorded outcomes.” |
| Customer interviews | “These respondents reported that assistants contributed to discovery or evaluation.” |
Reserve “incremental revenue caused by this programme” for a design and dataset capable of supporting that conclusion. A small before-and-after visibility test is not such a design.
Sources cited on this page
- support.google.com support.google.com/analytics/answer/9756891?hl=en--&utm_source=openai
- support.google.com support.google.com/analytics/answer/15612152?hl=en&utm_source=openai
- help.openai.com help.openai.com/en/articles/12627856?utm_source=openai
- support.google.com support.google.com/analytics/answer/11242841?hl=en&utm_source=openai
- support.google.com support.google.com/webmasters/answer/16984139
- support.google.com support.google.com/webmasters/answer/6211453?hl=en&utm_source=openai