{
  "slug": "ai-referral-conversions",
  "name": "AI referral conversions",
  "aliases": [
    "Assistant referral conversions",
    "AI-sourced conversions"
  ],
  "definition": "Completions of your configured analytics goals on sessions that arrived from an AI assistant.",
  "category": "AI referral traffic",
  "type": "raw measure",
  "unit": "conversions",
  "direction": "higher-better",
  "verification": "review",
  "aggregation": "The underlying conversion measure sums across rows, unlike the visitor and session measures beside it, which are distinct-count sketches, which is exactly why a conversion rate cannot be reassembled from a breakdown of the two.",
  "grain": "One traffic-source value (or the whole-domain total) for one date range.",
  "dimensions": [
    "source/medium",
    "landing page",
    "goal",
    "country",
    "device"
  ],
  "requiredFilters": [
    "date range"
  ],
  "sources": [
    "web-analytics"
  ],
  "reports": [
    "ai-referral-traffic-report",
    "search-to-revenue-report"
  ],
  "skills": [
    "search-to-revenue",
    "cross-domain-correlator",
    "monthly-exec-review"
  ],
  "verbs": [],
  "rungs": [
    "R5"
  ],
  "levers": [
    "L7"
  ],
  "questions": [
    "Do AI referral visits convert?",
    "How many conversions came from AI assistants last month?",
    "Which goals do assistant visitors complete?"
  ],
  "caveats": [
    "Inherits the whole classification problem of the sessions metric: with no assistant classifier, the population being converted is assembled by hand.",
    "Which goals are counted is a per-property configuration, so the same metric name means different things on two tenants, name the goals beside the number.",
    "Assistant-referred volumes are small on most sites, so a conversion count can move by a large percentage on a handful of events."
  ],
  "freshness": "loads nightly, a same-day question gets yesterday's number, labelled as yesterday's.",
  "failureModes": [
    "Attributing a conversion to an assistant when the analytics property is on last-click and the assistant was only the first touch.",
    "Comparing this against the ad platform's own conversion count, which is measured on a different model entirely."
  ],
  "notSameAs": [
    {
      "slug": "ai-referral-conversion-rate",
      "why": "The rate is its own measure in the semantic layer, not this count divided by anything you have to hand. Dividing a summed conversion count by a distinct-count session figure from a breakdown produces a different number from the rate the layer returns, and the two diverge most where the traffic is smallest, which is where assistant referrals live."
    }
  ],
  "related": [
    "ai-referral-sessions",
    "ai-referral-conversion-rate",
    "conversions-count",
    "per-goal-conversions"
  ],
  "workflows": [],
  "lastVerified": "2026-08-04"
}