When conversion tracking not working, Google Ads conversion tracking not working scenarios occur, the entire optimization engine of a paid media account loses its foundation. Conversions not showing in Google Ads can mean Smart Bidding targets ghost data, Meta campaigns optimize toward incorrect signals, and budget allocation decisions are made in the dark. This checklist provides a cross-platform diagnostic covering conversion actions, tag firing, deduplication, Meta Pixel, Conversions API, and consent-related gaps, so advertisers can pinpoint exactly where the signal breaks down.

What Does Conversion Tracking Not Working Actually Mean?

Conversion tracking failure is not always a binary event. In many cases, tracking appears to be active while silently recording inaccurate data. A tag may fire on page load rather than on purchase completion. A conversion action may be duplicated, inflating reported conversions by double or triple the real count. A Meta Pixel may fire client-side while the Conversions API sends a second event without proper deduplication, causing the same transaction to register twice. These silent errors are often more damaging than a complete tracking outage because they distort the signals that automated bidding systems use to make decisions.

Conversion tracking, at its core, is the mechanism by which an advertising platform learns which clicks lead to valuable outcomes. Google Ads uses a combination of the Google tag (gtag.js or Google Tag Manager) and conversion actions defined in the platform. Meta Ads relies on the Meta Pixel for browser-side events and the Conversions API (CAPI) for server-side events. When either layer is misconfigured, the platform receives incomplete or inaccurate data. Because modern bidding strategies like Target CPA, Target ROAS, and Meta’s Advantage+ are entirely dependent on conversion signal quality, even a 20 percent data gap can cause algorithmic bidding to underperform or enter learning mode unnecessarily. According to Google’s official advertising documentation, conversion data is the primary input for all automated bidding models, meaning bad tracking directly degrades campaign performance at a systemic level.

Google Ads Conversion Tracking Not Working: Platform-Level Diagnostics

The first diagnostic layer for Google Ads is the conversion action configuration itself. Inside the Google Ads interface, navigate to Tools and Settings, then Conversions. Each conversion action displays a status indicator. A status of “No recent conversions” does not necessarily indicate a tracking problem; it may simply reflect a period with no qualifying user actions. However, a status of “Unverified” or “Tag inactive” is a direct signal that the tag has not fired correctly on the designated conversion page. Advertisers should check the conversion action’s counting method, attribution model, and conversion window, as misconfigurations in any of these settings can cause conversions to appear missing even when the tag fires correctly.

Google Tag Diagnostics is a tool available within Google Ads that scans for tag implementation issues. It checks whether the Google tag is present on the site, whether conversion linker is enabled, and whether any duplicate or conflicting tags exist. When Google tag diagnostics surfaces a warning about cross-domain tracking or cookie consent blocking, these are not minor alerts. They indicate that a portion of conversion data is being lost, often silently. Advertisers running consent management platforms (CMPs) must ensure that the Google Ads conversion tag only fires after explicit user consent is granted, while also implementing Consent Mode v2 so that Google can model conversions from users who declined tracking, partially recovering the signal.

Another common source of Google Ads conversion tracking not working is the use of imported goals from Google Analytics 4. When GA4 is the source of truth for conversion data, any misconfiguration in the GA4 data stream, event parameters, or the link between GA4 and Google Ads becomes a failure point. If the GA4 event name does not match the imported conversion action name exactly, or if the GA4 measurement ID is firing on a subset of pages only, the imported conversion count will be lower than actual performance. The Google Ads Help Center recommends verifying the GA4 link status directly in both platforms before assuming the tracking implementation is at fault.

How to Check if Your Meta Pixel Is Working

The Meta Pixel is a JavaScript snippet that fires browser-side events to Meta’s servers. The primary diagnostic tool for Meta Pixel not firing issues is the Meta Pixel Helper, a Chrome browser extension published by Meta for Business. After installing the extension, visiting the conversion page and completing a test action will show whether the Pixel fires, which events are triggered, and whether event parameters such as value, currency, and content IDs are passed correctly. A green checkmark in the Pixel Helper confirms the event fired. A red warning indicates a parameter error, duplicate event, or complete failure to fire.

