Przejdź do treści
whitead

Conversion Tracking

słownik google ads zaktualizowano 2026.04.29 6 min czytania
// contents · 9 sekcji
  1. What conversion tracking measures
  2. The 2026 conversion stack
  3. Conversion actions vs goals vs values
  4. Common misconceptions
  5. "A generic JS pixel is enough."
  6. "GA4 conversion import equals a direct conversion tag."
  7. "Google Ads count doesn't match GA4. Which is right?"
  8. Related concepts
  9. Sources

Conversion tracking ties Google Ads spend to business outcomes. In 2026 it is no longer a pixel — it is Google Tag, Enhanced Conversions, Consent Mode v2.

What conversion tracking measures

Conversion tracking records a defined business action — purchase, qualified lead, call, app install — and credits it to the click that produced it. The credit travels with the GCLID on the landing-page URL and matches at the conversion event when the Google Tag fires. Without the match, Google Ads sees only clicks and cost; automated bidding has no signal to optimize against and ROAS becomes a guess.

Three primitives drive everything downstream: conversion action (the rule), conversion goal (campaign-level grouping), conversion value (monetary or proxy weight). Misconfigure them and bidding, attribution, and audits inherit the error.

  1. Install the Google Tag via Tag Manager and confirm the base tag fires on every page.
  2. Create one Primary conversion action for your macro-conversion (purchase or qualified lead).
  3. Turn on Enhanced Conversions and wire a real email/phone field — aim for a ≥70% match rate.
  4. Enable Consent Mode v2 (Advanced) for EEA/UK/CH traffic.

The 2026 conversion stack

Treat conversion tracking as a layered system. Each layer recovers signal the previous one lost:

  1. Google Tag (gtag.js) via Google Tag Manager — base tag fires on every page; conversion events fire on success URLs or DataLayer pushes. Replaces the legacy conversion.js pixel.
  2. Enhanced Conversions — sends SHA-256-hashed first-party data (email, phone, name, address) alongside the conversion ping. Google matches the hash to logged-in user state and recovers conversions ITP/cookie loss would drop. Enhanced Conversions for Web typically lifts measured conversions by +5-25% (Google Ads Help, 2025-08).
  3. Consent Mode v2 — when a user denies cookie consent, the tag fires cookieless pings that Google models. Advanced mode is mandatory for EEA/UK/CH traffic since 2024-03; the enforcement wave on 2025-07-21 began suppressing audiences and modeled conversions for non-compliant accounts.
  4. Server-side tagging (sGTM) — moves the tag from browser to a first-party endpoint on your domain. Bypasses ad-blockers, extends cookie lifetime past Safari ITP's 7-day cap, scrubs PII before forwarding.
  5. Offline Conversion Import (OCI) → Data Manager — for B2B funnels where the real conversion fires in the CRM, GCLID + hashed email flow back via Google Ads Data Manager. Salesforce's legacy native integration sunset 2025-05-31.

Layers are additive. Skipping Consent Mode v2 in EEA traffic alone can erase ~40% of modeled conversions (Conversios, 2025-10).

Conversion actions vs goals vs values

Auditors confuse these three constantly, which is why findings list them first.

Concept What it is Common mistake
Conversion action A single rule (e.g., "Purchase", "Lead form submit") with category, count rule, attribution model, value. Set under Tools → Conversions. Marking every micro-event as Primary, polluting the bidding signal.
Conversion goal Campaign-level bundle of actions used as the optimization target. Leaving "Use account default" then wondering why a lead-gen campaign optimizes for purchases.
Conversion value Currency or proxy amount attached to an action. Powers tROAS and Maximize Conversion Value. Hard-coding 1.00 for every lead, then running tROAS.

A new conversion action is defined by four fields — schematically:

  • Conversion action name
  • Category (Purchase, Lead, …)
  • Value
  • Count (Every / One)

"Set up conversion tracking before you launch your campaigns. If you wait, your bid strategies have no data to learn from."
— Google Ads Help, Set up conversion tracking (accessed 2026-04-29)

Primary actions feed Smart Bidding; Secondary are observed-only. Audit pattern: one Primary per macro-conversion (purchase OR qualified lead), micro-events as Secondary.

Common misconceptions

"A generic JS pixel is enough."

No. A pixel-only setup against 2026 browsers (Safari ITP, Firefox ETP, Chrome Privacy Sandbox) loses 15-30% of conversions before they reach Google Ads, with no path to recover EEA users on Consent Denied. Sufficient in 2019; a measurement floor in 2026.

"GA4 conversion import equals a direct conversion tag."

No. GA4-imported conversions arrive with GA4's attribution and session-stitching applied — delayed 24-48h, deduped, stripped of cross-device matching the native tag preserves. Use as backup, not primary.

Both are right for what they measure. Google Ads counts ad-click-credited conversions (30-day window, click-based, cross-device). GA4 counts session-scoped events (90-day window, data-driven). Expect 10-30% gap. Above 40%, you have a tagging problem.

Methodology note. In Whitead audits, broken or partial conversion tracking is a recurring high-severity finding — and almost always invisible from the inside because the account "shows conversions". We diagnose it by triangulating three signals: (1) the Primary conversion action's category and count rule against the actual macro-conversion (purchase / qualified lead) — a Primary tied to a low-intent micro-event causes Smart Bidding to chase noise; (2) Enhanced Conversions match rate in the diagnostics tab — Google's published guidance is to aim for ≥70% match rate (Google Ads Help), and a UI toggle without a wired-up email/phone field typically reads far lower; (3) Consent Mode v2 status on EEA/UK/CH traffic — Basic mode silently suppresses modeled conversions and Customer Match audiences post-2024-03 enforcement. Fix-priority logic mirrors the layered stack above: stand up the Google Tag first, prove the Primary fires, layer Enhanced Conversions, then Consent Mode v2, then server-side tagging only when the first four are clean — each layer compounds, so skipping one degrades every layer that depends on it.

Sources

// czy to było pomocne?
// anonimowo · nie zapisujemy danych osobowych
← Wróć do Wiki