Five custom properties on the Deal object, three workflow exports, and a six-tile reporting dashboard layout — the complete AEO attribution scaffold for HubSpot-native B2B SaaS teams. Email-gated, delivered Day 2.
Drop your email. We'll send the full package on Day 2 — custom properties JSON, three workflow exports, the dashboard spec PDF, and a 10-minute setup video. No drip, one email, unsubscribe whenever.
Three components — custom properties, workflows, and the dashboard layout — previewed below. The full package arrives in your inbox on Day 2.
These five properties store the AEO attribution data on each deal. They arrive as a HubSpot JSON export you import directly.
| Internal name | Label | Type | Purpose |
|---|---|---|---|
aeo_first_touch_engine |
AEO First Touch Engine | Dropdown | Which AI engine cited the content (ChatGPT, Perplexity, Claude, Gemini, Other). |
aeo_first_touch_prompt |
AEO First Touch Prompt | Single-line text | The prompt that surfaced your content (e.g. "best AEO tool for b2b saas"). |
aeo_citation_url |
AEO Citation URL | Single-line text | Your URL that was cited — the exact page the AI answer linked. |
aeo_influenced_pipeline |
AEO Influenced Pipeline | Currency | Deal amount if AEO was a touchpoint — populated by Workflow 2. |
aeo_first_touch_date |
AEO First Touch Date | Date | When the AEO touchpoint happened — for lookback windows and trend reporting. |
Each workflow arrives as an importable HubSpot export. Setup per workflow is under five minutes for an admin.
HubSpot does not allow dashboard imports, so the template ships as a PDF spec with tile-by-tile setup instructions. The layout below is the sketch.
The reason most B2B SaaS AEO programs cannot answer the CFO's renewal question is structural, not analytical. The pipeline data is in HubSpot. The AEO visibility data is in Profound, Scrunch, Peec, Otterly, or a spreadsheet. The two systems never meet in the same row, so nobody can say with precision how much pipeline AEO drove last month. The template is the minimum data model to fix that gap — even if you never run a paid AEO tool.
Five custom properties on the Deal object is the minimum honest schema for AEO attribution. Engine, prompt, citation URL, dollar amount, and date. Anything less and you lose the ability to answer "which prompts drove pipeline, on which engine, when." Anything more and you are over-engineering a V1. The template sticks to five.
The three workflows handle the automation that makes the schema usable without manual data entry. Workflow 1 stamps the first-touch AEO data on the contact when traffic arrives from an AI referrer (ChatGPT, Perplexity, Claude, Gemini). Workflow 2 rolls that data up to the deal when the contact converts into an opportunity. Workflow 3 runs the monthly rollup and emails the CMO. Together they make the dashboard maintain itself.
It doesn't detect AI citations that didn't produce a click. If ChatGPT recommends your product but the prospect remembers your brand and comes back direct a week later, HubSpot's referrer tracking won't catch it. This is the single biggest gap in DIY AEO attribution and the specific problem Lantern's V1 is built to solve — inferring AEO influence from direct-traffic patterns, UTM data, and citation monitoring across the four major engines.
It also doesn't dedupe multi-touch journeys across campaigns. If a prospect clicks a ChatGPT citation in January and a LinkedIn ad in March, the template counts the AEO touch as first-touch but doesn't allocate fractional credit across the two. That's fine for V1 reporting — first-touch AEO attribution is honest and defensible — but it's not full multi-touch attribution.
Finally, it doesn't produce the board-ready monthly PDF. The dashboard is the screen version. The PDF — with written context, CFO framing, and renewal defense math — is what Lantern ships on the $99/mo plan. Teams that want both can run the template in parallel with Lantern and use the HubSpot dashboard as the daily view.
Day 1: you email-gate below, we send the template package on Day 2.
Day 2: you receive four files — properties.json, workflow-1.json, workflow-2.json, workflow-3.json, and dashboard-spec.pdf. Plus a 10-minute setup video walking through the import.
Day 3 (30–45 min of admin time): import the properties JSON via HubSpot's bulk property upload. Import each workflow JSON via HubSpot's workflow import. Open a new dashboard in HubSpot and build the six tiles per the PDF spec — each tile has the exact filter string to paste.
Day 4 onward: the properties populate on new traffic automatically. Within 30 days you have your first monthly AEO pipeline rollup email. Within 90 days you have a trend line. Within 12 months you have a defensible year-over-year story.
For the full math behind the renewal defense this template supports, see the CFO's Guide to AEO Budget Defense. For tool comparisons to decide whether to run Lantern, Profound, Scrunch, or Peec alongside this template, see Lantern's compare pages.
Lantern's $99/mo plan populates all five custom properties every time an AI citation lands a deal in HubSpot — plus ships the board-ready PDF. Enterprise for larger teams.
Join Waitlist