The Events Manager within Meta Business Suite provides a second diagnostic layer. The Test Events tool allows advertisers to send real browser events and observe them appearing in the Events Manager in near real time. This confirms not only that the Pixel fires but also that Meta’s servers receive and process the event. If events appear in the browser extension but not in Events Manager, the issue may be an ad blocker, a browser privacy setting, or an iOS privacy framework stripping the cookie before the event reaches Meta’s servers. This is precisely the scenario where the Conversions API becomes essential, as it bypasses the browser entirely and sends event data directly from the server.

According to Meta for Business documentation, server-side events sent via CAPI can recover a significant portion of the signal lost to browser-based restrictions, particularly on iOS devices where Apple’s App Tracking Transparency framework limits client-side tracking. Industry data consistently shows that advertisers using both Pixel and CAPI together report more complete event matching and improved audience quality compared to Pixel-only implementations. The event match quality score in Events Manager, rated from 0 to 10, is a direct measure of how effectively Meta can match incoming events to real user accounts. Scores below 6 indicate that key identifiers such as email, phone number, or IP address are not being passed, which limits retargeting audience quality and lookalike model accuracy.

Meta CAPI Setup Issues: What Goes Wrong and Why

Meta CAPI setup issues fall into several distinct categories. The first is missing or incorrect event deduplication. When both Pixel and CAPI are active, the same event, such as a Purchase, may be sent twice: once from the browser via the Pixel, and once from the server via CAPI. Without a matching event ID passed in both calls, Meta treats these as two separate conversions, doubling the reported count. The event_id parameter must be identical in both the Pixel event and the CAPI payload for deduplication to function correctly. This is one of the most common and consequential CAPI configuration errors.

The second category of CAPI setup issues involves customer information parameters. CAPI sends user data such as hashed email addresses, phone numbers, and IP addresses alongside event data. If the server-side implementation fails to hash these values using SHA-256 before sending, Meta rejects them. If the values are hashed but sourced from a stale session rather than the current user action, the match quality score drops. Advertisers using third-party CAPI gateway solutions such as those offered through Meta’s partner integrations must verify that the gateway is passing all available customer information fields, not just the minimum required set.

The third category involves event timing mismatches. CAPI events should be sent within seconds of the browser-side event occurring. If a server-side batch process sends CAPI events hours after the browser event, Meta’s deduplication window may expire, causing both events to be counted. Additionally, significant delays between browser and server events can cause attribution mismatches, where the browser event attributes a conversion to one campaign and the server event attributes it to another. For teams managing Meta campaigns at scale, tools like the Adsroid AI agent for Meta Ads can flag CAPI configuration anomalies automatically, reducing the diagnostic time required to identify and resolve these issues.

Consent Mode, Privacy Restrictions, and Signal Loss

One of the most underdiagnosed sources of conversion tracking gaps is consent-related signal loss. In markets subject to GDPR, CCPA, or similar privacy regulations, advertisers are required to obtain user consent before firing tracking tags. When a user declines consent, standard tracking tags do not fire, and the conversion is simply not recorded. Google’s Consent Mode v2 addresses this by allowing the Google tag to operate in a cookieless, non-identifying mode when consent is declined. In this mode, Google uses behavioral modeling to estimate the conversions that would have been attributed to declined users, partially restoring the optimization signal without violating consent preferences.

Advertisers who have not implemented Consent Mode v2 in markets with high cookie decline rates may be operating with 20 to 40 percent of their conversion data missing, depending on the region and site category. This gap does not appear as an error in Google Ads; conversion status shows as active, and the tag fires correctly for consenting users. The missing data only becomes visible when comparing Google Ads conversion counts against backend order data or CRM records. If the discrepancy between platform-reported conversions and actual business outcomes exceeds 15 percent consistently, consent-related signal loss should be investigated as a primary cause.

