.svg)
You check your ad manager dashboard and something feels off. Your landing page analytics show 50 leads came in yesterday, but Meta or Google is only reporting 23 conversions. Where did the other 27 go?
Missing conversions in ad manager is one of the most frustrating problems digital marketers face today. It skews your data, throws off your ROAS calculations, and worst of all, it feeds bad information to the ad platform algorithms that are supposed to optimize your campaigns.
The result? You end up scaling the wrong ads, cutting winners that actually perform, and watching your ad spend efficiency decline.
This guide walks you through a systematic process to identify why your conversions are going missing and how to fix each issue. Whether you're dealing with iOS tracking limitations, pixel firing problems, attribution window mismatches, or server-side tracking gaps, you'll learn exactly where to look and what to do.
By the end, you'll have a clear troubleshooting framework you can use whenever conversion numbers don't add up.
Before you can fix missing conversions, you need to know exactly where your tracking breaks down. Start with a complete audit of your current setup.
Open your browser's developer tools (right-click anywhere on your site and select "Inspect") and navigate to the Network tab. Now walk through your entire conversion funnel as a real user would: click on an ad, land on your page, fill out a form, and complete the conversion action.
Watch for pixel or tag fires in the Network tab. You should see requests to fbevents.js for Meta Pixel, gtag for Google Ads, or whatever tracking solution you're using. If these requests don't appear when you complete a conversion, you've found your first problem. Many marketers discover their conversions are not tracking due to simple implementation errors.
Check that event parameters are passing correctly. Each conversion event should include the event name (like "Purchase" or "Lead"), the conversion value, and the currency. Missing or incorrect parameters mean your ad platforms can't properly attribute revenue to specific campaigns.
Test from multiple entry points. Sometimes tracking works fine when users land directly on your homepage but breaks when they arrive via a specific campaign URL or through a redirect. Test the complete user journey from actual ad clicks, not just by typing your URL into a browser.
Create a simple spreadsheet documenting every page where conversions happen. Note whether tracking is installed, whether it fires correctly, and any issues you discover. This becomes your baseline for measuring improvement.
Pay special attention to thank you pages, confirmation screens, and any pages that load after a form submission. These are the most common places where tracking gets overlooked during website updates or redesigns.
If you're running campaigns across multiple domains or subdomains, verify that cross-domain tracking is configured properly. Without it, the user journey breaks when someone moves from your main site to a checkout subdomain, and the conversion gets attributed to direct traffic instead of your ad.
Now that you understand where tracking might be failing, you need to quantify exactly how many conversions are going missing. This means comparing data across all your analytics platforms.
Pull conversion data from your ad manager, Google Analytics, and your CRM for the same time period. Use at least a full week of data to account for day-to-day variations. Make sure you're comparing apples to apples by using the same date range and time zone across all platforms. If you notice discrepancies, you may be dealing with Google Analytics missing conversions as well.
Calculate the percentage gap between what your ad manager reports and what your source of truth shows. If your CRM logged 500 conversions but Meta only shows 325, you're missing 35% of your conversions. That's the number you're trying to reduce.
Look for patterns in the discrepancies. Break down the data by campaign, device type, browser, and traffic source. You might discover that mobile Safari shows a 60% gap while desktop Chrome only shows 10%. That tells you exactly where to focus your fixes.
Check whether certain campaigns or ad sets show bigger gaps than others. If your retargeting campaigns have near-perfect tracking but your cold traffic campaigns show massive discrepancies, you're likely dealing with attribution window issues or privacy restrictions affecting new users more than returning visitors.
Document your baseline numbers clearly. Write down the total conversion gap, the percentage missing, and which segments show the worst tracking. You'll use these numbers to measure success as you implement fixes in the following steps.
This comparison process also helps you identify your most reliable source of truth. For most businesses, that's your CRM or backend database since it captures actual customers regardless of tracking limitations. Your ad platforms should eventually match this source as closely as possible.
Here's where it gets interesting. Even if your tracking is installed perfectly, privacy restrictions can still block a huge portion of your conversions from being reported.
Since iOS 14.5 launched in 2021, Apple requires apps to ask users for permission to track them across other apps and websites. The App Tracking Transparency prompt gives users a clear choice, and the majority opt out. When they do, pixel-based tracking from Meta and other platforms simply can't see those conversions.
Safari's Intelligent Tracking Prevention adds another layer of complexity. It limits third-party cookie lifespan to seven days and in some cases reduces it to just 24 hours. If your sales cycle is longer than that, conversions won't be attributed back to your ads even when tracking technically works. Understanding how to track conversions after cookie changes is essential for modern marketers.
The solution is server-side tracking. Instead of relying on browser pixels that can be blocked, you send conversion data directly from your server to the ad platforms. Meta calls this the Conversions API. Google calls it Enhanced Conversions. Both accomplish the same goal: capturing conversions that browser-based tracking misses.
Implementing server-side tracking requires technical work. You need to configure your server or use a platform that handles it for you to send conversion events with customer identifiers like email addresses or phone numbers. The ad platforms then match these identifiers to user profiles, allowing them to attribute conversions even when browser tracking fails. The Meta Conversions API is particularly effective for recovering lost Facebook attribution.
Make sure your server-side events include proper deduplication parameters. Both browser and server events should fire for each conversion when possible, but you need to tell the platforms to count each conversion only once. Meta uses an event_id parameter for this. Google uses similar mechanisms in Enhanced Conversions.
Test your server-side implementation in the Events Manager or equivalent diagnostic tool. You should see both browser and server events arriving, with deduplication working correctly so the total count matches your actual conversions.
The impact of proper server-side tracking can be dramatic. Many businesses see their reported conversion volume increase by 30% to 50% once they're capturing iOS and privacy-restricted conversions that were previously invisible.
Sometimes conversions aren't actually missing. They're just being counted differently than you expect because of attribution window mismatches.
Every ad platform uses attribution windows to determine how long after someone clicks or views an ad a conversion can be credited to that ad. Meta's default is 7-day click and 1-day view. Google Ads uses different windows depending on campaign type. If a conversion happens outside these windows, it won't show up in your ad manager even though it happened.
Review your current attribution window settings in each platform. Ask yourself whether they match your actual sales cycle. If you're selling enterprise software with a 30-day consideration period, a 7-day attribution window will miss most of your conversions by design.
Compare how your ad platforms count conversions versus how you count them internally. You might be looking at conversions by the date they occurred, while your ad manager reports them by the date of the original ad click. This timing difference can create apparent discrepancies even when all conversions are being tracked.
Understand that different attribution models also affect reported numbers. Last-click attribution gives all credit to the final touchpoint before conversion. First-click gives credit to the initial interaction. Multi-touch models distribute credit across multiple touchpoints. Your ad platforms and your internal analytics might be using different models, creating gaps in the numbers. Learning to measure assisted conversions effectively can help you understand the full customer journey.
For most businesses, the solution is to standardize on one attribution approach across all platforms. Choose windows that reflect your actual customer journey length. If you sell products that people buy quickly, 7-day click attribution works fine. If you have a longer sales cycle, extend the windows accordingly.
Document your chosen attribution settings and make sure everyone on your team understands them. When your media buyer, your analyst, and your CFO are all looking at different attribution windows, you'll never agree on which campaigns are actually working.
Even with server-side tracking in place, you'll still lose conversions if the ad platforms can't match your conversion data to specific users. This is where event matching quality becomes critical.
Customer identifiers are the key to accurate matching. When you send a conversion event, include as many identifiers as possible: email address, phone number, first name, last name, city, state, and zip code. The more data points you provide, the better the platform can match the conversion to the right user profile.
Check your Event Match Quality score in Meta's Events Manager. This diagnostic tool shows you exactly how well your conversion events are matching to Facebook users. Scores above 6.0 are considered good. Below 4.0 means you're losing significant attribution accuracy. If you're seeing issues, your Facebook Pixel may be missing conversions due to poor data quality.
Customer data must be hashed before sending it to maintain privacy compliance. Use SHA-256 hashing for email addresses and phone numbers. Most server-side tracking implementations handle this automatically, but verify it's working correctly. Sending unhashed personal data violates platform policies and privacy regulations.
Improve your match rates by capturing more first-party data at conversion points. If you're only collecting email addresses, add optional fields for phone numbers. The more identifiers you collect with user consent, the better your matching becomes.
Pay attention to data formatting. Phone numbers should include country codes. Email addresses should be lowercase with no spaces. Even small formatting inconsistencies can prevent successful matching and cause conversions to go unreported.
Test your event matching by completing test conversions yourself and checking whether they appear in your ad manager with proper attribution. If your test conversions aren't showing up, real customer conversions aren't either.
The difference between poor and excellent event matching can account for 20% to 30% of missing conversions. It's one of the highest-impact fixes you can make once basic tracking is in place.
The most reliable way to eliminate missing conversions is to connect your CRM or backend database directly to your ad platforms. This ensures that every conversion recorded in your source of truth also gets reported to the platforms optimizing your ads.
Manual conversion uploads work but they're slow and error-prone. You export data from your CRM, format it correctly, and upload it to each ad platform. By the time the data arrives, it's already outdated and the optimization algorithms can't use it effectively.
Real-time conversion syncing solves this problem. Tools like Cometly automatically capture conversions from your CRM, website, and other sources, then immediately sync them to Meta, Google, and other ad platforms with proper attribution to the original ad click. Learning how to sync conversions to ad platforms is crucial for accurate reporting.
Set up conversion value passing as part of your sync. Don't just tell the ad platforms that a conversion happened. Tell them the actual revenue value. This allows the algorithms to optimize for high-value conversions instead of treating all conversions equally.
Verify that synced conversions appear correctly in your ad manager with proper attribution. Check that the conversion events show up under the right campaigns, ad sets, and ads. If attribution is breaking during the sync process, you haven't actually solved the problem.
The beauty of automated conversion syncing is that it captures conversions regardless of browser restrictions, ad blockers, or tracking limitations. If a lead enters your CRM, it gets synced to your ad platforms. Period. This approach also helps you track conversions across multiple platforms simultaneously.
This approach also future-proofs your tracking against ongoing privacy changes. As browsers implement stricter cookie restrictions and users opt out of tracking more frequently, direct CRM integration becomes the only reliable way to maintain accurate conversion data.
Many businesses see their missing conversion gap drop from 30% or more down to under 5% once they implement proper conversion syncing from their source of truth.
Tracking isn't something you fix once and forget about. Website updates, platform changes, and new privacy restrictions can break your carefully configured setup at any time.
Create a weekly tracking health check routine. Every Monday morning, compare your ad manager conversion numbers to your CRM data from the previous week. If you see the gap widening, you know something broke and can investigate immediately instead of discovering the problem weeks later. Following best practices for tracking conversions accurately will help maintain data integrity.
Set up automated alerts for sudden drops in conversion volume. If your typical daily conversion count is 50 and it suddenly drops to 15 with no change in ad spend, that's a tracking issue, not a performance problem. Catching these issues quickly prevents wasted ad spend on campaigns that appear to be failing when they're actually working fine.
Document your entire tracking setup in detail. Write down which pixels are installed where, how server-side tracking is configured, what attribution windows you're using, and how conversion syncing works. When team members change or you need to troubleshoot an issue six months from now, this documentation becomes invaluable.
Stay updated on platform changes that might affect conversion tracking. Meta, Google, and other ad platforms regularly update their tracking requirements, attribution models, and privacy policies. Subscribe to their developer blogs and changelog notifications so you're not caught off guard.
Test your tracking after every website update or redesign. Even small changes can break pixel implementations or disrupt the user journey in ways that affect conversion tracking. Make tracking verification part of your standard deployment checklist.
Review your Event Match Quality scores monthly. If they start declining, investigate why. It might mean data quality issues have crept into your conversion events or that you need to capture additional customer identifiers.
Ongoing monitoring takes minimal time but prevents massive problems. Fifteen minutes per week of checking your tracking health is far better than discovering three months later that you've been optimizing based on incomplete data.
Fixing missing conversions in ad manager is not a one-time task but an ongoing process. Start by auditing your current setup, then systematically address privacy restrictions, attribution settings, and data quality issues.
The biggest wins typically come from implementing server-side tracking and syncing conversions directly from your CRM. These two changes alone can recover the majority of your missing conversions.
Quick checklist before you go:
Pixel or tag installed and firing on all conversion pages. Verify this through browser developer tools and test the complete user journey.
Server-side tracking implemented to capture iOS and privacy-blocked conversions. Use Meta Conversions API, Google Enhanced Conversions, or a platform that handles both.
Attribution windows aligned with your sales cycle. Don't use default settings if they don't match how long your customers actually take to convert.
Customer identifiers passing with events for better match rates. Include email, phone, and other data points with proper hashing for privacy compliance.
Conversion sync set up between your CRM and ad platforms. Automate this process so every conversion in your source of truth gets reported to your ad managers in real time.
Weekly monitoring routine in place. Compare ad manager data to your CRM regularly and set up alerts for sudden drops in conversion volume.
When your ad platforms receive accurate conversion data, their algorithms optimize better, your ROAS calculations become trustworthy, and you can finally scale with confidence knowing which ads actually drive revenue.
Ready to elevate your marketing game with precision and confidence? Discover how Cometly's AI-driven recommendations can transform your ad strategy. Get your free demo today and start capturing every touchpoint to maximize your conversions.
