How to Fix "Conversion Tag Inactive" Errors in Google Ads: A Step-by-Step Guide

"Conversion tag inactive" is the error Google shows you. The errors Google does not show you are running 24 hours a day even when the status reads Active.

That distinction is the whole article. You will get the step-by-step fix. Every cause, every diagnostic, every resolution path. But if you clear the status and declare victory, you are solving the wrong problem and leaving the expensive half untouched. More on that after the steps.

---

What "Inactive" Actually Means

Google marks a conversion action Inactive when it has not recorded a conversion in the last seven days AND cannot detect the tag firing on your page. It is not the same as "No recent conversions," which means the tag is healthy but traffic or volume is low.

Inactive = no signal detected. No recent conversions = signal present, no events.

The distinction matters because the fix paths are completely different. "No recent conversions" is usually a traffic or campaign issue. "Inactive" is a tracking infrastructure issue, and that is what this guide covers.

While the tag sits Inactive, Google Smart Bidding, Target CPA, Maximize Conversions, Target ROAS, is operating without the conversion signal it was trained on. The algorithm does not pause. It keeps spending and adjusting based on the data it does have, which is now incomplete or stale. After you fix the tag, it takes weeks for the learning to recover. So the cost of an Inactive tag is not just the conversions you did not track. It is the compounding spend inefficiency during the gap and the relearning period after.

Fix it fast. Then understand why it happened so it does not happen again.

---

Quick Answers

Why is my Google Ads conversion tag showing inactive?

The most common causes: the tag was removed or broken during a site update, it lives on the wrong page URL, a GTM container change was saved but never published, a trigger stopped matching the current page or form structure, or a consent banner or content blocker prevented the tag from firing for enough sessions to maintain Active status.

How do I check conversion tag status in Google Ads?

Navigate to Tools and Settings, then Measurements, then Conversions. Look at the Status column for each conversion action. You want "Recording conversions." Inactive and Unverified are the two failure states worth investigating.

What is the difference between Unverified and Inactive?

Unverified means the conversion action exists but Google has never detected the tag firing. It has not yet seen a real conversion. Inactive means it was working at some point and stopped. The diagnostic steps overlap but Unverified usually points to an installation problem while Inactive usually points to something that changed after a working setup.

How long does it take for a fixed tag to show Active?

After a genuine conversion is recorded and verified, allow 24 to 48 hours for the status to update. Do not keep retesting every 10 minutes. Give it the day.

Does an inactive conversion action affect Quality Score?

No. Quality Score is based on expected click-through rate, ad relevance, and landing page experience. It does not touch conversion tracking status. The impact of Inactive is on Smart Bidding signal quality, not Quality Score.

Can consent banners cause an inactive conversion tag?

Yes, and this is one of the most underdiagnosed causes. If your consent management platform is blocking the Google Ads tag until consent is given, and a large share of your traffic is rejecting or not engaging with the banner, conversion volume can drop below the threshold that keeps the status Active. There is a second layer to this that most guides miss, covered in the section below on consent.

Should I delete an inactive conversion action?

No. Deleting it removes the historical data. Change the status to Removed or mark it as a Secondary conversion instead of deleting. If it was a Primary conversion driving Smart Bidding, you need a replacement active conversion before you make any changes.

---

Step-by-Step Fix

Step 1. Confirm Which Conversion Actions Are Inactive

Go to Tools and Settings, Conversions. Note every action showing Inactive. Check whether any of those are marked as Primary conversions feeding Smart Bidding. The ones marked Primary are your critical path. Secondary inactive actions matter less urgently but still need fixing.

Step 2. Check the Tag Is on the Right Page

The most common cause of Inactive status, particularly after a site redesign or platform migration, is that the tag is installed on a page that no longer exists or has changed URL.

If you are using Google Tag Manager, open the container and find the Google Ads Conversion Tracking tag. Check its trigger. If the trigger is a Page View on a specific URL, confirm that URL still exists and still loads after a real conversion. Thank-you pages and confirmation pages are frequently renamed during redesigns. If you moved from /thank-you to /order-confirmation, the old trigger is firing on a URL that no longer loads.

If you are using gtag directly, check the page source of the conversion confirmation page. The conversion event snippet should be present. If the page was rebuilt or the developer removed it during a cleanup, it is gone.

Step 3. Check GTM Container Publish Status

This one causes a specific pattern: the tag looks correct inside GTM, the trigger looks right, everything appears fine in the container, but it is not working in production.

Open GTM. Check the workspace version. If someone edited a tag or trigger and saved but did not hit Publish, the live site is still running the previous container version. The fix is not to edit the tag. It is to publish the container. Any time someone says "I fixed the tag in GTM" and the problem persists, the first question is whether they published.

