How to attribute AI search to pipeline

End-to-end attribution from AI engine citation → AI-referred session → contact → opportunity → closed-won. The seven-link chain most teams break at link three.

Updated 2026-04-20 · How-to guide · ~7 min read

AI search attribution is a chain: citation appears, user clicks, session lands on your site, contact is created, opportunity opens, deal closes. Most teams have data at link 1 (citation count) and link 6 (closed-won) but nothing in between. Here's how to wire all seven links inside HubSpot.

Required tools

  • An AEO monitoring tool for citation data (Lantern, Profound, Peec, Scrunch, Otterly)
  • HubSpot Marketing Hub Professional
  • JavaScript snippet on your site (or Lantern-installed equivalent)
  • 30 minutes per month to review the closed-won prompt list

The steps

1

Capture the citation: monitor your prompts × engines on a daily cadence

You can't attribute traffic to citations you don't know about. Use Lantern, Profound, Peec, or Scrunch to monitor your top 50–150 prompts across ChatGPT, Perplexity, Claude, Gemini daily. Export the citation log so each row has: date, engine, prompt, your-brand-mentioned (boolean), URL cited.

2

Capture the session: tag every AI-referred page load

JavaScript snippet (covered in the ChatGPT-referrals guide) writes utm_source=[engine]&utm_medium=ai-referral&utm_campaign=[prompt-slug-if-known] before HubSpot's tracking code fires. The campaign param is what later joins citations to sessions.

3

Capture the contact: ensure your form fields preserve UTMs into hidden fields

HubSpot forms can auto-capture UTMs into properties named hs_analytics_first_url, but the cleaner path is hidden form fields bound to hs_form_utm_source / hs_form_utm_campaign. This way the contact record permanently knows which AI prompt drove the form fill.

4

Capture the opportunity: copy contact-level AI properties to the Deal at deal creation

Workflow: Deal created → Get associated primary contact → write contact's ai_source, ai_first_prompt, ai_first_engine to the Deal object. Without this, the link from contact to opportunity is broken at the report level.

5

Capture the deal stage progression: log AI-attribution at each stage transition

Optional but valuable. Workflow: Deal stage changed → if deal_ai_source is not 'none', append to a deal property ai_journey_log: 'YYYY-MM-DD: moved to [stage]'. This lets you see the full timeline from citation → close.

6

Capture closed-won: filter the Deal report on deal_ai_source != 'none' AND stage = Closed Won

This is the report that ties citation back to revenue. Sum of Amount = AEO-attributed ARR. Group by deal_ai_first_engine to see which engine drove the most. Group by deal_ai_first_prompt to see which prompts were most valuable.

7

Close the loop: send the closed-won prompts back to your AEO content team

The single highest-leverage AEO move is rewriting and republishing the prompts that drove closed-won deals — they're the proven money queries. Most teams skip this step and re-do generic content. Build a monthly report of 'top 10 prompts by closed-won ARR' and prioritize content production around it.

Common mistakes

  • Stopping at citation count — citation alone tells you nothing about revenue. The whole chain matters.
  • Forgetting that 80% of B2B AI traffic is anonymous (no form fill) — pair AI source attribution with intent-data tools (Clearbit, 6sense) to widen the captured surface.
  • Tracking only ChatGPT — Perplexity converts at 1.5–2x ChatGPT for B2B because it cites sources more aggressively. Don't ignore it.
  • Using last-touch instead of first-touch attribution — AI-referred buyers often visit 3–5 times before converting; last-touch credits the wrong source.

Where this fits in the AEO pipeline attribution stack

The steps above are one link in a longer chain. In order: you pick prompts to monitor, you track AI-referred sessions, you tag contacts in your CRM, you roll attribution up to the Deal object, you report pipeline dollars to the CFO. If you skip any link, the chain breaks and the number you quote to finance can't be defended in an audit.

If you're still evaluating which tool to run this workflow on, Lantern's AEO tool comparison hub has honest head-to-head pages for Profound, Scrunch, Peec AI, AthenaHQ, and HubSpot's own AEO product — scored on the dimensions that matter for a CMO buyer (CRM integration depth, reporting quality, prompt-scaling economics).

If you're about to walk this work into a budget review, the CFO's Guide to AEO Budget Defense has the memo template, the five-slide deck structure, the attribution-math cheat sheet, and the three most-common CFO objections with counter-arguments. It's the long-form companion to this how-to and was written for the renewal conversation specifically.

The operational rhythm that works: run the steps above once to set up, then review the output monthly in a 15-minute standing meeting with your Head of Growth and RevOps lead. Quarterly, re-audit your prompt list, your content backlog, and your attribution lookback window. Annual: present the full-year AEO ROI trend to the board. That cadence is what separates teams who ship an AEO dashboard once from teams who run AEO as an ongoing budget-defensible channel.

FAQ

Common questions.

Which attribution model should I use for AEO?
Start with first-touch, then graduate to a 40/20/40 W-shaped model (40% first AI citation, 20% middle touches, 40% last touch before close) once you have 30+ AEO-attributed deals. Pure last-touch hides AEO impact because closing deals usually involves a sales rep, not an AI citation.
How long does AEO attribution take to set up?
Manually wired in HubSpot: 8–14 hours of RevOps time. Wired with Lantern: under 30 minutes for the JS snippet + property installation. The expensive part isn't the setup — it's the monthly review discipline.
What's the difference between AI search attribution and pipeline attribution?
AI search attribution = which engine drove the visit. Pipeline attribution = which engine drove the dollar of pipeline / revenue. Pipeline attribution is the strict superset — it requires search attribution plus a CRM rollup.
Does this work with Salesforce?
The same data model translates to Salesforce — you'd build the equivalent of ai_source on the Lead/Contact object and roll up to Opportunity. Lantern's Salesforce integration is V1.5 (Months 4–6 from launch).

Lantern ships this as a monthly report.

Instead of hand-wiring the steps above, Lantern installs the HubSpot properties, the JS snippet, and the pipeline attribution workflow in under 30 minutes — then ships the monthly ROI report your CFO signs off on. $99/mo Starter or Enterprise. 14-day free trial.

Start free trial