Global Postback: Account-Level Conversion Tracking

Global vs per-offer postbacks

Per-offer postback — you paste your postback URL into each offer's settings individually. Fine for a handful of offers, painful at scale, and easy to forget one.
Global postback — you set the postback once for the whole account and every current and future offer inherits it.

Most affiliate trackers (Voluum, RedTrack, BeMob, ClickFlare) and most CPA networks support a global or universal postback. It's the default choice once you're running more than a few offers.

How a global postback fires

Your tracker generates an outbound offer link that includes a click-ID macro.
The user clicks; the click ID rides along to the offer.
On conversion, the network looks up your account-level global postback and pings it, substituting the click ID, payout, and offer ID into the URL macros.
Your tracker receives the ping, matches the click ID to the original click, and records the conversion.

https://yourtracker.com/postback?cid={click_id}&payout={payout}&offer={offer_id}

Setting one up

There are two sides to configure:

Network side — find the global / universal postback field in account settings and paste your tracker's postback URL with the network's macro tokens.
Tracker side — enable postback as the conversion-tracking method and confirm the click-ID parameter name matches what you send on the outbound click.

Then fire one test conversion and confirm it lands before you scale spend.

The click-ID requirement

A global postback is useless if there's nothing to match on. You must pass a unique click ID (often carried in a SubID) on the outbound click so the network can return it in the postback. No click ID means the postback fires but your tracker can't tie it to a click — an unattributed conversion. This is the single most common reason a global postback "doesn't work."

When you still need per-offer postbacks

Override with a per-offer postback when an offer has a different conversion event you want tracked separately (a lead vs a sale), a different payout structure that needs its own macro, or when you're routing one offer through a different tracker. Global covers the common case; per-offer is the exception.

Frequently asked questions

What is a global postback?

A global postback is a single conversion-tracking callback URL you configure once at the network or tracker account level, so every offer reports its conversions back automatically. It replaces the need to paste a separate postback URL into each individual offer.

What's the difference between a global postback and a per-offer postback?

A per-offer postback is configured separately inside each offer's settings. A global postback is set once at the account level and applies to every current and future offer. Global is the efficient default for running many offers; per-offer is used when a specific offer needs a different event, payout macro, or tracker.

What do I need to set up a global postback?

Two things: your tracker's postback URL with the right macro tokens (click ID, payout, offer ID), and a unique click ID passed on the outbound click so the network can return it. You paste the postback URL into the network's global postback field, then send a test conversion to confirm it matches.

Why isn't my global postback firing or matching?

The most common cause is a missing or mismatched click ID — without a unique click ID on the outbound click, the postback fires but your tracker can't tie the conversion to a click. Other causes include a macro token name that doesn't match the network's, a malformed postback URL, or the conversion event being different from the one the network reports.