For Meta, the equivalent mechanism is the iOS 14.5 and later impact on Pixel-based tracking. Following Apple’s ATT framework, users who opt out of tracking on iOS devices are not tracked by the Meta Pixel. Meta’s Statistical Modeling attempts to fill this gap, but the accuracy depends heavily on the volume of matched events coming through CAPI. Advertisers with low CAPI event match quality and high iOS user percentages in their audience may see reported Meta conversions significantly below actual business outcomes. Regularly comparing Meta-reported conversions against GA4 or backend data is a recommended practice for identifying this type of gap. This broader context of a full tracking audit across Google Ads is essential for catching these platform-specific blind spots.

Why Broken Tracking Silently Ruins AI Optimization

Modern paid media platforms are algorithmic systems that learn from conversion signals. When conversion tracking not working conditions exist, even partially, the learning algorithms receive corrupted input. A Smart Bidding strategy set to Target CPA that is receiving only 60 percent of actual conversions will calculate a CPA that appears higher than reality, causing the algorithm to underbid on auctions it should win. Conversely, a strategy receiving duplicate conversions due to deduplication failures will calculate an artificially low CPA, causing overbidding and budget waste.

Meta’s Advantage+ campaigns and automated audience targeting rely on conversion event data to identify high-value user segments. If the Purchase event consistently underreports due to Pixel blocking or CAPI misconfiguration, the algorithm builds lookalike audiences from an incomplete dataset, systematically excluding users who convert via iOS or cookieless browsers. The result is not an error message; it is a gradual degradation of campaign performance that resembles creative fatigue or audience saturation, making it difficult to diagnose without directly auditing the tracking layer. Teams that proactively manage Meta ad performance signals including creative fatigue often discover that apparent fatigue is actually a tracking gap masquerading as an engagement problem.

Adsroid’s AI advertising agent includes anomaly detection that cross-references conversion volume trends against historical baselines and flags statistically significant drops in conversion rate that do not correspond to changes in click volume or impression share. In documented use cases, this anomaly detection has identified CAPI deduplication failures within hours of occurrence rather than the days it typically takes for a human analyst to notice the discrepancy during a weekly review. Teams using Adsroid have reported recovering accurate conversion signal within 24 to 48 hours of an anomaly alert, compared to an industry average of several days when relying on manual monitoring alone. After restoring accurate tracking, campaigns that had entered conservative bidding mode due to signal loss returned to target performance levels, with some accounts seeing ROAS improvements of over 30 percent simply from restoring clean conversion data.

Step-by-Step Tracking Audit: How to Audit Conversion Tracking Across Google Ads and Meta

Step 1: Verify Conversion Action Configuration in Google Ads

Open Google Ads, navigate to Tools and Settings, then Conversions. Review each active conversion action for status, counting method, attribution model, and conversion window. Confirm that only the intended actions are set to Primary conversion, as secondary conversions do not influence Smart Bidding. Check that the conversion window aligns with the actual sales cycle length for the business. A 7-day window for a product with a 30-day consideration period will systematically undercount late-converting users who clicked an ad weeks earlier.

Step 2: Run Google Tag Diagnostics

Within Google Ads, access the Tag Diagnostics report under the Conversions section. Review for warnings related to tag presence, conversion linker status, and consent mode implementation. Use Google Tag Manager’s Preview mode or the Tag Assistant Chrome extension to verify that the Google tag fires on the correct pages with the correct conversion parameters. Confirm that the transaction ID parameter is passed for purchase events to enable deduplication and prevent double-counting from dynamic remarketing tags firing alongside conversion tags.

Step 3: Audit the Meta Pixel with Pixel Helper and Events Manager

Install the Meta Pixel Helper Chrome extension and visit every key conversion page, including cart, checkout, order confirmation, and lead submission pages. Document which events fire on each page and verify that required parameters are present. Then open Events Manager in Meta Business Suite and use the Test Events tool to send live test conversions. Confirm that events appear in Events Manager within 60 seconds and that the event match quality score is 7 or higher. Scores below 6 require investigation into which customer information parameters are missing or incorrectly formatted.

Step 4: Validate CAPI Event Deduplication

