Server-side tracking

Real orders. Clearer signals. Every delivery visible.

Connect eligible server-confirmed purchases with Google Ads, Meta and Google Analytics 4. Keep consent, stable identity and separate revenue and profit signals visible as each destination processes the event.

Explore in a demo ↗Explore the features ↓

13 connected capabilities

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

A stronger purchase source

Generate eligible purchases from order and payment state instead of treating browser activity as confirmation.

Consent stays in the flow

Separate analytics and marketing purposes and recheck current consent before pending deliveries.

Evidence beyond a send attempt

Follow destination states, retry timing and provider processing to investigate gaps.

The workflow

Built for the way
the work moves.

01
Verify the order
Capture eligible purchase values and stable order-derived identity.
02
Check each purpose
Route each destination with the consent and context it requires.
03
Follow the destination
Inspect receipt, processing, retries or blocked configuration.

One purchase. Stable identity.

Repeated capture attempts reuse event and destination records. A separate configured profit signal uses an order-economy snapshot.

Preserve captured values through retries
Keep revenue and profit destinations separate
Classify new and returning purchases without adding sales

Consent is part of every delivery.

Current recorded consent is checked again before sending. Withdrawal can skip pending deliveries.

Separate analytics and marketing purposes
Inspect skipped and blocked reasons
Check configuration before relying on measurement

Explore the detail

A dedicated place
for every capability.

See how each part of server-side tracking works, and where it connects.

First-party event ingestion

Capture validated commerce events with consent and separate delivery records.

Explore feature 02

Server-verified purchase events

Generate purchases from eligible order and payment state.

Explore feature 03

Google Ads server-side conversions

Follow configured Google Ads conversion delivery and processing.

Explore feature 04

Meta Conversions API

Send supported Meta events with stable identity and matching context.

Explore feature 05

GA4 Measurement Protocol

Send supported analytics events with client and session context.

Explore feature 07

Stable IDs and duplicate guards

Reuse captured purchase identity across repeated attempts.

Explore feature 08

Delivery status and retry handling

Investigate missing events through destination attempts and retry state.

Explore feature 09

Tracking activity and outgoing request inspection

Give authorized teams read-only event and delivery evidence.

Explore feature 10

Separate profit conversion signals

Provide a separate order-economy signal where configured.

Explore feature 11

New and returning customer purchase signals

Distinguish acquisition and retention using known customer history.

Explore feature 12

Tracking destination configuration tests

Check destination configuration before relying on measurement.

Explore feature 13

Affiliate server-side purchase callbacks

Connect eligible affiliate reporting with verified purchases.

Explore feature

Good to know

The practical
questions.

Does receipt prove ad attribution?

No. Receipt and processing describe destination handling. They do not prove attribution or create a second sale.

What is in the profit signal?

An order-economy snapshot with its recorded costs. Advertising costs and later refunds are excluded. Pending payment fees or estimated shipping can affect the snapshot. Revenue and profit are separate signals and must not be added together.

Does withdrawal stop pending deliveries?

Current consent is rechecked when delivery runs. Pending deliveries can be skipped after withdrawal; this workflow does not recall events already sent.

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 →