KB 02 — UTM → CRM (HubSpot) Attribution (the plumbing doc)
Serves decisions: D3 (Google fills lost before HubSpot), D4 (fix click→UTM→HubSpot). Dated: 2026-07-17. Cites 01-CANON.md.
1. The chain from ad click to a reportable deal
ad click (carries gclid/li_fat_id/rdt_cid + utm_*)
→ landing page (query string MUST survive all redirects)
→ form submit (UTMs captured into hidden fields → custom contact properties)
→ HubSpot classifies Original Source (Paid Search / Paid Social)
→ lifecycle workflows must NOT overwrite source
→ contact ↔ deal association
→ multi-touch attribution report (Pro/Enterprise)
A break at any arrow sends the lead to Offline / Direct / Organic and it disappears from paid reporting.
2. Why paid leads land in "Offline" (HubSpot's mechanism)
HubSpot sets Original Source from the full URL + referrer at first touch. Offline Sources is the catch-all for records it can't tie to a tracked web session — imports, API, integrations, manual entry, phone/in-person. Paid leads fall here (or Direct/Organic) when the click wasn't tagged, the tracking cookie/session was lost, or UTMs never reached the form. HubSpot traffic sources (updated 2026-06-25). This is precisely MSAI's 8,634 "Offline" of 8,911, only 4 paid-attributed.
Note (2026): HubSpot added an AI Referrals source bucket (ChatGPT/Claude/Perplexity). Multi-touch attribution reporting requires Marketing Hub Pro/Enterprise — MSAI's Pro-tier limitation is why Alecia hand-builds attribution via Campaign Influence lists.
3. Why GA4 can see a conversion that HubSpot never books (the D3 leak)
Google auto-tags with gclid, so GA4 often does register Google form-fills (MSAI: 7). They fail to reach HubSpot pipeline when:
- UTMs aren't captured into contact properties. HubSpot doesn't natively store all UTMs — you must create custom contact properties per UTM param and capture them via hidden form fields. HubSpot tracking URL; HubSpot Ads (2026-01-10).
- Source mapping is broken so paid resolves to Offline/Direct rather than Paid Search.
- A lifecycle/MQL workflow re-stamps Original Source on stage change (a common silent clobber) — audit any workflow that writes Original Source.
- The HubSpot Ads connection is broken/absent so clicks never map to contacts/deals (MSAI: LinkedIn 0 contacts/0 deals, ROI blank). The Ads tool only maps clicks after auto-tracking is enabled, with network exclusions (PMax/YouTube, LinkedIn Message/Thought-Leader/Document ads). The fix is traced by following one of the 7 fills end-to-end and finding the first arrow where source is lost.
4. GA4 channel classification (fix at the source)
GA4's Paid Social/Paid Search require a paid utm_medium (cpc|ppc|paid*|retargeting). A LinkedIn ad tagged utm_medium=social or =linkedin fails the regex and lands in Organic Social — MSAI's 26-Paid-Social-sessions anomaly. Custom channel groups fix only the report view; the durable fix is correct UTMs at the source. GA4 is case-sensitive (Facebook≠facebook). Google GA4 channel group. GA4 attribution is now Data-Driven by default (four rule-based models deprecated), so it will never tie out 1:1 with single-touch platform counts. MeasureSchool 2025-02-14.
5. The UTM standard (lock it once, apply everywhere)
All-lowercase, hyphen-separated, fixed vocabulary. Source = platform; medium = channel-type from a fixed list, never the platform name. DigitalApplied 2026.
| Param | Rule | Example |
|---|---|---|
| utm_source | platform, lowercase | linkedin google reddit |
| utm_medium | fixed vocab | paid-social cpc paid-display |
| utm_campaign | [channel]-[program]-[YYYYMM] |
linkedin-abx-202607 |
| utm_content | creative variant | abx-hero-a |
| utm_term | keyword (paid search) | condition-monitoring |
Full example: https://multisensorai.com/demo?utm_source=linkedin&utm_medium=paid-social&utm_campaign=linkedin-abx-202607&utm_content=abx-hero-a
QA rule: before any campaign goes live, pull every final URL and diff against the standard. One inconsistent utm_medium fragments the whole channel. (This standard already exists in MSAI's internal Lead Source Attribution Cleanup Tracker, tab "UTM Standard" — align to it.)
6. Target-state source map (HubSpot)
| Channel | HS Original Source | utm_medium | Rule |
|---|---|---|---|
| LinkedIn Ads | Paid Social | paid-social | utm_source=linkedin + paid-social |
| Google Search | Paid Search | cpc | GCLID auto-tag ON; verify GCLID+UTM don't collide |
| Google Display | Paid Search | paid-display | |
| Reddit Ads | Paid Social | paid-social | separated from LinkedIn by utm_source=reddit |
| Organic social | Organic Social | social | must NOT catch paid |
| Direct/unknown | Direct Traffic | (none) | paid landing here = tagging failure |
| Offline | Offline Sources | — | true offline only; paid must never land here |
7. Reconcile three views, don't force a match
Ad-platform clicks (click-date) ≠ GA4 sessions (conversion-date) ≠ CRM contacts. Order-of-magnitude gaps come from ad-blockers/consent (~30%), bots (counted by GA4, filtered by CRM), cross-device, window mismatch (90-day click vs 30-min session), and pre-tag bounce. Triangulate to a tolerance with CRM/revenue as source of truth; track platform-to-platform ratios over time. Search Engine Land 2026-05-11.
8. The fix, sequenced (do not scale spend until done)
Mirrors MSAI's internal tracker phases:
- Phase 1 — tag at source: lock UTM standard → apply to every LinkedIn, then Google (confirm GCLID+UTM coexist), then Reddit final URL → QA live links.
- Phase 2 — HubSpot source map: fix Original Source drilldowns; create custom UTM properties + hidden form fields; register tracking URLs; wire orphan paid Campaign Influence lists to campaign objects.
- Phase 3 — conversions & reconcile: set high-intent actions to Primary; add CAPI/server-side; confirm GA4 buckets paid correctly; three-way reconciliation; validate with 1-2 live test conversions (the acceptance test).
- Phase 4 — attribution & restart: widen to multi-touch; stand up a drift-alert workflow (flag any new paid-pattern contact landing as Offline); best-effort re-attribute the ~8,600 back-catalog into a separate clean property (never overwrite native Original Source); then resume channel ROI reporting. Durable layer: server-side GTM + CAPIs so this survives cookie deprecation (KB 01 §3).