Server-side tracking
Delivery status and retry handling
Investigate missing events through destination attempts and retry 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.
Make missing conversions investigable instead of silently disappearing.
- 01
Review the context
Find the event and destination.
- 02
Work with the detail
Read blocked, skipped or processing context.
- 03
Move the work forward
Review retry timing or configuration.
Recovery depends on failure type and provider response.
A connected capability
Delivery status and retry handling
Track destination-specific attempts, retry timing, blocked configuration and provider processing outcomes.
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 →