How to Test Google Ads Conversion Tracking After Consent

You've set up Google Ads conversion tracking, installed the code, and conversions are showing in Google Ads - but are they actually firing correctly after users accept consent? Many sites discover that conversions appear to work in testing, but fail silently in production because consent isn't properly configured or conversion tags fire before consent is granted.

This guide shows you exactly how to test if Google Ads conversion tracking works after consent, what to look for in browser DevTools, and how to verify that conversions are being attributed correctly. If you're seeing conversions in GA4 but not in Google Ads, this is likely the issue. See why Google Ads shows 0 conversions but GA4 shows events for the full explanation.

Manual testing is useful, but it only shows you one scenario. For a complete diagnostic that checks conversion tracking across all consent states and identifies configuration issues, run our free scan.

Test Conversion Tracking Automatically

Run a free diagnostic scan to verify conversion tracking works after consent, check if conversions fire before consent (violation), and identify any configuration issues.

Run Free Scan →

The scan checks conversion tracking detection, behavior before/after consent, and whether conversions are blocked by consent issues.

Why Testing Conversion Tracking After Consent Matters

Google Ads conversion tracking can appear to work in several ways that are actually misleading:

The GA4 vs Google Ads Confusion

Many sites see conversions in Google Analytics 4 (GA4) and assume Google Ads conversion tracking is working. But GA4 and Google Ads use different tracking systems. GA4 might fire events, but if Consent Mode v2 isn't configured correctly, those events never reach Google Ads for attribution.

This is why Google Ads shows 0 conversions but GA4 shows events - the tracking code exists, but consent configuration prevents proper attribution.

The "Works in Testing" Problem

