Meta Pixel present but no Conversions API (CAPI) signal
If this finding appears in a report, the sampled public page exposed a Meta Pixel signal without a recognised Conversions API signal. Conversions API sends events from a server or supported platform integration. A public page inspection cannot establish that server-side events are absent or that all measurement depends on the browser. This reference page does not test your account.
Why this matters
Browser and server events are separate delivery paths whose coverage and quality need verification. An existing server integration may be invisible to a public scan. Adding one can also introduce duplicate events or inappropriate data sharing. A missing public signal does not quantify lost conversions, prove a campaign problem or guarantee an improvement in return on ad spend.
How to fix it
Ask the authorised measurement owner to review the actual dataset, connected integrations, received events and diagnostics in Meta Events Manager. Compare browser and server coverage for the events the business needs, using an approved test journey rather than a fake lead or purchase. If a real gap justifies Conversions API, follow the supported platform or direct-integration documentation. Verify event matching and deduplication, consent behaviour, permitted data and ongoing diagnostics before relying on the results. Server delivery is not permission to bypass a visitor choice or send unnecessary personal information. Evaluate campaign outcomes separately from successful event delivery; do not install another integration solely because the public scan missed it.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit