ConsentCheck

Why Google Ads Shows 0 Conversions But GA4 Shows Events

You're seeing conversions in Google Analytics 4 (GA4), but Google Ads shows zero conversions. Your conversion tracking code is installed, events are firing, and GA4 is recording everything - but nothing is flowing back to Google Ads. This is one of the most frustrating and common Google Ads tracking problems.

The confusion is understandable: GA4 and Google Ads are both Google products, so you'd expect them to work together seamlessly. But they use different tracking systems, different attribution methods, and different consent requirements. When consent isn't properly configured, GA4 might fire events while Google Ads conversion tracking fails silently.

This problem almost always comes down to consent, timing, or Consent Mode v2 configuration. For a complete breakdown of how consent breaks Google Ads tracking, see why Google Ads conversions break.

Sometimes the difference is not a bug but an attribution model mismatch. See why GA4 and Google Ads show different numbers.

Diagnose Why Conversions Aren't Reaching Google Ads

Run a free diagnostic scan to identify if consent, Consent Mode v2, or conversion tracking configuration is preventing conversions from reaching Google Ads.

Run Free Scan →

The scan checks conversion tracking, consent signals, and identifies exactly why conversions aren't being attributed to Google Ads.

Why GA4 and Google Ads Show Different Results

GA4 and Google Ads are separate systems with different requirements:

GA4 Tracks Events, Not Conversions

GA4 tracks events (like "purchase", "sign_up", "generate_lead") and shows them in real-time reports. GA4 doesn't care about Google Ads attribution - it just records that an event happened on your site.

Google Ads, on the other hand, needs to attribute conversions to specific ad clicks and campaigns. This requires proper consent signals, conversion labels, and attribution data.

Different Consent Requirements

GA4 might fire events even when consent isn't properly configured, because GA4 can work with limited data. Google Ads conversion tracking, however, requires proper Consent Mode v2 configuration to attribute conversions correctly.

Without Consent Mode v2, Google Ads may suppress conversion attribution even if the conversion request is sent. This is why you see events in GA4 but zero conversions in Google Ads.

Different Attribution Windows

GA4 shows events in real-time. Google Ads uses attribution windows (typically 30-90 days) and may take 24-48 hours to process conversions. However, if conversions still don't appear after 48 hours, it's likely a consent or configuration issue, not a delay.

The 5 Most Common Reasons GA4 Shows Events But Google Ads Doesn't

Reason 1: Consent Mode v2 Not Configured

What's happening: GA4 events fire, but Google Ads can't attribute conversions because Consent Mode v2 isn't sending proper consent signals.

Why it breaks: Without Consent Mode v2, Google Ads doesn't know the consent state of users. When consent signals are missing or incorrect, Google Ads may suppress conversion attribution to comply with privacy requirements.

How to check: See how to check Google Consent Mode v2 for step-by-step verification. Or run our diagnostic scan to check automatically.

Reason 2: Consent Updates Don't Fire

What's happening: Consent Mode v2 is initialized (default denied), but consent updates never fire when users accept. GA4 might still track events, but Google Ads can't attribute conversions because consent signals never change to 'granted'.

Why it breaks: Google Ads needs to see consent state updates to know when tracking is allowed. If consent updates don't fire, Google Ads treats all users as non-consented and may suppress conversion attribution.

How to check: Accept consent on your site, then check the browser console for gtag('consent', 'update') calls. If you don't see them, consent updates aren't firing. This is exactly what our diagnostic scan detects automatically.

Reason 3: Conversions Fire Before Consent

What's happening: Conversion events fire before users accept consent. GA4 might record these events, but Google Ads may suppress or not attribute conversions that fire before consent is granted.

Why it breaks: Firing conversions before consent is a violation. Google Ads may suppress these conversions to comply with privacy requirements, even if the conversion request is sent.

How to check: In a fresh incognito window, open DevTools Network tab, filter for pagead, and navigate to a conversion page WITHOUT accepting consent. If you see conversion requests, they're firing before consent. See how to test Google Ads conversion tracking for detailed steps.

Reason 4: Missing or Incorrect Conversion Labels

