Missing Meta Conversion Events
Your Meta Pixel fires PageView and maybe a few custom events, but no standard conversion event (Purchase, Lead, CompleteRegistration, Subscribe). Meta has nothing to optimize toward. Any campaign on this account that asks for "Conversions" will quietly fall back to optimizing for traffic, link clicks, or whatever proxy it can find.
Why It Matters
Meta's ad delivery system is built around standard events. The optimizer learns "this kind of user, on this kind of placement, at this time of day, eventually fires Purchase." If Purchase never appears in the event stream, the optimizer has no target and the campaign drifts toward whatever signal it can latch onto — almost always link clicks, the cheapest action and the least correlated with revenue. Reporting falls apart at the same time. The Ads Manager "Results" column reads from standard events first, custom events second. With no standard events configured, every campaign reports against whatever objective it was created with, and you can't compare them to each other. Lead campaigns, sales campaigns, app campaigns all show different "Results" units and the numbers stop meaning the same thing. Audiences suffer too. Lookalike sources built from Purchase produce dramatically better seed quality than lookalikes built from PageView. No Purchase event, no purchase lookalike, no warm path for prospecting at scale. The usual cause is a pixel that was installed for diagnostics during a site rebuild, never wired to the order confirmation page, and never revisited.
How To Fix It
- Identify the right standard event for the business: Purchase for ecommerce, Lead or CompleteRegistration for lead gen, Subscribe or SubmitApplication where relevant. The full list is in Meta's standard events reference.
- Fire the event on the actual confirmation step, not the button click. Button clicks include abandoned attempts and inflate volume.
- Pass the standard parameters Meta expects for that event (value and currency on Purchase, content_name on Lead, etc).
- Verify in Events Manager Test Events that the event lands with the expected parameters.
- Wait 24-48 hours and confirm the event shows recent volume in the Overview tab before optimizing campaigns toward it.
Example
fbq('track', 'Purchase', { value: 129.99, currency: 'USD' });This Meta Pixel has no active standard conversion event. Per Meta's standard events documentation, events such as Purchase, Lead, CompleteRegistration, and Subscribe are the units Meta uses to optimize ad delivery and to populate Ads Manager Results columns. With only PageView or custom events configured, Conversions-objective campaigns lose their optimization target and tend to drift toward link-click proxies, lookalike audiences built from Purchase cannot be created, and cross-campaign reporting becomes incomparable. The most common root cause is a pixel installed for diagnostics and never wired into the order confirmation or lead confirmation step. Fix: implement the appropriate standard event for the business model, fire it on the confirmation step (not the button click), validate the payload in Events Manager Test Events, and confirm 24-48 hours of stable volume before optimizing campaigns toward it. Source: developers.facebook.com/docs/meta-pixel/reference.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.
References
Audit your own files for this check
AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.
Run a free audit