Compare the event_id values being passed by the browser-side Pixel events with those being passed by the server-side CAPI payload. These values must match exactly for the same transaction. Use the Events Manager deduplication report to check the percentage of events being deduplicated. If deduplication is occurring on less than 80 percent of events that have both Pixel and CAPI sources, the event_id generation logic is inconsistent and needs to be corrected. Review whether the event_id is generated at the time of purchase or at the time of page load, as late generation can cause ID mismatches between browser and server events.

Step 5: Check Consent Mode and CMP Integration

Verify that the consent management platform (CMP) on the site sends consent signals to both the Google tag and the Meta Pixel before or simultaneously with the user consent action. Use Google Tag Manager’s built-in Consent Mode variables to confirm that ads_storage and analytics_storage consent states are being read correctly by the GTM container. For Meta, verify that the Pixel’s cookie usage is conditional on consent status, and that CAPI events are still sent for non-consenting users using only non-identifying parameters where legally permissible. Review the percentage of sessions with and without consent in GA4 to quantify the data gap.

Step 6: Cross-Reference Platform Data Against Backend Records

Export Google Ads conversion counts and Meta reported conversions for a trailing 30-day period. Compare these figures against backend order management system records, CRM data, or GA4 e-commerce reports for the same period. A discrepancy of more than 10 to 15 percent in either direction warrants further investigation. Undercounting typically points to tag firing failures, consent blocking, or browser privacy restrictions. Overcounting typically points to duplicate conversion actions, deduplication failures, or incorrect counting methods set to Every rather than One in Google Ads.

Step 7: Review Attribution Model and Window Alignment

Attribution model selection materially affects reported conversion counts. A data-driven attribution model in Google Ads distributes conversion credit across multiple touchpoints in the click path, while a last-click model assigns all credit to the final click. Switching between models changes reported conversion volume without any actual change in business outcomes. Ensure that the attribution model selected in Google Ads matches the reporting context in which performance is being evaluated. Similarly, confirm that the Meta attribution setting, typically a 7-day click and 1-day view window, is appropriate for the campaign objective and matches the window used in historical performance comparisons.

Common Mistakes to Avoid When Diagnosing Conversion Tracking

Mistake 1: Assuming the Tag is Working Because It Was Working Before

Website updates, theme changes, CMS platform migrations, and tag manager container modifications can silently break conversion tags that previously worked correctly. A tag that fired accurately six months ago may have stopped firing after a site redesign that changed the URL structure of the confirmation page, removed the data layer push that passed conversion parameters, or introduced a new JavaScript framework that conflicts with the tag’s event listeners. Tracking audits should be conducted proactively on a monthly basis, not only when a problem is suspected. Scheduled tag verification is a standard component of any mature paid media workflow.

Mistake 2: Counting the Same Conversion Action in Multiple Places

A common configuration error is creating a conversion action directly in Google Ads and also importing the equivalent event from Google Analytics 4, then marking both as Primary conversions. This causes Smart Bidding to optimize toward twice the number of actual conversions, inflating reported performance while simultaneously training the algorithm on a distorted signal. Advertisers should audit the full list of active conversion actions regularly and ensure that each real-world conversion event is tracked by exactly one Primary conversion action. Secondary conversion actions can be used for additional measurement without influencing bidding.

Mistake 3: Ignoring the Event Match Quality Score in Meta

Many advertisers focus exclusively on whether CAPI events are being sent and ignore the event match quality (EMQ) score that Meta assigns to each event source. An EMQ score of 4 or 5 means that Meta can only match a small percentage of events to real user accounts, severely limiting retargeting audience size and lookalike model accuracy. Improving EMQ requires passing additional customer information parameters: hashed email, hashed phone number, IP address, user agent, and browser-generated click ID (fbclid). Each additional parameter passed correctly increases the match rate. Advertisers who improved their EMQ score from 5 to 8 or above typically see measurable improvements in audience reach and campaign efficiency within two to three weeks.

Mistake 4: Not Testing After Every Site or Tag Change