Step 4. Use Tag Assistant to Confirm Firing

Install the Google Tag Assistant Chrome extension. Navigate to your site. Complete the conversion action yourself, whatever it is: submit the form, reach the confirmation page, complete the purchase.

Tag Assistant will show you which tags fired, when they fired, and whether there were any errors. You are looking for the Google Ads conversion event to appear. If it does not appear at all, the tag is not installed where you think it is. If it appears with an error, the error message is your next diagnostic step.

One specific error worth calling out: "Global site tag not installed." This means the base Google tag loaded before the conversion event snippet, but the gtag.js library itself is missing from the page where the conversion fires. The conversion snippet cannot run without the base tag. Both need to be present on the conversion page.

Step 5. Check Triggers in GTM for Form and SPA Issues

If your site uses a single-page application framework like React, Vue, or Next.js, standard Page View triggers frequently miss the conversion page. The URL changes in the browser without a full page reload, so the GTM Page View trigger never fires.

For SPAs, you need History Change triggers or a custom event trigger that fires when the conversion step completes. Check your trigger type. If it is a standard DOM Ready or Page View trigger and your site is an SPA, that is your problem.

For form submissions, check whether your form fires via AJAX. A standard Form Submission trigger in GTM requires the form to submit and the page to navigate. If the form submits via AJAX and displays a success message without a page change, the Form Submission trigger will not fire. You need a custom event or a click trigger on the submit button paired with a confirmation check.

Step 6. Verify Auto-Tagging Is Enabled

Auto-tagging is what allows Google Ads to pass the GCLID parameter through your URLs and tie ad clicks to conversions. Without it, conversion tracking from Google Ads campaigns breaks.

Go to Google Ads, Settings, Account Settings. Confirm Auto-tagging is enabled. If it was disabled at some point, this alone can cause conversions to stop recording against specific campaigns even if the tag fires.

Step 7. Check Conversion Windows

If your conversion action was previously Active and has now gone Inactive, check the conversion window setting. If you set a 7-day or 14-day conversion window and your sales cycle is longer than that, conversions are occurring but outside the window and not being recorded against the ad click. Navigate to the conversion action settings and look at the conversion window. For B2B or considered purchases, a 30-day or 90-day window is usually more appropriate.

Step 8. Fire a Real Test Conversion and Wait

Do not test by browsing to the confirmation page directly. Do not test by visiting the thank-you URL manually. The tag fires in context, as part of a genuine conversion flow. Use Google Ads Preview and Diagnosis tool or click your actual ad, go through the full funnel, and complete the conversion.

After a confirmed fire in Tag Assistant, give it 24 to 48 hours before checking status again. Testing from your own logged-in Google Ads account will not record the conversion, as Google filters internal traffic. Use an incognito browser that is not signed into any Google account, or use a different device.

---

The Cause Nobody Puts in the Step-by-Step

You followed every step above. Tag fires. Status updates to Active. Done.

Not done.

Here is what generic fix guides skip, and it costs advertisers far more than the Inactive incident itself.

Your CMP Is Blocking the Tag for a Third of Your Visitors

If you are running a consent management platform, which after June 15, 2026 is mandatory for any EEA traffic under Google Consent Mode v2, your conversion tag is gated behind consent. Users who reject cookies, or who do not interact with the banner at all, do not trigger the Google Ads conversion event.

That is the intended behavior. That is legal compliance working correctly.

The problem is the CMP itself.

A Google Ads account saw a 90% overnight drop in measured conversions caused by a Consent Mode v2 misconfiguration. The client's consent banner was collecting user preferences but not transmitting consent signals to Google's tag infrastructure. After diagnosis and remediation, roughly 40% of attribution was recovered through Google's behavioral modeling. The rest was permanently gone.

That was a misconfiguration. But there is a structural problem that is not a misconfiguration. It is how most CMPs are built.

OneTrust, Cookiebot, Usercentrics, and Iubenda all load their consent banners from third-party CDNs. Those CDNs are on the blocklists used by uBlock Origin and Brave. When a privacy-conscious user visits your site, the CMP script is blocked. The banner never loads. In Basic Consent Mode, the Google Ads tag also never loads. In Basic mode, Google tags are blocked until the user interacts with the banner. No banner, no interaction, no tag fire.

Tag Assistant and the Google Tag debugger show consent status at the moment you test. When you test your own site, you have likely already accepted cookies, or you are testing in a mode where consent defaults to granted. So your own diagnostics show the tag working. For a significant share of real users, it is not.

This does not show up as Inactive. It shows up as a gradual, invisible reduction in the conversion volume you are sending to Smart Bidding.

