Server-side tracking
Server-verified purchase events
Generate purchases from eligible order and payment state.
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.
Reduce reliance on a browser receipt page for purchase confirmation.
- 01
Review the context
Confirm server-side order eligibility.
- 02
Work with the detail
Capture values and stable order identity.
- 03
Move the work forward
Review purchase destination records.
Current generation applies to eligible configured storefront orders.
A connected capability
Server-verified purchase events
Build purchase events from eligible server-side order and payment state, using order values and stable order-derived IDs.
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 →