Any modification to the website, tag management container, or third-party integration should trigger an immediate conversion tracking test. This includes plugin updates, payment gateway changes, A/B testing tool installations, and CMS version upgrades. Each of these changes can interfere with tag firing, data layer population, or cookie behavior. Establishing a post-deployment testing protocol using the Google Tag Assistant and Meta Pixel Helper takes fewer than 15 minutes and prevents tracking gaps that can persist for days or weeks before being noticed during a campaign performance review. The Adsroid platform features automated tag monitoring that alerts account managers to conversion volume anomalies immediately after they occur, reducing the window of undetected tracking failure.

Conversion Tracking Not Working: Cross-Platform Comparison of Diagnostic Tools

Criteria: Tag Verification. Google Ads provides Tag Diagnostics and Tag Assistant. Meta provides Pixel Helper and Events Manager Test Events. Adsroid provides real-time anomaly detection that flags conversion volume drops automatically without requiring manual tool checks.

Criteria: Deduplication Support. Google Ads supports deduplication via transaction ID parameter in conversion tags. Meta supports deduplication via event_id matching between Pixel and CAPI. Madgicx offers reporting dashboards but does not natively audit CAPI deduplication at the parameter level.

Criteria: Consent Mode Compatibility. Google Ads supports Consent Mode v2 with behavioral modeling for declined users. Meta supports CAPI for cookieless event transmission. Revealbot focuses on campaign automation but does not include consent gap analysis in its diagnostic suite.

Criteria: Cross-Platform Signal Comparison. Google Ads and Meta each provide their own conversion reporting with no native cross-platform reconciliation. Optmyzr offers cross-channel reporting but requires manual configuration of data sources. Adsroid cross-references conversion signals across Google Ads and Meta against baseline trends automatically, surfacing discrepancies without manual data export.

Criteria: Attribution Model Audit. Google Ads allows switching between data-driven, last-click, and linear attribution within the platform. Meta provides a fixed attribution window setting. Adsroid monitors attribution window alignment and flags cases where window mismatches may explain apparent conversion count changes following a bidding strategy update.

Criteria: CAPI Configuration Audit. Meta Events Manager provides EMQ scoring and parameter coverage reporting. Madgicx and Revealbot do not offer CAPI audit tooling natively. Adsroid’s integration layer validates that CAPI events include required parameters and that EMQ scores remain above configured thresholds, alerting users when scores decline. For a broader view of cross-channel tracking infrastructure, the Adsroid integrations page outlines how the platform connects to ad accounts, analytics tools, and CRM systems to centralize conversion data.

Criteria: Alerting and Monitoring. Google Ads and Meta both provide manual alert setup through platform notifications. Optmyzr provides rule-based alerts. Adsroid provides autonomous anomaly detection that learns normal conversion patterns and alerts users to deviations in real time, without requiring manual rule configuration.

“The most dangerous tracking error is not the one that causes a complete outage. It is the one that causes a 25 percent undercount that goes unnoticed for weeks while automated bidding quietly adapts to the wrong baseline. By the time the error is found, the algorithm has been trained on corrupted data for a full learning cycle.” – James Calloway, Paid Media Analytics Consultant

“Advertisers often treat conversion tracking as a one-time setup task. The reality is that tracking integrity requires ongoing verification, especially in environments where consent rates, browser behavior, and site infrastructure change constantly. A tracking audit should be as routine as a weekly performance review.” – Priya Mehta, Performance Marketing Lead

Frequently Asked Questions About Conversion Tracking Not Working

Why are my Google Ads conversions not showing in the account?

Conversions not showing in Google Ads is most commonly caused by one of four issues: the conversion tag is not firing on the correct page, the conversion action is set to a counting method or attribution window that excludes the events being measured, the Google tag is blocked by a consent management platform or browser privacy setting, or the conversion action status is set to Secondary rather than Primary, which means it is not influencing bidding or primary reporting columns. Use the Tag Diagnostics tool in Google Ads and the Tag Assistant Chrome extension to verify tag firing before investigating configuration settings.

How do I check if my Meta Pixel is working correctly?