What's happening: GA4 events fire with generic event names, but Google Ads conversion tracking requires specific conversion labels (e.g., AW-123456789/AbC-dEfGhIj). If conversion labels are missing or incorrect, Google Ads can't attribute conversions.

Why it breaks: Google Ads needs conversion labels to know which conversion action to credit. Without proper labels, conversion requests are sent but not attributed to any campaign.

How to check: In DevTools Network tab, look for conversion requests containing your conversion label. If labels are missing or don't match your Google Ads conversion actions, that's the problem.

Reason 5: Server-Side Tracking Issues

What's happening: If you use server-side conversion tracking (Google Ads API, Measurement Protocol), conversions might be sent from your server but fail due to missing consent signals or incorrect configuration.

Why it breaks: Server-side tracking still requires proper consent signals. If consent data isn't passed correctly from the browser to your server, Google Ads may reject or suppress the conversions.

How to check: Verify that consent signals are being passed correctly in server-side conversion requests. Check your server logs and Google Ads API responses for errors.

The Consent Mode v2 Connection (Most Common Cause)

In most cases, the issue is Consent Mode v2. Here's why:

How Consent Mode v2 Affects Attribution

Consent Mode v2 tells Google Ads what consent state users have granted. When properly configured:

  • Default state is 'denied' (before consent)
  • Consent updates to 'granted' when users accept
  • Google Ads receives consent signals with conversion requests
  • Google Ads can attribute conversions correctly

