Server-side tracking

Purpose-specific consent and withdrawal

Align pending delivery with current purpose-specific consent.

Explore in a demo ↗See the workflow ↓

Part of Server-side tracking and conversion quality

bmanager.io / Server-side trackingExample workspace

One purchase. Every destination.

Order BM-2048 · Example delivery record

Server verified

01 · OrderEligible purchase
2,000 DKK revenue

02 · ConsentAnalytics: granted
Marketing: granted

03 · IdentityOrder-derived ID
Snapshot reused

Independent destination delivery
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

Separate profit signal

Order-economy snapshot · Independent configured target

760 DKK

Current consent recheckedStable identityDestination-specific attempts

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.

Keep event routing aligned with the consent recorded by the system.

01
Review the context
Review analytics and marketing separately.
02
Work with the detail
Recheck consent when delivery runs.
03
Move the work forward
Skip where required consent was withdrawn.

Withdrawal affects pending delivery, not events already sent.

A connected capability