The fix that addresses this structurally: run your CMP from your own subdomain, not a third-party CDN. A first-party CMP is not on any ad blocker filter list. The banner loads on every session. Consent signals transmit correctly. The Google Ads tag fires for every user who consents, including users with ad blockers, because the CMP itself is not blocked.

DataCops First-Party Consent Manager loads from your subdomain. It is TCF 2.2 certified, which satisfies the Google Consent Mode v2 requirement for EEA traffic. It is included in the Business plan at $49 per month, alongside CAPI. If you are running a separate OneTrust or Cookiebot contract to satisfy Consent Mode v2, you are paying for a tool that is structurally blocked for 30 to 40% of your privacy-conscious traffic.

Advanced vs Basic Consent Mode: One Setting That Changes Everything

In Basic Consent Mode, all tags are blocked until consent is given. If a user clicks Reject, you get no data at all. In Advanced Mode, tags still load and send anonymous cookieless pings to Google even after rejection.

Those pings are what enable Google's conversion modeling. Modeling fills in the attribution gaps for non-consenting users using behavioral patterns. Without those pings, there is nothing to model from.

If you are running Basic Consent Mode and a meaningful share of your EU traffic is rejecting cookies, you are sending Google a near-zero signal for a large user segment. Smart Bidding is optimizing on a subset of your real conversions, and it has no way to know the rest exist.

Check your GTM implementation. Find your Consent Mode configuration. Confirm it is set to Advanced, not Basic. Google says two common reasons Google tags stay blocked in GTM are old exception triggers and additional consent checks added on top of the built-in consent controls. If a previous developer added manual blocking rules before Consent Mode existed, those rules may still be layering on top, blocking the tags even after consent is granted.

The v2 Parameters That Break Everything if Missing

Consent Mode v2 added two parameters to the original four: ad_user_data and ad_personalization. Without these signals properly configured, you lose the ability to capture new EEA users in GA4 audience lists, share audiences with Google Ads for remarketing, or get accurate conversion attribution. Google enforces this strictly.

Your conversion tag can be firing correctly, your CMP can be transmitting consent, and you can still be losing attribution if those two parameters are missing from your consent signal. Check your dataLayer push or your CMP's Consent Mode integration and confirm all four parameters are present: ad_storage, analytics_storage, ad_user_data, and ad_personalization.

---

After the Fix: What Happens to Smart Bidding

This is the section that determines whether fixing the tag is worth the effort of doing it correctly.

Every day your Google Ads conversion tag sat Inactive, Smart Bidding was training on a corrupted or missing signal. The algorithm adjusted. It found patterns in the traffic it could observe and optimized toward those patterns. Some of those patterns were wrong. Some of the traffic it was optimizing toward was not your converting audience.

Fixing the tag does not reset that learning. The model has to relearn on fresh data, and that takes time and spend. Depending on how long the tag was Inactive and how much volume ran during that period, recovery can take two to four weeks.

During that relearning period, you are likely to see elevated CPAs and reduced ROAS. This is normal. Do not panic and change your bidding strategy. Changing strategy mid-relearning resets the clock. Let the algorithm digest the corrected signal.

What you can do to accelerate recovery: increase your conversion data volume. More real conversions per week means faster learning. If your conversion volume is thin, enhanced conversions and server-side data can increase the event match quality score Google uses to attribute conversions, which effectively increases the quality of each conversion signal even if the volume is the same.

The DataCops Conversion API routes Google Enhanced Conversions through a server-side connection. That matters here because it also filters bot traffic before any event fires. The 361-billion-IP database that DataCops runs checks every session before the conversion event is sent. Bots, VPNs, datacenter traffic, and proxy IPs are excluded from the CAPI pipeline.

Why does that matter for relearning? Because if you are sending bot conversions to Google Ads along with real ones, the Smart Bidding algorithm is learning from both. When you feed ad platforms 95% of your conversion data via server-side rather than 60% via client-side, the algorithms learn faster and bid more efficiently. But feeding them bot-contaminated data at any volume undoes that. You are not buying better ads. You are buying faster convergence on the wrong audience.

The standard advice after an Inactive incident is to fix the tag, wait for Active status, and move on. The complete advice is to fix the tag, then audit what your CAPI or server-side setup is actually sending to Google, and whether it is real human conversions or a mix.

---

When Standard Fixes Do Not Work

If you have completed every step above, the tag fires in Tag Assistant, a real test conversion was completed, 48 hours have passed, and the status is still Inactive, there are a few remaining possibilities.

The conversion action was removed or is paused. Check the conversion action settings directly. A removed action does not record data regardless of tag status.

