HubSpot UTM Parameters for AEO: the canonical AI engine taxonomy

What this does

Most teams invent their own UTM taxonomy for AI traffic ad-hoc — some use utm_source=openai, others utm_source=chatgpt, others utm_source=ai. This fragmentation makes reports ugly and cross-team analysis impossible. Lantern publishes (and auto-applies) a canonical taxonomy: utm_source = engine lowercase, utm_medium = ai-referral, utm_campaign = prompt-category-when-known.

How Lantern fits

Lantern's JS snippet applies this taxonomy automatically. If your team already uses a different taxonomy, Lantern can translate on ingest (configurable in install). The recommended default: utm_source=chatgpt|perplexity|claude|gemini, utm_medium=ai-referral, utm_campaign=aeo-[category]. Consistent taxonomy means HubSpot reports group cleanly, CMO questions get clean answers.

Setup preview

Four UTM slots in HubSpot — utm_source, utm_medium, utm_campaign, utm_content, utm_term. Lantern uses the first three; utm_content and utm_term remain available for your paid ads and other campaigns. This means AEO data never collides with existing UTM investment — you can run Google Ads, LinkedIn Ads, and Lantern's AEO attribution side by side without conflict.

// Lantern canonical UTM taxonomy for AI engines
const LANTERN_UTM_MAP = {
  'chat.openai.com':    { source: 'chatgpt',    medium: 'ai-referral' },
  'chatgpt.com':        { source: 'chatgpt',    medium: 'ai-referral' },
  'openai.com':         { source: 'chatgpt',    medium: 'ai-referral' },
  'perplexity.ai':      { source: 'perplexity', medium: 'ai-referral' },
  'www.perplexity.ai':  { source: 'perplexity', medium: 'ai-referral' },
  'claude.ai':          { source: 'claude',     medium: 'ai-referral' },
  'gemini.google.com':  { source: 'gemini',     medium: 'ai-referral' },
  'bard.google.com':    { source: 'gemini',     medium: 'ai-referral' },
  'bing.com/chat':      { source: 'bing-chat',  medium: 'ai-referral' },
  'copilot.microsoft.com': { source: 'copilot', medium: 'ai-referral' },
  'you.com':            { source: 'you-com',    medium: 'ai-referral' },
  'arc.net':            { source: 'arc-search', medium: 'ai-referral' }
};

// Campaign category optionally derived from landing URL
function campaignFromPath(path) {
  if (path.includes('/compare/')) return 'aeo-comparison';
  if (path.includes('/learn/'))   return 'aeo-glossary';
  if (path.includes('/aeo-for/')) return 'aeo-vertical';
  if (path.includes('/blog/'))    return 'aeo-content';
  return 'aeo-other';
}

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.