The short answer
Inactive means Google saw your conversion tag before and has stopped seeing it. "Never received a tag ping" means it has never seen it at all (Unverified). Find what changed on the site or in Google Tag Manager, fix the tag, test one real conversion from a clean browser, and wait 24 to 48 hours. Never delete the action; set it to secondary while you fix it.
DataCops is a tool that sends your Google Ads conversions server-side from your own domain, gives every visit a bot verdict, sends the real sale from your CRM, warms up new campaigns with the customers you already have, and logs every send, so a broken tag shows up the same day.
How DataCops stops it happening again:
- Server-side, not only a page script. One script and one DNS record collect on your own subdomain; with your DNS on Cloudflare, the free Worker reads the click at the edge. A redesign cannot quietly delete a server send, and ad blockers do not stop it.
- The gclid is kept on the server. Captured on the landing visit and stored for up to 90 days, so a checkout redirect that drops it no longer breaks attribution.
- Counted once. The browser tag and the server event share an event ID.
- Real people only. Every visit gets a bot verdict against 360+ billion IPs, and every form email is checked (disposable providers, domains with no mail server and an email risk score), so Smart Bidding relearns from humans, not bots.
- Relearn faster with Ads Warmup. After an outage, upload your recent customers (up to 20,000 rows), see a match score per person, and send them to Google Ads, Meta and TikTok, so bidding gets real buyers to learn from straight away.
- The real sale, not the form fill. CRM stages go back to Google Ads as offline conversions (HighLevel natively, any CRM by webhook), and Shopify orders through the DataCops Shopify app.
- Consent that loads. A first-party consent banner served from your own domain, and a delivery log shows every send as sent, held, skipped or failed, so a stop shows up the same day.
Best for: lead gen, clinics, home services and HighLevel agencies whose Google Ads count form fills, Shopify stores, and teams without a GTM specialist.
The Monday the tag went quiet
A developer ships a new checkout on Thursday. It looks great. Nobody touches Google Ads.
On Monday the conversion column reads zero. By Wednesday the status says Inactive. Meanwhile Maximize Conversions has spent five days bidding with no idea what a good click looks like.
The tag did not break. It simply was not on the new thank-you page. That is the story behind most Inactive errors: something changed, and tracking was not on the release checklist.
Tags rarely break. Sites change around them.
Tools that fix and prevent an inactive tag
| Tool | Best for | Watch out for |
|---|---|---|
| DataCops | Server-side conversions from your own domain, bots filtered, the real CRM sale sent back, Ads Warmup, a log of every send; Google Ads plus Meta, TikTok and LinkedIn | Needs one script and one DNS record on your site |
| Google Tag Assistant | Free check that a tag fires on a page | Tests your own visit only; says nothing about bots or blocked visitors |
| Google Tag Gateway | Serving Google tags through your domain, free | Google only, no bot filter, no CRM sales |
| Server-side GTM (for example on Stape) | Teams that want full control of every tag | Someone must build and maintain the container; see Stape alternative |
| Custom code | Developers with unusual needs | You own every Google change, retry and duplicate |
When not to use DataCops
- The only problem is a missing tag on one page. Fix it with the steps above. You do not need a tool.
- Google Ads is your only channel, with no bot or consent problem. Google Tag Gateway plus advanced Consent Mode is free and covers it.
- You want full control of every tag. A server-side GTM container on hosting such as Stape gives you that, if someone on your team owns it.
- You need multi-touch attribution across your whole mix. Attribution platforms such as Triple Whale or Northbeam analyse what comes out. DataCops cleans what goes in.
Inactive, Unverified, or "never received a tag ping"?
Google Ads shows a tag status for each conversion action. Three of them get mixed up, and the fix depends on which one you have.
| What you see | What it means | Where to look |
|---|---|---|
| Unverified, or "your conversion action has never received a tag ping" | Google has never seen this tag fire | The install: right page, right ID and label, not blocked |
| Inactive | It worked, then Google stopped seeing it | Whatever changed recently |
| No recent conversions | The tag is fine; nothing converted lately | Traffic, campaigns, the offer |
Find the status in Google Ads under Goals, Conversions, Summary. Click the conversion action and open its diagnostics for Google's own hints. Note which actions are Primary: those feed Smart Bidding and are your critical path. Secondary ones can wait an hour.
If you see "never received a tag ping" on a brand-new action, the tag is usually on the wrong page, carries the Conversion ID and label of a different action, or never loads because consent blocks it. If you see it on an old action, someone probably created a new action and pointed the tag at the old one, or the reverse.
What an inactive tag costs while it sits there
The status is not just a warning label. Smart Bidding (Target CPA, Target ROAS, Maximize Conversions) does not pause when the signal stops. It keeps spending and adjusting on whatever data it still has, which is now incomplete or stale.
So the cost has three parts: the conversions you did not record, the spend steered by a broken signal during the gap, and the relearning period after the fix, when results are often worse before they get better. Quality Score is not affected; bidding is. We compare the two strategies in Target CPA vs Maximize Conversions.
Fix it fast. Then find out why it happened, so it does not happen again.
The eight causes, most common first
1. Site change
A redesign, new theme, new checkout or page-builder update removed the tag, or the thank-you page it lived on.
2. GTM not published
Someone edited the container and saved the workspace but never published. The live site still runs the old version.
3. Trigger stopped matching
The trigger waits for /thank-you, but the page is now /order-received. Or the form now submits without a page load.
4. Single-page app
React, Vue or Next.js change the URL without reloading, so a Page View trigger never fires on the confirmation step.
5. Wrong ID or label
The tag holds the Conversion ID and label of an old action or another account. It fires, and Google files it nowhere.
6. Google tag missing
The conversion event is on the page but the base Google tag (gtag.js) is not, so the event cannot run.
7. Consent blocks it
The tag waits for consent, most visitors never click, or the banner itself is blocked and never appears.
8. Browser blocking
Ad blockers and privacy browsers stop the Google tag for part of your traffic. Rarely the whole cause, often part of it.
Fix it, step by step
Work in order. Stop when you find the problem, fix it, then do the last two steps.
- Note the date it went quiet. In Goals, Conversions, segment by day and find the last day with conversions. Ask what shipped that week: a deploy, a plugin update, a GTM change, a new cookie banner.
- Check GTM versions. In Tag Manager open Versions. If the live version is older than your last edits, nobody published. Compare the two to see exactly what changed. Any time someone says "I fixed it in GTM" and nothing changed, ask this first.
- Check the tag is on the right page. With GTM, open the Google Ads conversion tag and its trigger, and confirm the URL still exists after a real conversion. With gtag on the page, view the source of the confirmation page and confirm both the Google tag and the conversion event are present.
- Walk the conversion with Tag Assistant. Open tagassistant.google.com, connect your site and complete a real test conversion. Look for the Google Ads conversion event on the final step. Not listed at all means the tag is gone. Listed with an error means read the error.
- Fix the trigger. If the URL changed, update the Page URL condition. If the form submits by JavaScript with no new page, use a custom event pushed to the dataLayer after a successful submit. On a single-page app, use a History Change trigger or a custom event for the confirmation step.
- Match the ID and label. In Google Ads open the conversion action, choose Tag setup, and copy the Conversion ID and label. Compare them character by character with the tag.
- Check auto-tagging. In account settings, confirm auto-tagging is on, so the gclid reaches your site. Then check the gclid survives your checkout or form redirects.
- Check consent. In a fresh window, accept the banner and convert again; then reject and convert. If nothing fires either way, the banner or Consent Mode is the cause. See the next section.
- Check the conversion window. If your sales cycle is longer than the window, conversions happen but fall outside it. For considered or B2B purchases, 30 to 90 days is usually right.
- Publish and record one real conversion. Publish in GTM, then convert from a normal browser that is not signed in to your Google Ads account, with no extensions, ideally by clicking a real ad. Visiting the thank-you URL directly is not a test.
- Wait 24 to 48 hours. Status updates are not instant. Checking every ten minutes changes nothing.
If you need time and do not want bids steered by a broken action, set it to Secondary. Do not delete it: deleting throws away its history and breaks any bid strategy that points at it. If it was the Primary action for Smart Bidding, have a working replacement before you change anything. The deeper debugging guide is debugging GTM conversion tags.
Never delete a broken conversion action. Demote it, fix it, promote it back.
The consent cause most guides miss
Consent is the cause your own testing will not show you. When you test your site you have usually already accepted cookies, so the tag fires for you. For a real share of visitors it does not.
Basic vs advanced Consent Mode
In basic Consent Mode, Google tags do not load at all until the visitor accepts. A visitor who rejects, or never clicks, sends nothing. In advanced mode the tags load with consent denied and send cookieless pings, which Google uses to model the conversions it cannot observe. With basic mode and a lot of EEA traffic, Smart Bidding sees a small slice of your real conversions and has no way to know the rest exist.
The four v2 signals
Consent Mode v2 needs four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. The last two were added in v2. If your banner sends only the first two, conversions can fire and still lose attribution and audiences for EEA users. Check your banner's Consent Mode integration, or the dataLayer, for all four. Our Consent Mode v2 guide walks through the setup.
Old blocking rules on top
Google notes that tags often stay blocked in GTM because of old exception triggers or extra consent checks added on top of the built-in consent settings. If a previous developer added manual blocking before Consent Mode existed, it may still block tags after consent is granted.
The banner that never loads
Most consent banners load their script from the vendor's own domain. Some ad blockers and privacy browsers block those domains, so the banner never appears. In basic mode, no banner means no interaction, and no interaction means the Google tag never fires. It does not show as Inactive. It shows as a slow, invisible fall in conversions. A banner served from your own domain avoids that: the DataCops first-party consent manager loads from your subdomain and feeds Consent Mode.
When it still says Inactive
The tag fires in Tag Assistant, a real conversion went through, 48 hours passed, and the status has not moved. Check these.
- The action is removed or paused. A removed action records nothing, whatever the tag does.
- The action expects a different URL. Some setups tie the action to a specific page. If the tag fires elsewhere, nothing records.
- Your test was filtered. Conversions from a browser signed in to the Google Ads account, or from a blocked internal IP, may not record. Test from a clean device.
- The gclid is stripped. Some checkout and payment redirects drop URL parameters. If the gclid is gone when the conversion fires, Google cannot tie it to the click. Check the final URL in Tag Assistant.
- Volume is very low. One test conversion on a quiet account may not move the status quickly. Give it a few days of real traffic.
Active is not the same as right
The status going green tells you the tag fires. It does not tell you what it counts.
Most lead gen setups fire on the form's thank-you page. That counts every submission: the real prospect, the tyre kicker, the bot with a made-up number. Google Ads cannot tell them apart. It sees three conversions and goes looking for more people like all three.
So after the fix, run one more check. Put last month's Google Ads conversions next to the leads your team confirmed as real. If Google shows 120 and sales remember 40, your tag is Active and your bidding is still learning the wrong thing. The fix is to send the stage that matters, a booked call, a won deal, a paid invoice, as an offline conversion, and to keep bot visits out of what you send. DataCops checks each form email against fixed rules (throwaway and disposable providers, domains with no mail server, and an email risk score), and with LeadCops (Business and up) a lead that fails is held and never billed.
One form fill, on its way to Google AdsAfter the fix: what Smart Bidding does
Fixing the tag does not reset what the bid strategy learned during the gap. It has to relearn on fresh data, and that takes time and spend. Expect a period of higher cost per conversion before things settle.
- Do not switch bid strategy mid-relearning. Changing strategy starts the learning again.
- Feed it more real conversions. More real conversions per week means faster learning. Enhanced conversions and server-side sends raise how many conversions Google can match.
- Give it your known buyers. Ads Warmup sends a CSV of existing customers (up to 20,000 rows, each with a 0 to 10 match score) to Google Ads, Meta and TikTok as fresh signal, dated when you send (on Google Ads, only people who clicked a Google ad are credited). It does not rewrite history; it gives the relearning strategy real buyers to aim at.
- Feed it clean ones. Sending bot conversions alongside real ones speeds learning toward the wrong audience. Volume without filtering is not a win.
The standard advice is: fix the tag, wait for Active, move on. The complete advice is: fix the tag, then check what you are actually sending to Google, and whether it is real customers or a mix.
Google Tag Gateway: does it help?
Google Tag Gateway serves your Google tags through your own domain instead of Google's, which helps them load where third-party requests are blocked. It is free and worth setting up if you run client-side Google tags.
Know its limits. It covers Google's tags only, not Meta, TikTok or LinkedIn. It sends conversions as they are, bots included. It does not fix a consent banner that never loads, and it does not send the sale that happens in your CRM later. If Google Ads is your only channel and you have no bot or consent problem, Tag Gateway plus proper Consent Mode is a reasonable free setup. For a fuller comparison, see GTM alternatives and server-side tracking.
How DataCops stops it happening again
- Collection on your own domain. One script and one DNS record put collection on your subdomain. With your DNS on Cloudflare, the free DataCops Cloudflare Worker reads the click ID and UTMs off the first request, before the page or any browser script runs.
- The gclid is kept on the server. gclid, wbraid and gbraid are captured on the landing visit and stored for up to 90 days, so a redirect or a deleted cookie does not lose the click.
- Returning visitors recognised. A signed first-party cookie set by the server on your own domain lasts up to 400 days where enabled, set only after consent and a clean bot check.
- Server-side sends, counted once. Conversions go to Google Ads from the server with enhanced conversions data (hashed email and phone). The browser tag and the server event share an event ID, so each conversion counts once.
- Real people only. Every visit gets a bot verdict checked against an IP database covering 360+ billion IPs, and a Real people only switch per platform keeps bot visits out of what Google learns from.
- The real sale goes back. HighLevel stages natively (lead, booked, showed, won with value, paid), any CRM through a webhook, Shopify orders through the DataCops Shopify app, all matched back to the click. See Google Ads conversion tracking.
- Consent and analytics on your domain. The first-party consent manager is served from your own domain, DataCops skips events marked as declined, and first-party analytics, a GA4 alternative, shows the same real-people traffic.
- Ads Warmup. Your existing customers, scored per person and sent to Google Ads, Meta and TikTok, so a new or relearning campaign starts warm.
- Evidence for refunds. On the Organization plan, the fraud refund report exports bot-flagged Google Ads clicks in the format Google's Click Quality form asks for. You attach it; Google decides.
- You see a stop the same day. A delivery log row per conversion: sent, held, skipped or failed, with the reason. No more finding out from a zero in the conversion column a week later.
The same conversions also go to Meta, TikTok and LinkedIn. Pricing.
Best for: lead gen, clinics, home services and HighLevel agencies whose Google Ads count form fills, and teams without a GTM specialist.
The tracking stack audit
Use the incident as a reason to check the whole stack. Most teams find the tag was the smallest problem.
- Consent banner: does it load from your own domain or a vendor's? Does it load for every visitor?
- Consent Mode: advanced or basic? All four v2 signals sent?
- Server-side: do you send conversions from a server too, and does it filter bots first? What share of your paid traffic is bots?
- Conversion windows: do they match your real sales cycle?
- Counting: One or Every? For lead gen, One is almost always right. Every on a lead form counts repeat submissions as new conversions.
- Attribution model: Google Ads defaults to data-driven attribution. If you switched models around the outage, before and after are not comparable.
- What counts as a conversion: a form fill, or a customer? Send the later stage as an offline conversion if you can.
More on the full setup in conversion tracking and click fraud protection. Questions from other advertisers are in the DataCops community.
FAQ
What does "your conversion action has never received a tag ping" mean?
Google has never seen the tag for this conversion action fire on your site, so the action is Unverified. Either the tag was never installed on the right page, it carries the wrong Conversion ID or label, or it is blocked before it runs. Install or correct the tag, complete one real conversion and wait up to 48 hours.
Why is my Google Ads conversion tag showing inactive?
Google used to see the tag and has stopped. The usual reasons: a site update removed it or renamed the thank-you page, a GTM change was saved but never published, the trigger no longer matches the page or form, or consent settings block it for most visitors.
What is the difference between Unverified and Inactive?
Unverified means Google has never seen the tag fire, so it is an install problem. Inactive means it worked before and stopped, so look for what changed. No recent conversions is different again: the tag is fine, nothing converted lately.
How long until a fixed tag shows active again?
Usually within 24 to 48 hours of a real conversion being recorded. Test once properly from a clean browser, then leave it alone.
Does an inactive conversion tag hurt Quality Score?
No. Quality Score looks at expected click-through rate, ad relevance and landing page experience. The damage is to Smart Bidding, which loses the signal it optimises toward.
Can a cookie banner make the tag inactive?
It can cut conversion volume sharply if the tag waits for consent and most visitors never click the banner, and a banner loaded from a third-party domain can be blocked entirely. Use Consent Mode in advanced mode with all four v2 signals, and load the banner from your own domain.
Should I delete an inactive conversion action?
No. Fix it, or set it to secondary so it stops steering bids. Deleting throws away its history and breaks any bid strategy that points at it.
How do I help Smart Bidding recover after an inactive tag?
Do not change bid strategy while it relearns, send more real conversions, and keep bots out of them. DataCops Ads Warmup can also send your recent customers (up to 20,000 rows, each with a match score) to Google Ads as fresh signal, so the strategy has real buyers to learn from.
Will server-side tracking stop the tag going inactive?
It removes the most common causes: a browser tag deleted by a site change, or blocked in the browser. With DataCops the conversion is also sent from a server, deduplicated against the browser tag, and every send is logged, so a stop is visible the same day.
