How to Check if Your Google Ads Conversion Tracking is Working

There is nothing worse in digital marketing than spending thousands of euros on a Google Ads campaign, only to realize your conversion tracking has been broken for weeks. You are either optimizing campaigns using ghost data, or worse, reporting zero results to your stakeholders when sales are actually happening.

Testing your tracking shouldn't involve crossing your fingers and buying your own product to see if it registers tomorrow. Here is the exact step-by-step framework to audit your Google conversion tags in real time using Google's native debugging suite.

Step 1: Verify the Conversion Action Status

Before diving into code, check the health indicators inside your Google Ads dashboard. Navigate to Goals > Conversions > Summary.

Look at the 'Status' column for your primary conversion action:

• Active / Recording Conversions: Google has successfully spotted your tag firing within the last 7 days. This is a great sign, but it doesn't guarantee your values or parameters are mapping correctly.

• No Recent Conversions: The tag is installed correctly, but no one has completed the action recently. If you know you've had sales, your trigger is broken.

• Unverified / Tag Inactive: Google hasn't seen your tag fire at all. If you recently deployed it, you need to force a test conversion to kickstart the system.

Step 2: Launch Google Tag Assistant

To watch your tags fire in real time, navigate to tagassistant.google.com. Following Google's major platform unification, standard GTM containers operate as centralized 'Google Tags' using individual product 'Destinations.'

1. Enter your website's exact URL and click Connect. This will launch your website in a new, isolated browser window with debugging parameters automatically appended to the URL.

2. Keep this debug window open and complete your conversion action (e.g., fill out your contact form or complete a test checkout).

3. Return to the Tag Assistant dashboard tab. Look at the left-hand sidebar under 'Output Summary.' Click on the specific page event where the conversion happens (like a thank-you page load).

4. Under Tags Fired, you should see your Google Ads Conversion Tracking destination. Click it to verify that critical variables, like your transaction_id, currency, and exact order value, are being passed cleanly without formatting errors.

Step 3: Cross-Examine with GA4 DebugView

If your Google Ads conversions are imported directly from Google Analytics 4 (GA4), or if you want to verify that your dataLayer is executing cleanly, you need to check the GA4 backend in real time.

Keep your Tag Assistant session active (this automatically passes the required _dbg parameter to your browser session) and open your Google Analytics 4 property in a separate tab. Navigate to Admin > Data Display > DebugView.

As you move through your website in the debug window, you will see a live vertical timeline of events. Look for your conversion event (such as purchase or generate_lead). Click on the event block to expand its parameters. Ensure that matching transaction data is visible here; if the event appears in DebugView but contains a blank value parameter, Google Ads will receive a flat conversion count without financial weight.

Why Most People Hit a Brick Wall Here

If you followed these steps perfectly and your timeline is completely blank, or your tags are listed under 'Tags Not Fired,' your infrastructure has a structural block. The most common reasons self-audits fail include:

• Consent Mode v2 Blocks: If your Cookie Management Platform (CMP) is misconfigured, it will hold back your initialization triggers, completely blocking the tags from loading even if you click 'Accept' on your test device.

• Browser Extensions & Ad Blockers: Legacy client-side debugging tools are highly susceptible to tracking blocks. If you are testing with an active ad blocker or tracking protection script enabled, your dataLayer pushes will fail to register in the dashboard.

• Duplicate Firing Logic: You might see your conversion fire twice on a single action because a legacy hardcoded global site tag is conflicting with your Google Tag Manager container.

Need an Expert Eye?

Diagnosing an analytics setup can get messy fast, especially when dealing with server-side variables, complex dataLayers, and strict privacy consent rules. If your tracking numbers still aren't matching up or your real-time debuggers are throwing errors, let our team fix it for you. Head over to our Implementations & Auditing page or contact us directly at daniel@converted.ie to schedule a comprehensive tracking audit.