Conversion Tracking Not Working? A Troubleshooting Guide for Phoenix Advertisers
Broken conversion tracking is the most expensive invisible problem in digital advertising. Here is how to find and fix it.
The Cost of Broken Conversion Tracking
Broken conversion tracking does not generate error messages, send alerts, or make anything visibly stop working. Your ads keep running, your budget keeps spending, and your reports keep generating numbers. The numbers are just wrong. This makes broken tracking one of the most expensive problems in digital advertising because it can persist for weeks or months before anyone notices. The damage compounds in three ways. First, you lose visibility into which campaigns, keywords, and audiences are actually working. Decisions get made on incomplete data. Second, automated bidding strategies — Target CPA, Target ROAS, Maximize Conversions — rely on conversion data to function. Feed them bad data and they make bad decisions, often dramatically overspending or underspending. Third, you lose the ability to calculate real ROI, which means you cannot make informed budget allocation decisions. We estimate that 40-50% of Phoenix ad accounts we audit have at least one significant conversion tracking issue. These range from missing tracking tags on key pages to improperly configured conversion events to cross-domain tracking failures. The median account has been losing 15-25% of its conversion data without the account owner knowing.
Diagnosing Google Ads Conversion Tracking Issues
Start with the Google Ads Conversions page (Goals > Conversions > Summary). Check each conversion action for status. 'Recording conversions' means the tag is firing. 'No recent conversions' or 'Inactive' means the tag is not working. Common Google Ads tracking failures: The Google Ads tag is installed on the website but the conversion action was created in a different Google Ads account. This happens when agencies switch and the new agency creates new conversion actions without checking which tags are actually installed. The conversion fires on page load of the thank-you page, but the thank-you page URL changed and nobody updated the conversion trigger. The tag is in Google Tag Manager but the GTM container is not published. Someone made changes in GTM and saved them as a draft without clicking Publish. Cross-domain tracking is not configured. If your ad sends visitors to domain-a.com but the conversion happens on domain-b.com (common with third-party booking or payment systems), conversions are lost unless cross-domain tracking is explicitly set up. Conversion counting is set to 'Every' instead of 'One' for lead generation businesses. If a single visitor submits a form three times, you do not have three leads — you have one lead counted three times. Set lead-based conversion actions to count one conversion per click. Verify your fix by using the Google Tag Assistant browser extension. Navigate to your conversion page and confirm the tag fires with the correct conversion ID and label.
Diagnosing Meta Ads Pixel and CAPI Issues
Meta conversion tracking has two layers: the browser-based Pixel and the server-side Conversions API (CAPI). Both should be running simultaneously for accurate tracking, with Meta deduplicating events that are captured by both systems. Check Pixel health in Events Manager > Data Sources > your Pixel. Look at the Event Overview for your key events (Lead, Purchase, CompleteRegistration, etc.). If event volume has dropped suddenly, the Pixel may have been removed, blocked by a browser update, or broken by a site code change. Use the Meta Pixel Helper browser extension to verify the Pixel fires correctly on each step of your conversion flow. Check CAPI status in the same Data Sources section. Events sent via CAPI show the server icon. If CAPI events are not appearing, check your server-side integration — this typically breaks when API tokens expire, server configurations change, or the integration platform (Zapier, Stape, etc.) has an issue. The most common Meta tracking issue we see in Phoenix accounts: event match quality below 6.0. Meta assigns a quality score to each event based on how well it can match the event to a Meta user. Low match quality means Meta cannot attribute conversions accurately, which degrades audience building and campaign optimization. Improve match quality by sending additional customer information parameters — email (hashed), phone (hashed), city, state, zip code — with each event.
Diagnosing GA4 Event and Conversion Issues
GA4 tracking issues manifest as missing events, undercounted conversions, or events that fire but are not marked as conversions. In GA4 Admin > Events, verify that your key events exist and show recent activity. Click into each event to confirm it is marked as a conversion. A common mistake: creating an event and forgetting to toggle the 'Mark as conversion' switch. The event collects data but is not treated as a conversion in reports or shared with Google Ads. Check the GA4 DebugView (Admin > DebugView) in real-time while you complete a conversion action on your site. You should see each event fire in sequence. If events are missing, the issue is in your tag configuration — either GTM or the gtag.js implementation. For cross-domain tracking in GA4, verify that your measurement ID is consistent across all domains and that the Linker settings in GTM include all relevant domains. Test by navigating from domain A to domain B and checking that the _gl parameter appears in the URL — this parameter carries the session ID across domains. If your GA4 conversion count does not match your Google Ads conversion count, check attribution models. GA4 uses data-driven attribution by default, while Google Ads may use different attribution. Also check conversion counting settings — GA4 may count 'once per event' while Google Ads counts 'once per click' or 'every.'