There is a URL mismatch between where the tag fires and the conversion URL specified in the conversion action settings. Some conversion action configurations specify a destination URL. If the tag fires on a URL that does not match that specification, the conversion does not record.

Your traffic volume is too low. Certain conversion action types require a minimum volume before Google considers them Active. If your site has very low traffic, one test conversion may not be sufficient to move the status.

Auto-tagging is being stripped. Some platforms, particularly certain e-commerce redirect flows, strip URL parameters including the GCLID during checkout redirects. If the GCLID is not present when the conversion fires, Google cannot attribute the conversion to the ad click. Check the final URL after your conversion flow completes in Tag Assistant and confirm gclid is still in the URL parameters.

---

The Google Tag Gateway Question

January 2026 brought Google Tag Gateway, Google's free infrastructure for converting your Google tags from third-party to first-party. By routing requests through your own domain, it bypasses browser constraints and delivers an average of 14% more observed conversions.

If you are running client-side Google tags and have not set up GTG, doing so will reduce the share of your conversions being stripped by ad blockers. It is a meaningful improvement over pure client-side and it is free. Setup is a CNAME record pointing a subdomain at Google's infrastructure.

The important limitation: if you need conversion tracking for Meta, TikTok, LinkedIn, or other non-Google platforms alongside Google, Tag Gateway will not cover it. Server-side GTM can send data to all of them from a single endpoint.

Google Tag Gateway is a legitimate fix for the Google Ads signal problem specifically. It is not a fix for your overall conversion data quality. It does not filter bots. It does not solve the CMP blocking problem described above. It does not help Meta or TikTok. If Google Ads is your only paid channel and you have no bot problem and no CMP issue, GTG plus proper Consent Mode v2 configuration is a reasonable and free solution.

If you run multi-platform paid media, the pipe for each platform still needs to be addressed separately, or through a unified server-side solution.

For Meta CAPI setup and Google Enhanced Conversions from a single pipeline, DataCops starts at $49 per month on the Business plan and adds bot filtering before any event fires on either platform. That is the distinction from GTG: DataCops routes clean, validated conversions. GTG routes your conversions as-is, bot traffic included.

---

The Conversion Tracking Stack Audit

After resolving an Inactive incident, use it as a forcing function to audit the full stack. Most teams discover during this audit that the tag fix was the smallest problem.

The audit checklist:

Your CMP, is it loading from your subdomain or a third-party CDN? If it is loading from OneTrust's or Cookiebot's CDN, it is being blocked for some share of your traffic. You do not know which share. You do not see it fail.

Your Consent Mode configuration, is it Advanced or Basic? Is it transmitting all four v2 parameters?

Your CAPI or server-side setup, if you have one, is it filtering bots before sending events? What is the bot rate on your paid traffic?

Your conversion windows, do they match your actual sales cycle?

Your attribution model, since September 2022 the default is data-driven attribution in Google Ads. If you switched from last-click during or after a tracking outage, the historical comparison is not apples to apples.

Your conversion counting settings, are they set to One or Every? For lead gen, One is almost always correct. For e-commerce with repeat purchase, Every may be appropriate. Mismatched counting inflates your conversion volume and trains Smart Bidding on ghost events.

If you are interested in a more complete review of advanced conversion tracking infrastructure, the technical implementation guide covers the full stack. For understanding how bot traffic flows into your CAPI and what that does to your paid media optimization, the fraud traffic validation page has the specifics.

---

When NOT to Use DataCops for This Problem

DataCops is not the right tool in every scenario.

If your only platform is Google Ads and your traffic is entirely Google-focused, the Google Tag Gateway is free and handles Google's signals well. Add proper Consent Mode v2 and you cover the consent gap. You do not need a paid tool for a single-platform, low-complexity setup.

If you are a developer who wants full container control and prefers to build your own server-side GTM setup, Stape at $17 per month for Pro hosting is the right infrastructure layer. It gives you the GTM container control that DataCops abstracts away. If you want to own every tag decision, Stape is built for you.

If you need SOC 2 Type II certification today for enterprise procurement requirements, DataCops is in progress on that certification. Tracklution has SOC 2 and ISO 27001 if that is a hard requirement.

If your conversion problem is attribution modeling and you want multi-touch attribution across your entire marketing mix, not just signal recovery, Triple Whale or Northbeam are attribution platforms built for that analysis layer. DataCops cleans what goes into the pipe. Those tools help you understand what comes out.

---

The conversions you sent to Google Smart Bidding last month, how many can you confirm were real humans, recorded accurately, with all four Consent Mode v2 parameters transmitted? If you cannot answer that with a number, the tag going Inactive was the visible problem. The invisible ones are still running.