Few things send a PPC manager's heart rate up faster than logging into Google Ads and seeing a conversion action flagged as "No recent activity." Whether you're managing a $5,000/month account or a $500,000/month account, that status means your bidding algorithms are flying blind, your optimization decisions are built on incomplete data, and every dollar you spend from that moment forward is at elevated risk. The good news: this is almost always fixable, and fixing it correctly — not just making the warning go away — is what separates experienced practitioners from those who paper over the problem and pay for it later.
Before you start troubleshooting, it's worth being precise about what Google is telling you. "No recent activity" on a conversion action means Google has not recorded a conversion from that specific action in the past 30 days. That's it. It does not automatically mean your tag is broken. It does not mean conversions aren't happening. And it definitely doesn't mean you should panic and start creating duplicate conversion actions.
There are three distinct scenarios that produce this status:
Navigate to Tools & Settings → Conversions → Click the specific action. Look at the "Tag status" field. You'll see one of these:
| Tag Status | What It Means | Priority |
|---|---|---|
| Unverified | Tag has never fired or hasn't fired since creation | High — tag likely not implemented |
| No recent conversions | Tag seen on site but no conversion event recorded in 30 days | Medium — could be broken or no activity |
| Recording conversions | Working correctly | No action needed |
| Tag inactive | Tag not found on any pages recently | High — tag likely removed from site |
Install the Google Tag Assistant Chrome extension (or use the Tag Assistant companion at tagassistant.google.com). Navigate directly to your conversion page — the actual order confirmation or lead thank-you page, not your homepage. Watch for the Google Ads Conversion Tracking tag to fire. If it doesn't appear at all, your tag is missing from that page. If it fires but shows errors, you'll get specific error codes to chase down.
A common question in the r/googleads community involves how to test conversion tracking implemented via Google Tag Manager. GTM's preview mode is the right tool here. Open GTM, click "Preview," enter your site URL, and then complete an actual test transaction or form submission. In the Tag Assistant panel, you're looking for two things:
If the tag is sitting in "Tags Not Fired" on the confirmation page, your trigger configuration is the problem. Check whether your Page View trigger is using "Page URL contains /thank-you" (or whatever your confirmation URL path is) and verify that the actual URL matches — including any dynamic parameters that might have changed.
If your checkout process routes through a third-party payment processor or a subdomain, you may have a cross-domain tracking gap. Google's conversion tag on your main domain won't fire if the conversion actually completes on checkout.yourstore.com or a hosted payment page. In this scenario you need either:
The most common GTM-related cause is a trigger that's either too broad or too specific. A trigger set to "All Pages" will fire the conversion tag on every page view — this looks great in your conversion column for about a week until Smart Bidding optimizes toward worthless pageviews and your CPA balloons. Conversely, a trigger with an exact URL match like "Page URL equals https://www.yoursite.com/thank-you" will break the moment someone hits "https://www.yoursite.com/thank-you?order_id=12345" because the query parameter makes it a non-match.
The fix: Use "Page URL contains /thank-you" (or whatever your confirmation path is) rather than an exact match. This handles query parameters gracefully while still being specific to the confirmation page.
If you're passing dynamic conversion values (order totals), your GTM variable needs to reference the correct data layer variable or DOM element. Common failure points include:
If you've implemented Consent Mode v2 — which you should have done by March 2024 for EEA traffic — verify that your consent configuration isn't blocking all ad storage by default. A misconfigured Consent Mode setup where ad_storage defaults to "denied" and no consent banner is updating it to "granted" will result in zero conversion signals from a large portion of your traffic. This is increasingly a diagnosis point for accounts seeing "No recent activity" since mid-2024.
This scenario trips up practitioners more than you'd expect. If you launch a campaign in a low-volume niche, or you're tracking a high-value conversion event (like a demo request from enterprise buyers), it's entirely possible to have a properly functioning tag that records zero conversions over a 30-day window simply because the volume isn't there.
How to verify this is the case (rather than a broken tag):
If you confirm tracking works and conversions are genuinely zero, the problem is campaign performance — not tracking — and that's a different conversation about bid strategy, audience targeting, and landing page quality.
For high-value accounts where conversion data accuracy is non-negotiable, client-side tag firing is inherently fragile. Ad blockers, browser privacy restrictions, and site changes all create gaps. The more robust architecture uses server-side measurement:
If your sales team closes deals in a CRM, you can import those offline conversions back into Google Ads using the GCLID (Google Click ID). The GCLID is captured when someone clicks your ad, stored in your CRM against their lead record, and then uploaded back to Google when the deal closes — days, weeks, or months later. This bypasses all client-side tracking fragility entirely.
Linking GA4 to Google Ads and importing GA4 goals as Google Ads conversions gives you a second measurement layer. GA4's measurement protocol allows server-side event sending, which is significantly more reliable than client-side tags for critical conversion events. As practitioners often discuss in measurement-focused communities, the best setups run both a direct Google Ads tag and a GA4-imported conversion for the same event — not to double-count, but to cross-validate and catch gaps.
Once you've identified and resolved the tracking issue, don't just walk away. Run through this validation checklist before moving on:
If you're staring at a "No recent activity" flag right now, here's your prioritized checklist:
Conversion tracking is the foundation everything else in paid search is built on. Smart Bidding, performance reporting, budget allocation, creative testing — all of it degrades when tracking degrades. The accounts that consistently outperform aren't necessarily running more sophisticated campaigns; they're running campaigns built on more reliable data. Treat your tracking infrastructure with the same rigor you'd apply to your bidding strategy, and "No recent activity" becomes a five-minute diagnostic rather than a crisis.