Server-side tracking

Affiliate server-side purchase callbacks

Connect eligible affiliate reporting with verified purchases.

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.

Connect affiliate conversion reporting with verified order context.

01
Review the context
Review purchase and consent.
02
Work with the detail
Check configured click or coupon context.
03
Move the work forward
Inspect the callback result.

Partner eligibility determines routing; a callback is not an extra sale.

A connected capability