Server-side tracking
Meta Conversions API
Send supported Meta events with stable identity and matching context.
Order BM-2048 · Example delivery record
2,000 DKK revenue
Marketing: granted
Snapshot reused
| Destination | Signal | State |
|---|---|---|
| Google AdsMarketing consent checked | Revenue · 2,000 DKK | Processing |
| MetaMarketing consent checked | Revenue · 2,000 DKK | Received |
| Google Analytics 4Analytics consent checked | Purchase validation | Validated only |
Order-economy snapshot · Independent configured target
Illustrative states. Receipt is not attribution; validation-only does not record a conversion. Profit snapshot excludes advertising costs and later refunds, may contain estimated shipping or pending payment fees, and is never added to revenue.
Illustrative product view · Example data
Server-side tracking and conversion quality
From context
to action.
Support Meta conversion measurement with controlled server-side payloads.
- 01
Review the context
Review event and marketing consent.
- 02
Work with the detail
Check the Meta destination.
- 03
Move the work forward
Inspect delivery state.
Matching context affects delivery; receipt is not attribution.
A connected capability
Meta Conversions API
Map ecommerce events to Meta server events with stable IDs and supported matching context.
Explore the complete server-side tracking workspace →Keep the context connected
The next part
of the picture.
Start with your business
See the whole picture.
Explore the workflows that matter to your team, then take the next step.
Build your demo agenda Browse all features →