Conversion tracking might work perfectly when you test it manually (you're logged in, cookies are already set, consent was granted previously). But for new users who haven't accepted consent yet, or users who reject cookies, conversions may not fire or attribute correctly.

The Silent Failure

Google Ads might show some conversions, leading you to think everything is working. But if conversions only fire for users who accepted consent, and 30% of users reject cookies, you're losing 30% of conversion data - and Google Ads is optimizing on incomplete information.

Method 1: Test in Browser DevTools (Network Tab)

The most reliable way to test if conversion tracking fires after consent is to monitor network requests in real-time.

Step 1: Open a Fresh Browser Session

Open your website in a new incognito/private window. This simulates a new user with no existing cookies or consent state. This is critical - testing in a regular browser window where you've already accepted consent won't show you the real behavior.

Step 2: Open DevTools Network Tab

Press F12 (Windows/Linux) or Cmd+Option+I (Mac) to open DevTools. Go to the Network tab and check "Preserve log" so requests don't disappear when the page loads or navigates.

Step 3: Filter for Google Ads Requests

In the filter box, type pagead or doubleclick to see Google Ads-related requests. You should see requests to domains like:

google.com/pagead
doubleclick.net
googlesyndication.com

Step 4: Accept Consent

Click "Accept" or "Allow" on your consent banner. Watch the Network tab - you should see new Google Ads requests appear after accepting consent. If no requests appear, conversion tracking might not be firing.

Step 5: Trigger a Conversion

Navigate to a page where conversions should fire (e.g., thank-you page, checkout completion). Watch the Network tab for conversion tracking requests.

What to look for:

Requests containing your conversion label (e.g., AW-123456789/AbC-dEfGhIj)
Requests with event=conversion parameter
Requests sent to google.com/pagead/conversion

If you see these requests after accepting consent, conversion tracking is firing. If you don't see them, conversions aren't firing - which could be due to consent configuration, timing issues, or the conversion tag not being installed correctly.

Method 2: Check Conversion Requests in Payload

Once you see conversion requests in the Network tab, you need to verify they contain the correct consent signals.

Step 1: Click on a Conversion Request

In the Network tab, click on a request that looks like a conversion (contains your conversion label or "conversion" in the URL).

Step 2: Check Request Headers and Parameters

Go to the "Payload" or "Query String Parameters" tab. Look for:

label - Your conversion label (e.g., AW-123456789/AbC-dEfGhIj)
value - Conversion value (if configured)
currency_code - Currency (if configured)
gclid - Google Click ID (if from a Google Ads click)

If these parameters are present, the conversion request is being sent. However, this doesn't guarantee it will be attributed - Google Ads also needs proper consent signals.

Step 3: Verify Consent Signals

Check if the request includes consent parameters:

gcs (Google Consent State) - Should show consent signals
gcd (Google Consent Default) - Should show default states

If consent parameters are missing or show 'denied' when they should be 'granted', Consent Mode v2 isn't working correctly, and Google Ads may not attribute the conversion even though the request was sent.

Method 3: Test with GTM Preview Mode

If you're using Google Tag Manager, GTM Preview mode can help you see if conversion tags fire, but it has limitations for consent testing.

Step 1: Enable GTM Preview Mode

In Google Tag Manager, click "Preview" and enter your website URL. This opens your site in a new window with GTM debugging enabled.

Step 2: Check Tag Firing

Navigate to a conversion page. In the GTM Preview panel, you should see your conversion tag listed. If it shows "Fired", the tag is executing.

Important limitation: GTM Preview shows that tags fire, but it doesn't tell you if:

The conversion request actually reached Google Ads
Consent signals were included in the request
Google Ads will attribute the conversion

This is why conversions can appear in GA4 or GTM Preview but never reach Google Ads - the tag fires, but consent configuration prevents proper attribution.

Note: Google Ads reporting delays and attribution windows are not considered tracking failures. Conversions may take 24-48 hours to appear in Google Ads, and attribution windows can be 30-90 days. This test checks technical behavior, not reporting delays.

Method 4: Test Before vs After Consent

The most important test is verifying that conversions DON'T fire before consent (violation) and DO fire after consent (correct behavior).

Test 1: Before Accepting Consent

In a fresh incognito window, open DevTools Network tab, filter for pagead, and navigate to a conversion page WITHOUT accepting consent.

Expected behavior: You should NOT see conversion tracking requests. If you do see them, conversions are firing before consent - which is a violation and means Google Ads may suppress or not attribute those conversions.

Test 2: After Accepting Consent

In the same session, accept consent, then navigate to a conversion page (or trigger the conversion event).

Expected behavior: You SHOULD see conversion tracking requests. If you don't see them, conversions aren't firing after consent - which could be due to:

Consent Mode v2 not updating when users accept
Conversion tags not configured to fire after consent
Timing issues (tags fire before consent updates complete)

Test 3: After Rejecting Consent

In a fresh session, reject/decline consent, then navigate to a conversion page.

Expected behavior (with Consent Mode v2): You might see conversion requests, but they should include consent signals indicating 'denied'. Google can model these conversions if Consent Mode v2 is properly configured. Without Consent Mode v2, you shouldn't see conversion requests at all (tracking should be blocked).

Common Issues You Might Discover

When testing conversion tracking after consent, you might discover several common problems:

Issue 1: Conversions Fire Before Consent

You see conversion requests in the Network tab before accepting consent. This is a violation - conversions should only fire after users grant consent.

Why it happens: Conversion tags are configured to fire on page load or too early in the user journey, before consent is collected. This is one of the most common tracking before consent issues.

Issue 2: Conversions Don't Fire After Consent

You accept consent, but no conversion requests appear when you trigger a conversion. The conversion tag exists, but it's not firing.

Why it happens: Conversion tags might be blocked by consent settings, Consent Mode v2 isn't updating when users accept, or tags are configured incorrectly in GTM.

Issue 3: Conversions Fire But Aren't Attributed

You see conversion requests in the Network tab, but they don't appear in Google Ads. The requests are being sent, but Google Ads isn't crediting them to your campaigns.

Why it happens: Consent signals are missing or incorrect in the conversion requests. Without proper consent signals, Google Ads may suppress conversion attribution. This is why Google Ads shows 0 conversions but GA4 shows events.

Issue 4: Conversions Only Work for Some Users

Conversions fire for users who accept consent, but not for users who reject. Without Consent Mode v2, you lose conversion data for all users who reject cookies.

Why it matters: If 30% of users reject cookies, you're losing 30% of conversion data. Google Ads optimizes on incomplete information, reducing campaign performance.

What to Check in Google Ads (After Testing)

After you've verified that conversion requests are firing correctly in the browser, check Google Ads to see if conversions are being attributed:

Check 1: Conversion Actions

Go to Google Ads → Tools & Settings → Conversions. Check if your conversion actions are set up correctly and have the right conversion labels.

Check 2: Recent Conversions

In the Conversions section, look for recent conversions. Note that conversions can take 24-48 hours to appear in Google Ads, so don't expect immediate results.

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

Check 3: Conversion Value and Attribution

Verify that conversion values are being recorded correctly (if you're tracking value) and that attribution windows are set appropriately. Remember that attribution windows can be 30-90 days, so conversions might be attributed to clicks from weeks ago.

Why Manual Testing Has Limitations

Manual testing is useful for understanding how conversion tracking works, but it has significant limitations:

Time-consuming - Testing multiple scenarios (before consent, after accept, after reject) takes significant time
Only shows one scenario - You're testing one user journey, not all possible paths
Misses timing issues - You might miss cases where conversions fire too early or too late
Doesn't check all pages - Conversion pages might be on different URLs (checkout, thank-you) that you need to test separately
Can't verify consent signals - You can see requests fire, but verifying consent signals in requests requires deeper inspection
Doesn't check server-side tracking - If you use server-side conversion tracking, browser testing won't catch those issues

A comprehensive diagnostic scan automates all of these tests, checks behavior across the entire user journey, and gives you a complete picture of what's working and what's broken. For a full breakdown of all the ways conversion tracking can break, see why Google Ads conversions break.

Next Steps: Get a Complete Conversion Tracking Diagnostic

Manual testing helps you understand conversion tracking, but for a complete diagnostic that checks all scenarios automatically, run our free scan. The scan verifies:

If conversion tracking code is detected
If conversions fire before consent (violation)
If conversions fire after consent (correct behavior)
If conversions are blocked by consent issues
If Consent Mode v2 is configured correctly
If consent updates fire when users accept

Run a Complete Conversion Tracking Diagnostic

Get an automated report that tests conversion tracking across all consent states, identifies configuration issues, and shows exactly where conversions are breaking. No manual DevTools work required.

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