Google Ads Shows 0 Conversions But GA4 Does? (Your Tracking Is Broken)

This is one of the most expensive tracking issues in Google Ads. It silently breaks optimization while campaigns keep spending.

If GA4 shows conversions but Google Ads shows 0, your tracking is broken.

This means:

Google Ads can't optimize your campaigns
Budget is being misallocated
You're likely losing conversions right now

In most cases, this is caused by consent mode or attribution issues.

You can debug it manually below — or check your setup instantly:

🔍 Run Free Tracking Scan →

For a full breakdown of consent and timing failure patterns, see why Google Ads conversions break.

Quick Answer

If GA4 shows events but Google Ads shows 0 conversions, the issue is almost always:

Consent Mode v2 not configured correctly
Consent not updating after user interaction
Conversions firing before consent
Missing consent signals (gcs / gcd)

This is one of the most common issues we detect in real-world audits. If it persists beyond 48 hours, your Google Ads tracking is broken.

Most sites with this issue have broken consent mode or missing signals.

Run a quick scan to see exactly what's wrong:

Check My Tracking →

Is This Normal or a Problem?

Normal: small differences from attribution models or short reporting delays
Not normal: GA4 conversions while Google Ads stays at zero after 48 hours

If you are in the second scenario, treat this as a setup issue, not a reporting nuance.

Find exactly why conversions aren't reaching Google Ads

Scan your site and detect:

Missing consent signals
Broken conversion tags
Attribution issues blocking Google Ads

🔍 Run Free Scan →

Built like a diagnostic tool, flags what's wrong so you can fix or escalate fast.

Urgent checks in order

Verify conversion requests are actually sent on real conversion steps.
Confirm consent updates fire and request payloads include valid consent signals.
Check conversion labels and action settings in Google Ads.
Only then review attribution windows/reporting delays.

What Google Ads Needs (That GA4 Doesn't)

Google Ads requires additional attribution signals that GA4 does not always require:

gclid (Google Click ID)
gcs (consent state)
gcd (consent details)

GA4 can record events without full ad attribution context. Google Ads cannot attribute conversions reliably without these signals.

If this issue appeared after a release or CMP change, consent mode may have stopped working after an update.

GA4 vs Google Ads Tracking

Feature	GA4	Google Ads
Tracks events	Yes	No
Needs consent signals	Partial	Critical
Works without gclid	Often	No

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. We recovered a 40% conversion drop from this issue. See our case study.

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.

These issues are hard to detect manually.

Run a scan to identify which one is affecting your site:

Diagnose My Tracking →

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

Quick Debug Flow

Do you see conversion requests in DevTools? If no, tracking is not firing.
Do requests include gcs/gcd? If no, Consent Mode implementation is broken.
Do requests include the correct conversion label? If no, label/setup issue.
If yes to all three, verify Google Ads conversion action settings.

Manual debugging can take hours.

Get a full report in seconds:

Run Free Diagnostic →

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.

This can directly cost campaign performance

If these symptoms match your setup, run a full scan now to pinpoint where attribution is breaking.

Diagnose My Setup →

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.

Find What's Broken →

See a sample report: View sample report →

Related guides:

Part of the Google Ads conversion tracking series:

← Back to: Why Google Ads Conversions Break

Related guides:

Advanced setup: Server-side GTM + Consent Mode v2