HubSpot Service Hub AEO: closing the loop with post-sale citation data

What this does

AEO attribution usually stops at closed-won. But AI-sourced customers may behave differently than SEO-sourced customers post-sale — different activation rates, different NPS, different churn. Lantern propagates ai_source from Contact to the Ticket and Feedback objects in Service Hub, letting CS teams segment their post-sale data by original acquisition source.

How Lantern fits

On Service Hub install, Lantern extends three objects with ai_source inheritance: Tickets (ai_source copied from the ticket's primary contact), Feedback Surveys (ai_source copied from the respondent), Custom Service Objects (configurable). Reports built on Service Hub now split by ai_source — revealing patterns like 'ChatGPT-sourced customers have 2x higher NPS' or 'Perplexity-sourced customers churn at 40% lower rate'.

Setup preview

Service Hub integration is opt-in (off by default — CS teams are often last to adopt). Turn on in Lantern settings, and on next sync Lantern propagates ai_source to tickets and feedback. Requires Service Hub Starter or higher (no Free tier). Retroactive propagation covers 90 days of historical tickets by default; longer lookback available on Enterprise.

// Lantern Service Hub: propagate ai_source to tickets
// Runs on ticket created via workflow

function propagateAISourceToTicket(ticket) {
  const primaryContact = ticket.associations.contacts[0];
  if (!primaryContact) return;

  const aiSource = primaryContact.properties.ai_source;
  const aiEngine = primaryContact.properties.ai_engine;

  if (!aiSource) return; // Not an AI-sourced customer

  // Update ticket with ai_* properties (copied from contact)
  return hubspotClient.crm.tickets.basicApi.update(ticket.id, {
    properties: {
      ai_source: aiSource,
      ai_engine: aiEngine,
      ai_customer_acquisition_source: aiSource  // custom property
    }
  });
}

// Report: Ticket volume split by AI source
// HubSpot custom report on Tickets, group by ai_source, count:
//   chatgpt:    2,240 tickets (4.1 per customer)
//   perplexity:   890 tickets (3.2 per customer)
//   claude:       310 tickets (2.8 per customer)
//   none (SEO):  5,400 tickets (5.1 per customer)

Where this fits in the bigger picture

This page describes one specific surface inside HubSpot where Lantern's AEO pipeline attribution plugs in. The full integration stitches together across HubSpot Contacts, Deals, Workflows, Lists, Reports, Forms, CMS, and the Marketing/Sales/Service Hub stack. If you're evaluating where to start, the comparison hub has side-by-side comparisons of Lantern against 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 renewal review or budget conversation, 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 that translates the technical HubSpot setup on this page into a defensible dollar number for finance.