Google Consent Mode v2: The GA4 and GTM Technical Guide
If your site runs Google Analytics or Google Ads on European traffic, Google Consent Mode v2 has already…

GA4 conversion tracking works differently than most people expect — and the March 2024 rename from “conversions” to “key events” made the confusion worse, not better. After auditing dozens of GA4 properties, I find the same pattern almost every time: properties that have fifteen “conversions” lighting up daily, none of which connect to an actual business outcome.
This guide covers exactly what changed, what to track, how to mark a key event step by step, and the mistakes that silently corrupt your conversion data. If you’re new to the GA4 event model entirely, read my GA4 event tracking explainer first — that covers how the underlying event system works before you start marking things as conversions.
In March 2024, Google split the single concept of “conversions” into two distinct terms across its analytics stack:
The reason was attribution. Before the change, the same word meant slightly different things in GA4 and Google Ads, and the two platforms used different attribution windows. Advertisers routinely saw mismatched numbers between the platforms and had no clean way to explain the gap.
The practical effect: if you don’t run Google Ads, you’ll work entirely with key events. Nothing about the actual setup process changed. The toggle you used to mark a conversion is the same toggle that marks a key event — only the label is different.
> One thing that hasn’t changed: GA4 only counts key events going forward from when you enable the toggle. There is no retroactive attribution.
The most common GA4 conversion tracking mistake isn’t a technical error — it’s scope creep. Each new event gets promoted to a key event because it feels significant, until the conversion dashboard becomes meaningless.
The distinction that matters is engagement signal versus business outcome. Use this table to separate them:
| Track as a regular event (not a key event) | Mark as a key event |
|---|---|
| Scroll depth 50% or 90% | Form submission (lead) |
| Video play or video complete | Purchase completed |
| Outbound link click | Free trial or account signup |
| File download | Demo or consultation request |
| Add to cart | Subscription activated or plan upgraded |
| Time on page (30s, 60s) | Phone call initiated (click-to-call) |
| Newsletter optin (micro-step) | Confirmed newsletter subscriber (double-opt-in complete) |
The practical limit is 3–5 key events per property for most businesses. More than 7 almost always means micro-conversions have crept into the list. That said, a large e-commerce site tracking multiple checkout stages has legitimate reasons to go higher — the rule is that each key event must represent a direct link to revenue or a qualified lead.
Before touching GA4, answer one question: what action on your website directly generates or leads to revenue? Everything else is supporting data.
There are two paths: marking an existing event in the GA4 interface, or creating a new event from existing conditions. Both take under five minutes once you know where to look.
Use this when the event already fires in GA4 — whether it’s an automatically collected event like purchase, or a custom event you’ve already configured.
generate_lead
The event now appears under Admin > Key events and will be counted in your standard acquisition and conversion reports from that point forward.
Use this when you want to define a conversion from existing event data — for example, treating a visit to a specific “/thank-you” page as a lead confirmation event.
lead_form_completeevent_name equals page_view AND page_location contains /thank-youFor more complex scenarios — button clicks, third-party form submissions, JavaScript-driven interactions — you’ll need Google Tag Manager and its data layer to send the event to GA4 in the first place. GTM gives you trigger-level control that the GA4 interface alone can’t match.
Business model shapes everything here. The “right” conversion events for a content site look nothing like those for an e-commerce checkout. Use this as a starting point:
| Business type | Strong key events | Common vanity mistakes |
|---|---|---|
| E-commerce | purchase, begin_checkout, add_payment_info |
add_to_cart, view_item (track as events, not key events) |
| SaaS / Software | sign_up, trial_start, upgrade_plan |
page_view on pricing page, scroll depth on feature pages |
| Lead generation | generate_lead, form_submit, book_demo |
Outbound link clicks, brochure downloads without follow-up |
| Content / Publishing | paid_subscription, newsletter_signup (confirmed) |
scroll, video_start, time-on-page events |
| Local business | click_to_call, book_appointment, request_directions |
Homepage visits, any page_view event |
Google publishes a reference list of recommended GA4 events that covers standard e-commerce and engagement events — worth bookmarking if you’re defining your event naming scheme.
This is the step that gives the “conversions” label its meaning in the new terminology. When you import a GA4 key event into Google Ads, it becomes a conversion action inside Google Ads — and that’s what drives Smart Bidding, target CPA, and target ROAS optimizations.
The import process works like this:
A few things worth knowing before you do this. First, Google Ads will use its own attribution window once the key event is imported — this won’t match GA4’s attribution exactly, which is where the historical discrepancy between platforms came from. Second, only import key events that represent actions you want to bid toward. Adding a micro-conversion like scroll_90 to Google Ads will teach Smart Bidding to optimize for the wrong signal and inflate your CPA.
Third, the Google tag (gtag.js) reference documents how events sent via gtag interact with both GA4 and Google Ads measurement — useful if you’re running dual-tagging.
A key event that never fires — or fires on every pageload by mistake — is worse than no tracking at all. These three checks take five minutes and should become routine.
1. GA4 Realtime Report
Go to Reports > Realtime. Trigger the conversion action yourself — submit the form, complete a test purchase, or click the call button. The event should appear within seconds in the “Event count by Event name” card. If it doesn’t show up, the event isn’t reaching GA4.
2. GA4 DebugView
Turn on debug mode with Google Tag Assistant or GTM Preview, and then go to Admin > DebugView in GA4. You’ll see a live event timeline with parameters. Key events appear with a green flag indicator.
3. GTM Preview Mode
If you used GTM to send the event, click Preview in the GTM workspace. Complete the conversion action in the browser window that opens. In the debug panel, confirm the tag fired and that the correct event parameters were passed.
> Always test from an incognito window. Browser extensions, logged-in sessions, and cached states can interfere with event firing and produce false positives.
GA4’s conversion tracking is genuinely useful, but it has real constraints that marketing materials tend to gloss over.
Cross-device attribution gaps. GA4 relies on User-ID and Google signals to stitch together cross-device journeys. If you haven’t implemented User-ID for authenticated users, a significant share of multi-device conversions will appear as separate sessions — inflating your unique converters count and undercounting actual conversion rate.
Ad blockers and consent mode. A meaningful share of desktop traffic in some markets runs ad blockers or privacy tools that block the GA4 tag entirely. If you’ve implemented Consent Mode v2, GA4 will model some of the blocked conversions — but modeled data is not the same as measured data, and the confidence interval isn’t shown in the standard reports.
Data-driven attribution requires sufficient volume. GA4’s default attribution model (data-driven) distributes credit across touchpoints based on historical patterns. However, it requires a minimum conversion volume — roughly 300–400 key events over the past 28 days per conversion type — to run the model reliably. Properties below that threshold fall back to last-click attribution without a clear notification in the UI.
Sampled data in exploration reports. The standard acquisition reports show unsampled data. However, the Explorations section (custom funnels, path analysis) applies sampling for large properties. If you’re analyzing conversion funnels for a high-traffic property, be aware that the segment percentages may be estimates rather than exact counts.
These aren’t reasons to abandon GA4 — they’re reasons to know what you’re measuring and what you’re extrapolating. Understanding GA4’s engagement metrics alongside conversion data gives you a fuller picture; my guide to engaged sessions in GA4 explains how to read quality signals alongside conversion counts.
GA4 surfaces key events in several places across the interface:
The Traffic acquisition report with key events added is the single most useful standard report in GA4. It answers the question every business actually cares about: which channels produce results, not which channels produce visits.
GA4 conversion tracking comes down to one decision made well: picking the right 3–5 key events that map directly to business outcomes. The rename from conversions to key events was administrative. The underlying question — what does a successful user action look like on your specific site — hasn’t changed, and getting that definition right matters far more than any technical configuration detail.
Set them up correctly, verify they fire, add monetary values where you know them, and review the list quarterly. GA4 then becomes a tool for decisions rather than a dashboard full of numbers that feel important but aren’t.
For a complete foundation before you configure any of this, the GA4 setup tutorial walks through property configuration from scratch — including the data streams and measurement settings that need to be in place before conversion tracking makes sense.
First published . Last updated .