When Consent Mode v2 isn't working:

  • Consent signals are missing from conversion requests
  • Google Ads doesn't know if consent was granted
  • Google Ads may suppress conversion attribution
  • Conversions appear in GA4 (which doesn't need consent signals) but not in Google Ads

This is why Consent Mode affects Google Ads optimization - without proper consent signals, Google Ads can't attribute conversions, which breaks campaign optimization.

How to Diagnose the Problem

To figure out why conversions aren't reaching Google Ads, check these in order:

Step 1: Check if Conversion Requests Are Being Sent

In a fresh incognito window, open DevTools Network tab, filter for pagead, accept consent, then trigger a conversion. Do you see conversion requests?

  • If yes: Conversion tracking is firing. The problem is likely consent signals or attribution.
  • If no: Conversion tracking isn't firing at all. Check if conversion tags are installed correctly or blocked by consent settings.

Step 2: Check Consent Mode v2 Configuration

Verify that Consent Mode v2 is initialized and consent updates fire when users accept. See how to check Google Consent Mode v2 for detailed steps.

  • If Consent Mode v2 is missing: This is likely the root cause. Google Ads needs consent signals to attribute conversions.
  • If Consent Mode v2 exists but updates don't fire: Consent updates aren't working, which breaks attribution.

Step 3: Check Conversion Request Parameters

In the Network tab, click on a conversion request and check the Payload/Parameters. Look for:

  • Conversion label (should match your Google Ads conversion action)
  • Consent parameters (gcs, gcd)
  • Google Click ID (gclid) if from a Google Ads click

If consent parameters are missing or show 'denied' when they should be 'granted', that's why Google Ads isn't attributing conversions.

Step 4: Check Google Ads Conversion Actions

In Google Ads, go to Tools & Settings → Conversions. Verify that:

  • Conversion actions are set up correctly
  • Conversion labels match what's in your code
  • Conversion actions are enabled and not paused

Common Misconceptions (What It's NOT)

When GA4 shows events but Google Ads doesn't, people often assume it's something else:

Misconception 1: "It's Just a Reporting Delay"

While Google Ads can take 24-48 hours to process conversions, if conversions still don't appear after 48 hours, it's likely not a delay - it's a configuration issue.

Reality: If you see conversion requests in the browser but no conversions in Google Ads after 48 hours, there's a consent or attribution problem.

Misconception 2: "GA4 and Google Ads Use the Same Tracking"

Many people think GA4 and Google Ads share the same tracking system, so if GA4 works, Google Ads should work too.

Reality: They're separate systems. GA4 tracks events; Google Ads attributes conversions to campaigns. GA4 doesn't need consent signals to show events; Google Ads needs them to attribute conversions.

Misconception 3: "The Conversion Code Is Broken"

People assume the conversion tracking code itself is broken or not installed correctly.

Reality: If GA4 is showing events, the tracking code is likely working. The problem is usually consent configuration preventing Google Ads from attributing conversions, not the code itself.

Misconception 4: "It's an Attribution Window Issue"

Attribution windows can be 30-90 days, so people think conversions will appear eventually.

Reality: Attribution windows affect which click gets credit, not whether conversions are recorded. If conversions don't appear at all (not just attributed to the wrong click), it's a consent or configuration issue.

The Business Impact

When conversions appear in GA4 but not in Google Ads, the business impact is significant:

1. Campaign Optimization Breaks

Google Ads' machine learning algorithms optimize based on conversion data. Without conversion data, Google can't optimize bids, targeting, or ad delivery effectively. Campaigns keep running, but performance degrades over time.

2. Budget Wastage

Without conversion data, Google Ads can't identify which keywords, ads, or audiences drive conversions. Budget gets spent on underperforming traffic, while high-converting traffic might be underfunded.

3. Reporting Inaccuracy

You can't accurately measure ROI, CPA, or conversion rates when conversions aren't being recorded. This makes it impossible to make data-driven decisions about campaign optimization.

4. Retargeting Audiences Don't Build

Google Ads remarketing lists require conversion and consent data. Without proper attribution, audiences stay empty or incomplete, breaking remarketing campaigns.

How to Fix It

The fix depends on what's broken, but here are the most common solutions:

Fix 1: Configure Consent Mode v2

If Consent Mode v2 is missing, you need to initialize it. Add this code BEFORE any Google tags load:

gtag('consent', 'default', {
  'ad_storage': 'denied',
  'analytics_storage': 'denied',
  'wait_for_update': 500
});

See how to check Google Consent Mode v2 for complete setup instructions.

Fix 2: Ensure Consent Updates Fire

When users accept consent, you must call:

gtag('consent', 'update', {
  'ad_storage': 'granted',
  'analytics_storage': 'granted'
});

This must fire when users click "Accept" on your consent banner. If it doesn't, Consent Mode v2 won't update, and Google Ads can't attribute conversions.

Fix 3: Prevent Conversions Firing Before Consent

Ensure conversion tags only fire AFTER users accept consent. In Google Tag Manager, set up triggers that check consent state before firing conversion tags.

See how to test Google Ads conversion tracking to verify conversions don't fire before consent.

Fix 4: Verify Conversion Labels

Make sure conversion labels in your code match the conversion labels in Google Ads. Check Google Ads → Tools & Settings → Conversions to get the correct labels.

Why Manual Diagnosis Is Difficult

Diagnosing why GA4 shows events but Google Ads doesn't is complex because:

  • Multiple systems involved - GA4, Google Ads, Consent Mode v2, consent banner, GTM, conversion tags
  • Timing matters - The order of when things fire (consent, tags, updates) affects whether attribution works
  • Consent signals are invisible - You can't easily see consent signals in conversion requests without deep inspection
  • Different user journeys - Behavior varies for users who accept vs reject consent
  • Attribution delays - It's hard to know if conversions are delayed or actually broken

A comprehensive diagnostic scan automates all of these checks, tests behavior across all consent states, and gives you a definitive answer about what's broken and how to fix it. For a complete breakdown of all the ways conversion tracking can break, see why Google Ads conversions break.

Get a Complete Diagnostic

Instead of manually checking each potential issue, run an automated diagnostic scan that checks:

  • If conversion tracking code is detected
  • If conversions fire before consent (violation)
  • If conversions fire after consent (correct behavior)
  • If Consent Mode v2 is configured correctly
  • If consent updates fire when users accept
  • If consent signals are included in conversion requests
  • If tracking behavior is consistent (reject blocks, accept allows)

Diagnose Why Conversions Aren't Reaching Google Ads

Get an automated report that identifies exactly why conversions appear in GA4 but not in Google Ads. The scan checks consent configuration, conversion tracking behavior, and identifies specific fixes.

Run Free Scan →

See a sample report: View sample report →

Related guides:

Part of the Google Ads conversion tracking series:

← Back to: Why Google Ads Conversions Break