When conversion data stops syncing to Ads Manager, your ad platform loses the signal it needs to optimize campaigns. Budgets get misallocated, automated bidding strategies make decisions based on incomplete data, and you lose visibility into what is actually driving revenue.
For B2B SaaS marketing teams, this is not a minor inconvenience. It is a direct threat to campaign performance and reporting accuracy. Every hour your conversion data is broken, your ad platform is flying blind.
The good news is that the root causes of broken conversion syncing are almost always traceable. A misconfigured pixel, a broken server-side event, a mismatched conversion action, or a gap in your first-party data pipeline each has a clear diagnostic path and a concrete fix.
This guide walks you through exactly how to identify why your conversion data is not syncing and how to resolve it, whether you are running campaigns on Meta, Google, or both. You will also learn how to set up a more reliable tracking foundation so this problem does not resurface.
By the end, your conversion events will be flowing correctly into Ads Manager, your attribution data will be accurate, and your ad platform will have the enriched signals it needs to optimize toward real revenue outcomes. Let's get into it.
Step 1: Confirm the Scope of the Sync Problem
Before you start changing anything, you need to understand exactly what is broken. The difference between "all conversion data is missing" and "one specific event stopped firing" completely changes your diagnostic approach. Jumping straight to fixes without scoping the problem first is how teams waste hours chasing the wrong issue.
Start by opening your ad platform's diagnostic tools. In Meta, go to Events Manager and review the event health dashboard. In Google Ads, navigate to Tools and Settings, then Conversions, and look at the diagnostics column for each conversion action. Both platforms surface active errors, warnings, and recent event activity directly in the interface.
Look for these specific patterns:
Total data absence: No conversion events have been received in the past 24-48 hours across all event types. This typically points to a pixel or base code failure, a broken server-side connection, or an authentication issue.
Partial data loss: Some events are firing but specific ones are missing. For example, your PageView event is healthy but your Lead or Purchase event has stopped. This usually indicates a trigger condition failure or a specific event configuration problem.
Data delays: Events are arriving but with a lag of more than 24-48 hours. This can be a server-side processing delay or a batch upload issue with offline conversions.
Count mismatches: Events are showing in Ads Manager but the numbers do not match your CRM or internal analytics. This often points to deduplication failures, attribution window mismatches, or double-firing pixels.
One important check that teams frequently overlook: verify that the time window you are analyzing matches the attribution window set in your ad account. If your ad account uses a 7-day click attribution window and you are looking at conversions from leads who converted on day 10, those conversions will not appear. This creates the appearance of a sync failure when the issue is actually a window mismatch, which is especially common for B2B SaaS companies with longer sales cycles. Understanding Facebook ads attribution settings is essential before drawing conclusions from your data.
Document what you find before moving to the next step. Knowing whether you are dealing with a full outage, a partial failure, or a data quality issue will save you significant time as you work through the remaining steps.
Step 2: Audit Your Pixel and Base Code Installation
Once you know the scope of the problem, the next step is verifying that your tracking code is actually present and firing correctly on the pages that matter. Pixel installation issues are one of the most common causes of missing conversion data, and they are often introduced silently after a website update, CMS migration, or tag manager change.
Install the Meta Pixel Helper Chrome extension and visit your key landing pages, lead forms, and conversion confirmation pages. The extension will show you whether a pixel is present, which Pixel ID it is firing with, and whether any events are being triggered. A green checkmark with the correct Pixel ID is what you want to see. Errors, warnings, or missing pixels are your first concrete finding.
For Google, use Google Tag Assistant to verify that your Google tag and any conversion tracking tags are firing correctly. Tag Assistant will flag misconfigured tags, missing triggers, and tags that are loaded but not executing.
Here are the specific issues to look for during this audit:
Base code missing from key pages: The base pixel or Google tag should load on every page of your site, not just the thank-you page. If the base code is absent from your landing pages, the platform cannot track the full user journey or attribute ad clicks correctly.
Duplicate pixel fires: If your pixel fires multiple times on the same page load, you will see inflated event counts. Ad platforms apply deduplication logic, but excessive duplicates can trigger suppression that drops legitimate data.
Tag manager containers stuck in draft mode: This is a surprisingly common issue. If someone updated a tag or trigger in Google Tag Manager or a similar platform but never published the container, the changes are not live. Check that your container version is published and matches what you expect to be running.
Trigger conditions that no longer match: If your website recently updated its URL structure, form class names, or button IDs, tag triggers that relied on those elements may have stopped firing. Review each conversion trigger to confirm it still matches the current page structure.
Recent site changes: A CMS redeployment, theme update, or developer push can overwrite or remove tracking code that was previously working. If conversion data dropped around the same time as a site change, this is almost certainly the cause. Reliable Facebook conversion tracking depends on your base code remaining intact through every site update.
The success indicator for this step is straightforward: Pixel Helper shows a green checkmark with the correct Pixel ID on your key landing and conversion pages, and Tag Assistant confirms your Google tags are loading and firing without errors. If you find issues here, fix them before moving forward, since everything downstream depends on the base code being healthy.
Step 3: Validate Your Server-Side Event Configuration
Browser-side pixels have become increasingly unreliable. Ad blockers intercept tracking scripts, iOS privacy changes limit cross-site data collection, and browser restrictions on third-party cookies continue to expand. If you are relying solely on a browser pixel for conversion data, you are already working with incomplete information.
Server-side tracking through the Meta Conversion API (CAPI) or Google Enhanced Conversions sends event data directly from your server to the ad platform, bypassing browser-level restrictions entirely. This is now considered a best practice for any team that takes data quality seriously. Following a proper Conversion API implementation tutorial will help you avoid the most common configuration mistakes.
To validate your server-side setup, go to Meta Events Manager and check the event breakdown for each conversion event. You should see a split between browser events and server events. If you only see browser events, your CAPI integration is either not configured or not sending data. If you see server events but they have errors, click into the event details to review the specific error messages.
Key things to check in your server-side configuration:
Event Match Quality score: In Meta Events Manager, each event has a match quality score that indicates how well your server events are being matched back to the users who clicked your ads. A low score means your events are missing key customer information parameters. The parameters that most improve match quality are email, phone number, external ID, and click ID. If your server events are missing these, your match rate and attribution accuracy will suffer.
Deduplication event_id parameter: When you run both browser and server events for the same conversion, both will fire. Without a shared event_id parameter, the ad platform counts the same conversion twice. Every server event must include an event_id that matches the corresponding browser event. This is a required component of any dual-layer tracking setup, not an optional enhancement.
Authentication and access token validity: A common failure point is a CAPI integration that was configured but never properly authenticated, or one where the access token has expired. Events appear to be sent from your side but are rejected by the platform silently. Check your API access token in Meta's Business Settings and confirm it has the correct permissions and has not expired.
Testing server events directly: Use the Test Events tool in Meta Events Manager to send a real browser or server event and verify it appears with the correct parameters. For Google Enhanced Conversions, use Google Tag Assistant to confirm that enhanced conversion data is being captured and sent. Do not assume the integration is working because it was set up previously. Test it now.
If server events are not configured at all, this is the highest-leverage fix you can make. A properly configured server-side layer will recover data that browser pixels are losing and significantly improve your overall attribution quality.
Step 4: Check Conversion Action Settings in Ads Manager
Even if your pixel and server-side events are functioning correctly, your conversion data will not appear in campaign reporting if the conversion actions inside Ads Manager are misconfigured. This step is about verifying the settings within the ad platform itself.
In Google Ads, navigate to Tools and Settings, then Conversions. Review each conversion action and check its status. An action can be active, inactive, or paused, and only active actions with recent data flow will contribute to campaign optimization. In Meta Ads Manager, go to Events Manager and review your custom conversions and standard events to confirm they are set up correctly and associated with the right campaigns.
The specific settings to verify:
Conversion window alignment with your sales cycle: This is critical for B2B SaaS teams. Default attribution windows in Google Ads are often set to 30 days for clicks and 1 day for views. If your average lead-to-close cycle is 60 or 90 days, a significant portion of your conversions will fall outside the window and never be attributed. Review your conversion window settings and extend them to match your actual sales cycle.
Optimization event and campaign alignment: Each campaign optimizes toward a specific conversion event. If your campaign is set to optimize for Purchase but your pixel only fires a Lead event, no conversion data will flow back to that campaign. Check that the optimization event selected for each campaign actually matches an event that is actively firing. This mismatch is more common than teams realize, especially after account restructures.
Paused, archived, or renamed conversion actions: If someone paused a conversion action during a campaign review or renamed it after an account restructure, campaigns that referenced the old action will stop receiving conversion data. Check the full list of conversion actions, including archived ones, to see if anything was changed recently.
Enhanced Conversions at the account level for Google Ads: Enhanced Conversions must be enabled at the account level before it can be used by individual conversion actions. Go to your account settings in Google Ads and confirm that Enhanced Conversions is turned on, then verify that each relevant conversion action is configured to use enhanced data. A complete guide to Enhanced Conversions Google Ads setup will walk you through each required account-level configuration.
The success indicator for this step is that each active campaign has at least one conversion action showing recent activity within the last 7 days. If a conversion action shows no recent data despite your pixel and server events appearing healthy, the mismatch between the event being fired and the event the campaign is optimizing for is the most likely culprit.
Step 5: Resolve First-Party Data and Event Matching Issues
Ad platforms match conversion events back to the users who clicked your ads. When that matching process fails or produces weak results, conversion data gets dropped or remains unattributed. This is one of the more nuanced causes of missing conversion data, but it has a significant impact on both reporting accuracy and campaign optimization.
The matching process relies on two things: click ID parameters that tie a conversion directly to an ad click, and hashed user data (email, phone number) that allows probabilistic matching when a direct click ID match is not available. If either of these is missing or misconfigured, your match rate suffers.
Here is how to address each layer of the matching problem:
Click ID capture and storage: When someone clicks a Meta ad, Meta appends an fbclid parameter to the destination URL. Google appends a gclid for Google Ads clicks. These click IDs need to be captured on your landing page and stored in your CRM or database. When you send server-side conversion events, you pass the stored click ID back to the platform, which creates a direct match between the conversion and the original ad click. If you are not capturing and storing click IDs today, this is a high-priority fix. Without click IDs, your server-side matching relies entirely on hashed user data, which is less accurate.
UTM parameter survival through redirects: If your landing pages use redirects, UTM parameters and click IDs can be stripped in the process. Test your ad click URLs by following the full redirect chain and confirming that parameters arrive intact on the final destination page. If parameters are being dropped, you need to update your redirect configuration or use a parameter-preserving redirect method.
Hashed user data in form submissions: Your lead forms and checkout flows should capture email addresses and phone numbers, hash them using SHA-256, and pass them to the Conversion API with each server event. Hashing is required for privacy reasons and is the format ad platforms expect. If your server events are sending unhashed user data, they will be rejected or ignored.
Offline conversion imports for CRM pipeline stages: For B2B SaaS teams tracking leads through a multi-stage CRM pipeline, offline conversion imports allow you to send conversion signals back to the ad platform when a lead reaches a specific pipeline stage, such as qualified opportunity or closed-won. Confirm that your offline conversion import is configured to upload at the right stage and that it is running on a regular schedule. A common failure here is an import that was set up once but stopped running after a CRM integration change. Proper marketing data integration between your CRM and ad platforms is what keeps these imports running reliably.
Improving your event match quality directly improves how well your ad platform can optimize campaigns. Higher match rates mean more conversions are attributed, which gives the platform's bidding algorithms better data to work with.
Step 6: Test End-to-End with a Live Conversion Event
After working through the previous steps, you may have made several changes to your pixel, server-side configuration, conversion actions, or first-party data setup. Before you consider the issue resolved, you need to verify that the full tracking chain is working correctly from a real conversion event all the way through to Ads Manager.
Do not rely on historical data for this verification. Historical data reflects what was happening before your fixes. You need to trigger a new event and trace it through every layer of your stack in real time.
How to run an effective end-to-end test:
Trigger a real test conversion: Submit a test lead form, trigger a test purchase event, or use a test account to complete a sign-up flow. Use a real email address that you control so you can verify matching. Do not use obviously fake data like "test@test.com" for match quality testing, since the platform will not be able to match it to a real user profile.
Check Events Manager within 15-30 minutes: Browser events typically appear in Meta Events Manager within a few minutes. Server events processed through CAPI may take slightly longer. Open Events Manager and look for your test event. Confirm it shows the correct event name, the correct parameters, and a match quality indicator. If you see an error flag or a low match quality warning, review the specific parameters attached to the event and compare them against what you configured.
Use the Test Events tool for direct verification: Meta Events Manager has a dedicated Test Events feature that lets you send browser or server events and see them appear in real time with full parameter details. This is the most direct way to confirm that your CAPI integration is sending correctly formatted events and receiving successful responses from the API.
Compare event counts across systems: After your test, compare the event count in Ads Manager against your CRM or internal database for the same time period. A one-to-one match confirms your tracking is clean. Any discrepancy points to a remaining gap that needs investigation. Using paid ads analytics tools that unify data across platforms makes this cross-system comparison significantly faster.
Check API response codes for direct integrations: If you are using a direct CAPI integration rather than a third-party connector, review the API response for your test event. A 200 response confirms successful receipt. Error codes like invalid_parameter or missing_required_field point to specific data problems that need to be corrected in your event payload.
The success indicator for this step is clear: a test conversion appears in Events Manager within 30 minutes with a high match quality score, no error flags, and a count that matches your internal records. If you reach this point, your conversion data is syncing correctly.
Building a Tracking Foundation That Holds
One-time fixes are not enough. The teams that maintain clean, reliable conversion data treat tracking as infrastructure, not an afterthought. If you resolve this sync issue without changing how you manage tracking going forward, you will be back in the same position the next time a site update, account change, or platform update breaks something.
Here is how to build a foundation that prevents recurrence:
Implement server-side tracking as your primary data pipeline: Browser-based pixels will continue to face increasing restrictions as privacy standards evolve. A server-side layer that sends conversion data directly from your infrastructure to ad platforms is not optional for teams that need reliable attribution. This should be your primary tracking mechanism, with browser pixels serving as a secondary layer.
Use a centralized attribution platform: Managing conversion data across Meta, Google, your CRM, and your website in separate systems creates blind spots and makes it difficult to catch sync failures quickly. A platform like Cometly connects your ad platforms, CRM, and website events into a single attribution system that tracks every touchpoint in real time, from first ad click to closed revenue. When your data lives in one place, you can see immediately when something breaks and which channel or event is affected.
Set up automated alerts for conversion volume drops: You should not be discovering sync failures by noticing that campaign performance has declined over several days. Configure automated alerts that notify you when conversion volume drops below a threshold within a defined time window. Catching a sync failure within hours instead of weeks prevents significant data loss and campaign damage.
Establish a monthly tracking audit routine: Once a month, check your event match quality scores, review conversion action status across all active campaigns, verify that server events are deduplicating correctly, and confirm that click ID capture is working on your landing pages. This routine takes less than an hour and catches configuration drift before it becomes a serious problem.
Send enriched first-party data back to ad platforms: When your ad platforms receive high-quality, enriched conversion signals, their optimization algorithms perform better. Better signals mean more accurate targeting, smarter bidding, and improved campaign performance over time. This is not just about fixing a sync problem. It is about giving your ad platform the data it needs to drive real revenue outcomes.
Your Sync Fix Checklist
Fixing conversion data that is not syncing to Ads Manager requires working through each layer of your tracking stack systematically. The underlying pattern behind most sync failures is the same: a gap between where data is generated and where it needs to arrive.
Browser pixels get blocked, click IDs go uncaptured, server events miss required parameters, and conversion actions fall out of sync with campaign settings. Each of these gaps has a fix, and you have now worked through all of them.
Use this checklist to confirm your setup is complete before closing out this investigation:
1. Pixel fires correctly on all relevant pages with the correct Pixel ID
2. Tag manager containers are published and triggers match current page structure
3. Server-side events are configured, authenticated, and firing successfully
4. Server events include deduplication event_id parameters
5. Event Match Quality scores are healthy in Events Manager
6. Conversion actions are active and match the optimization events used in campaigns
7. Attribution windows are aligned with your actual sales cycle
8. Click IDs are being captured on landing pages and stored for server-side matching
9. Hashed user data is included in server event payloads
10. A live test conversion appeared in Events Manager without errors
If you want a more permanent solution that prevents these issues from recurring, Get your free demo of Cometly and see how it connects your ad platforms, CRM, and website into one attribution system that tracks every touchpoint in real time and sends enriched conversion data back to your ad platforms automatically.