Install the Meta Pixel Helper Chrome extension, visit the conversion pages on the site, and complete the target actions such as adding to cart or submitting a form. The extension will display which events fired, whether required parameters are present, and whether any errors occurred. Additionally, use the Test Events tool in Meta Events Manager to confirm that events are reaching Meta’s servers and are being processed correctly. Check the event match quality score for each event; scores of 7 or above indicate sufficient customer information is being passed for effective audience matching and attribution.

What is the difference between Meta Pixel and Conversions API (CAPI)?

The Meta Pixel is a JavaScript-based client-side tracking solution that fires events from the user’s browser. It is affected by ad blockers, iOS privacy restrictions, and cookie consent declines. The Conversions API (CAPI) is a server-side integration that sends event data directly from the advertiser’s server to Meta’s servers, bypassing the browser entirely. Using both together provides the most complete conversion signal. When implementing both, event deduplication via a matching event_id is required to prevent the same conversion from being counted twice by Meta’s system.

What causes Meta CAPI setup issues?

The most frequent Meta CAPI setup issues include missing event deduplication causing double-counting of conversions, customer information parameters not being hashed correctly with SHA-256 before transmission, event timing delays that exceed Meta’s deduplication window, and incomplete parameter sets that result in low event match quality scores. Advertisers should verify CAPI implementation using the Events Manager payload testing tool and monitor the event match quality score weekly. A score below 6 indicates that critical identifiers are missing and the CAPI setup requires remediation.

How does Consent Mode v2 affect Google Ads conversion tracking?

Google Consent Mode v2 allows the Google tag to fire in a restricted mode when users decline cookie consent. In this restricted mode, no identifying cookies are set, but behavioral signals are sent to Google, which uses machine learning to model the conversions that would have been attributed to declining users. This modeled data is included in Smart Bidding signals, partially recovering the optimization input that would otherwise be lost to consent declines. Advertisers who have not implemented Consent Mode v2 in GDPR-regulated markets may be missing 20 to 40 percent of their conversion signal, depending on the site’s consent acceptance rate.

How do I audit conversion tracking across both Google Ads and Meta?

A comprehensive tracking audit covers seven areas: conversion action configuration in each platform, tag and pixel firing verification using browser-based diagnostic tools, CAPI deduplication validation, consent mode and CMP integration review, cross-referencing of platform-reported conversions against backend business data, attribution model and window alignment, and anomaly monitoring for ongoing signal degradation. This audit should be conducted monthly at minimum, and immediately following any site update, tag container modification, or significant change in reported conversion rate. Using an AI-powered tool that monitors conversion volume automatically can reduce the time required to detect tracking failures from days to hours.

Can broken conversion tracking affect Smart Bidding performance in Google Ads?

Yes. Smart Bidding strategies including Target CPA, Target ROAS, Maximize Conversions, and Maximize Conversion Value are entirely dependent on conversion signal quality. If conversion tracking underreports due to tag failures, consent blocking, or attribution mismatches, Smart Bidding will calibrate bids based on fewer conversions than actually occurred, causing systematic underbidding in competitive auctions. If conversion tracking overcounts due to duplicate actions or deduplication failures, Smart Bidding will overbid, wasting budget. Maintaining accurate, deduplicated, consent-compliant conversion tracking is a prerequisite for effective Smart Bidding performance, not an optional enhancement. For related insights on how tracking quality affects broader campaign performance, reviewing AI visibility as a marketing metric provides useful context on the limits of platform-reported data.

Closing Perspective: Accurate Tracking as the Foundation of AI-Driven Advertising

Every diagnostic step outlined in this checklist points to the same underlying principle: AI-driven advertising platforms are only as intelligent as the data they receive. When conversion tracking not working scenarios persist undetected, the platforms tasked with optimizing campaigns do so with flawed information, compounding the problem over time as algorithms adapt to incorrect baselines. For advertisers who want to move beyond reactive troubleshooting and toward proactive signal management, platforms like Adsroid’s AI agent for Google Ads provide automated anomaly detection, cross-channel conversion monitoring, and real-time alerts that identify tracking failures before they materially impact campaign performance, enabling faster resolution and more reliable optimization across every platform in the account.