Measurement and attribution

Meta Conversions API setup: verify the signal end to end

A working Conversions API setup is not merely an endpoint returning 200. It sends the intended business event, at the correct time, with stable identifiers, value and currency where relevant, and it can be reconciled with the source system without creating duplicates.

By Adwize Editorial TeamReviewed by Adwize Product Team8 min read

Start with an event contract, not an integration method

Write down the business action each event represents, the system that confirms it, and the timestamp that should be sent. A Purchase should map to a completed commercial event, not simply a visit to a thank-you URL that can be refreshed.

  • Event name and triggering business action
  • Authoritative source and event timestamp
  • Required value, currency and order identifier
  • Permitted customer information parameters

Trace one known conversion through every handoff

Use a controlled test order or lead and retain its internal reference. Compare the source record, the server payload and the event visible in Meta. This reveals transformations, missing fields and time-zone errors that aggregate dashboards tend to hide.

  1. Create one identifiable test conversion.
  2. Capture the payload before it leaves your server or partner.
  3. Confirm receipt and diagnostics in Events Manager.
  4. Reconcile the event with the source record after processing.

Judge quality separately from delivery volume

A high event count can coexist with poor matching, delayed timestamps or incorrect revenue. Review diagnostics, matching inputs and event coverage by event type. Then compare daily totals with the store or CRM over the same closed window rather than the current partial day.

Release with a reconciliation monitor

Record expected ranges for count, value, delay and duplicate rate, then alert on meaningful deviations. Keep the monitor independent from campaign performance so a profitable week cannot conceal a broken signal and a weak week cannot be blamed automatically on tracking.

Worked example

A store records order A-1042 at 14:03 for EUR 86. The browser and server payloads are traced to that order, checked for the same event name and event ID, then reconciled in Events Manager and the commerce system before the setup is declared usable.

Common mistakes

  • Treating a successful HTTP response as proof of correct business data.
  • Testing volume without reconciling a known order from source to destination.

Editorial next decisions

Use these guides only when their decision becomes the next unresolved constraint in your evidence trail.

Limitations

Conversions API can improve connectivity and measurement inputs, but it does not recover events your business never records, prove incrementality, or override consent and data-use obligations.

Questions readers ask next

Should Conversions API replace the Meta pixel?

Meta recommends considering the pixel alongside Conversions API for website events. The two channels can provide complementary connectivity, provided browser and server copies are deduplicated correctly.

What should be tested after launch?

Recheck event counts, value, currency, timestamps, diagnostics, match quality and duplicate handling against a closed source-of-truth window after every checkout, CRM or consent change.

Sources checked

Primary documentation was checked on the date shown. Product interfaces and eligibility can change, so verify the current account state before acting.

Measurement and attributionMeta Pixel and CAPI deduplication: prove one action stays one eventMeasurement and attributionMeta Event Match Quality: improve the signal without chasing a scoreMeasurement and attributionMeta Ads vs GA4 attribution: compare systems without forcing equality