An ad showed "2 Website Leads" in Meta Ads Manager. Zero real WhatsApp messages had come in. This isn't a hypothetical — it happened this same week, on a real account we audited, and it's exactly the kind of gap that makes a business owner stop trusting their ad numbers altogether.
Key takeaways
- Meta preloads your ad's landing page in the background — that generates real hits to your server with no person behind them.
- If your conversion event fires on the simple loading of the page, those hits get counted as "results."
- The fix: fire the event only on a real, verifiable click — never on the page load.
- Ask whoever runs your ads EXACTLY when their conversion event fires.
The case: "2 leads" that were never a conversation
Looking at Meta Ads Manager, the account showed "Website Leads" results for a campaign driving to WhatsApp. But the number of real WhatsApp Business conversations was zero. Checking the internal tracking sheet, dozens of "clicks" toward the WhatsApp link had been logged — far more than what Meta reported as real — and none of them turned into an actual conversation.
Why this happens
The cause wasn't an obvious misconfiguration — it was something almost nobody accounts for: Meta preloads and reviews the ad's landing page in the background, as part of its own ad review and delivery process, especially in formats like Stories. That generates real hits to the server, with the same user-agent and the same URL a real visitor would have, but with no person on the other end.
If your conversion event (say, "Lead") is set to fire when the page loads — instead of when someone actually clicks something — every one of those automatic Meta preloads gets counted as a real result.
"Meta's 'results' metric can inflate for reasons that have absolutely nothing to do with real buying intent, if your tracking doesn't distinguish between 'the page loaded' and 'a person actually clicked.'"
The fix that actually works
What got implemented was simple to describe, if not trivial to get exactly right: never fire the conversion event on the load of a page that could be an ad's direct destination — only fire it on a real, verifiable click, with its own event handler on the button. On top of that, server-side deduplication by click identifier (fbclid) was added, with a short time window, to filter out retries and preloads of the same click that would otherwise get counted twice.
The result isn't just a nicer-looking number on the dashboard — it's knowing, with certainty, how many real leads every dollar of budget is actually generating. Without that, any decision to "scale this campaign" or "pause that one" gets made on data that doesn't reflect what actually happened.
What to ask whoever runs your ads
If your Meta results don't match the real conversations or sales you're closing, there's one question worth asking: at exactly what moment does the conversion event fire? If the answer is "when the page loads" instead of "when the user takes a real action" — that's the problem, and it's more common than it seems.