Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Postback

A server-to-server message reporting a conversion, install or in-app event back to the ad network or affiliate platform that should receive credit.
Ad TechtechnologyUpdated

Definition

A postback, also called server-to-server tracking, is a message one system's server sends directly to another's to report that something happened: an order, a lead, an install or an event inside an app. It usually carries an identifier issued at the click or ad, so the receiving platform can match the conversion to the interaction it served, plus details such as order value or event name.

The name describes the direction. The receiving platform has already handed out an identifier with the click; the advertiser's side posts the result back to it later. The browser, with its blockers, expired cookies and pages closed too early, is not involved in that last step.

In practice: affiliate postbacks and app measurement postbacks

In affiliate tracking, the guide to how affiliate tracking works describes the advertiser's server, or a server-side tag manager acting for it, sending the order to the affiliate platform with the click identifier stored when the visitor arrived. The platform matches the identifier to its logged click and records the conversion. Because the advertiser now controls the message, it can also send updates when an order is returned or cancelled, and it decides at that moment whether the affiliate should be credited at all; the guide to affiliate attribution and deduplication covers the rules for that choice and recommends an order reference in every postback.

In app measurement, the guide to app attribution, MMPs and SKAdNetwork describes the measurement partner deciding which network earned each install and returning the result to the networks as postbacks: the install to the winner, chosen in-app events after it. Those event postbacks are how an event-optimised campaign learns which users to find. On iOS, for users who have not allowed tracking, Apple's SKAdNetwork framework has Apple's own systems send an install postback to the network without identifying the user; as Apple's documentation describes, these arrive after a delay and carry more or less detail depending on campaign volume. The measurement plan for app installs assigns forwarding postbacks to networks to the measurement partner and keeps in-app behaviour with the analytics tool.

Why postbacks replace or back up browser pixels

A pixel reports a conversion from the customer's browser. Anything that stops the page loading the pixel, from a blocker to a payment step on another domain, loses the conversion, and nobody is told. A postback is sent from the advertiser's systems after the order exists, so it does not depend on the page. Many advertisers run both, with the platform removing duplicates, so that the postback is the main record and the pixel a backup.

That arrangement brings three duties. Duplicates must be removed, usually by sending the same order or event reference from both routes. The integration must be monitored, because a change to the order system can stop postbacks silently. And dates need care: a platform that records conversions when the postback arrives will place some of them on a later day than the system that sent them, which is one of the first things the guide to reconciling app install numbers asks a team to check.

Illustrative example — not a real result

A puzzle game studio lines up install dates

Tumblewray Puzzle Games sees its measurement partner credit one ad network with 4,820 iOS installs in June, while the network's dashboard shows 4,310. The gap of 510 looks like lost attribution. Comparing daily figures, the team finds the network dates each install by the arrival of its postback, which comes days after the install itself, while the partner dates by first open. Re-dating the network's July report to install day moves 420 installs back into June. The remaining gap of 90 sits within differences in attribution windows. The studio now compares the two sources only for months that closed at least two weeks earlier.

An MMP is the measurement partner that sends install and event postbacks to ad networks in app marketing. Deduplication removes the double count when a postback and a pixel report the same conversion. A Tracking Pixel is the browser-side method postbacks replace or back up. A Conversions API is a platform's own server-side interface for the same job, which an advertiser's systems call with conversion data rather than posting to a generic postback address.

Common confusions

  • A postback is a kind of pixel. A pixel fires from the browser; a postback is sent between servers.
  • Server-side means complete. A postback that stops after an order system change reports nothing, and nobody notices without monitoring.
  • Running a pixel and a postback doubles the count. Only if no shared reference lets the platform deduplicate.
  • Network and partner totals should match daily. They use different dates and windows, and some postbacks arrive late by design.
  • Postbacks may carry anything useful. Personal data has no place in them; an order reference and the values the platform needs are enough.

More terms to look up

Where this term is used

Sources

  1. SKAdNetwork — Apple Developer

Related