{
  "slug": "ai-referral-conversion-rate",
  "name": "AI referral conversion rate",
  "aliases": [
    "AI referral CVR",
    "Assistant referral conversion rate"
  ],
  "definition": "The rate at which assistant-referred visitors completed a configured goal. It is a governed measure in the semantic layer with its own denominator, distinct visitors, not sessions, so it is not the conversion count over anything a breakdown hands you.",
  "category": "AI referral traffic",
  "type": "rate",
  "unit": "a 0 to 1 fraction in the semantic layer, formatted as a percent for display",
  "direction": "higher-better",
  "verification": "review",
  "aggregation": "Never average two conversion rates to get a combined rate, and never rebuild it from a session and conversion breakdown, the semantic layer computes it as its own measure, and its denominator is a distinct-visitor estimate while the conversion count is a plain sum.",
  "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"
  ],
  "skills": [
    "search-to-revenue",
    "cross-domain-correlator"
  ],
  "verbs": [],
  "rungs": [
    "R5"
  ],
  "levers": [
    "L7"
  ],
  "questions": [
    "Do assistant referrals convert better or worse than organic search?",
    "What is our conversion rate on AI referral traffic?"
  ],
  "caveats": [
    "Inherits the classification blocker of the whole family, the denominator is a hand-assembled set of traffic-source rows, not a measured channel.",
    "The denominator is distinct visitors, not sessions. A rate rebuilt as conversions over sessions is a different number, and the gap widens as the population shrinks, which is exactly where assistant referrals live.",
    "Assistant volumes are small enough that the rate is dominated by sampling noise; the significance verdict is the thing to read, not the arrow.",
    "The web-analytics feed exposes two conversion-rate measures, one dividing summed conversions by a distinct-visitor estimate, the other averaging a per-row rate column, and they do not agree. Say which one the number came from."
  ],
  "freshness": "loads nightly, a same-day question gets yesterday's number, labelled as yesterday's.",
  "failureModes": [
    "Declaring assistant traffic 'higher intent' from a rate computed on a few dozen visitors.",
    "Reconstructing the rate from a breakdown and getting a different figure from the one the layer returns.",
    "Quoting the two twin rate measures interchangeably."
  ],
  "notSameAs": [
    {
      "slug": "ai-referral-conversions",
      "why": "The count is a sum of goal completions; the rate is a separate measure in the semantic layer with its own denominator, a distinct-visitor estimate, not the sessions or the rows a breakdown gives you. One is not derivable from the other with the numbers to hand, and treating the rate as count-over-sessions is the standard way this family is misread."
    }
  ],
  "related": [
    "ai-referral-sessions",
    "ai-referral-conversions",
    "conversion-rate",
    "conversion-rate-change"
  ],
  "workflows": [],
  "lastVerified": "2026-08-04"
}