Quick answer
In ads and app marketing, a postback is a server-to-server request sent automatically after an install, sign-up or purchase, so another system, often an ad network, learns about it. It is not the event in your own analytics; it is a notification about a result an attribution tool computed.
What is a postback?
In advertising and app marketing, a postback is a server-to-server request sent automatically after something happens, such as an install, a sign-up or a purchase, to tell another system about it. The sender is usually an attribution tool or the advertiser's server; the receiver is usually an ad network or an analytics tool. The request is typically a URL with placeholders that the sender fills in with real values at the moment of the event. Vendors also call it a callback or a server-to-server (S2S) call.
The word has other meanings, and a search for it returns all of them. In web development a postback is a form's data sent back to the same page that displayed it, as in ASP.NET's IsPostBack property. Payment processors also use the word for a notification to a merchant after a transaction. This page covers the advertising meaning only; the other two have nothing to do with ads or attribution.
How an ad postback works
A typical install-and-purchase path for a mobile app campaign:
- The click. A person taps an ad. The tracking link records the click and its click ID.
- The install. The person installs and opens the app. A mobile measurement partner (MMP) matches that first open to the click.
- The install postback. The MMP calls the ad network's endpoint with the placeholders filled in. In Adjust's setup the install callback is triggered when a user opens the app for the first time after installing.
- Event postbacks. Later events, such as a purchase, can trigger further postbacks, usually only if they happen within a set window after the install.
- The reply. The receiving server answers with an HTTP status. A 2xx status means the request was received; 4xx and 5xx mean it was not handled.
An illustrative template (macro names differ by vendor; this is not any vendor's syntax):
https://track.example.com/pb?click={click_id}&event={event_name}&rev={revenue}&t={timestamp}
At the moment of a purchase the sender substitutes values and calls:
https://track.example.com/pb?click=abc123&event=purchase&rev=24.90&t=1767225600
Here 1767225600 is 1 January 2026, 00:00 UTC. The receiver now knows that click abc123 led to a purchase worth 24.90, without any browser being involved.
What is inside a postback
A postback carries only the fields the sender was told to include. Adjust's install callbacks give a concrete list of placeholders:
| Field (Adjust placeholder) | What it tells the receiver |
|---|---|
{installed_at} | Timestamp of the first app open |
{conversion_duration} | Seconds between the click and the install |
{is_redownload} | 1 if this is the first activity after a redownload, otherwise 0 |
{gps_adid}, {idfa}, {idfv}, {adid} | Device identifiers |
{tracker}, {tracker_name} | The tracking link that was credited |
{activity_kind}, {created_at} | The kind of data point and when it was created |
If a placeholder has no data, Adjust omits it from the callback. Device identifiers and click IDs can single out a person, so check what you send, and to whom, against your privacy notice and consent settings.
Types of postback
| Type | Sent when | From and to | Notes |
|---|---|---|---|
| Install postback | First open after the install | MMP to ad network | Carries the credited click and install time |
| In-app event postback | An event you chose is reported, such as a purchase | MMP to ad network | Each event usually needs its own mapping and is usually sent only inside a window |
| SKAdNetwork postback | After the iOS install and conversion-value windows | Apple device to ad network | See below |
Apple's SKAdNetwork changes the pattern: the device, not an MMP, sends the postback. For ads signed with version 3 or later, the device sends one winning postback and up to five nonwinning ones to different networks (from iOS 14.6); nonwinning postbacks carry no conversion value or source app ID. From iOS 16.1, version 4 allows up to three postbacks for the winning attribution in three conversion windows. For ads signed with version 3 or earlier, the delay from the last conversion update to the postback is 24 to 48 hours. From iOS 15, the app's developer can receive a copy of the winning postback by naming an endpoint in the app's Info.plist.
Postback vs pixel vs webhook
| Postback | Browser pixel or tag | Webhook | |
|---|---|---|---|
| Where it runs | Server to server | The visitor's browser | Server to server |
| Needs the visitor's browser | No | Yes | No |
| Affected by blockers and closed tabs | No | Yes | No |
| What it carries | Fields chosen through placeholders | Whatever the tag collects | An event description, usually a request body |
| Typical use | Credit an install or purchase to an ad network | Count a page view or conversion on a page | Notify any system about any event |
A postback is best read as a webhook with advertising fields and a click ID attached. For how credit is divided once a conversion is known, see attribution; for acquiring the users in the first place, user acquisition.
Worked example: auditing postback delivery
Sample data: one day, an MMP sends 500 install postbacks to an ad network and logs the HTTP status of each reply.
| Status class | Postbacks | Share | What it usually means |
|---|---|---|---|
| 2xx | 487 | 97.4% | Received |
| 5xx | 9 | 1.8% | The receiving server failed |
| 4xx | 4 | 0.8% | The request was refused, often a malformed URL or a rejected value |
| Total | 500 | 100.0% |
How to recompute: 487 ÷ 500 = 97.4%; 9 ÷ 500 = 1.8%; 4 ÷ 500 = 0.8%; 500 − 487 = 13 postbacks not received. If the network's console shows 487 installs against the MMP's 500, the 13-install gap is explained by the 13 failed replies, not by attribution disagreeing. Check the 4xx ones first, because retrying a malformed request will not fix it; the 5xx ones are worth replaying if your tool allows it.
Common misunderstandings about postbacks
- "The postback is the event." The event is recorded by your own SDK or server. The postback is a notification about a result the MMP computed, so its counts depend on the MMP's matching window and de-duplication and will not equal your own analytics exactly.
- "Every postback is real time." SKAdNetwork postbacks are delayed by design; for version 3 and earlier, they arrive 24 to 48 hours after the last conversion update.
- "The URL can be shared." A receive URL with a token in it works like a password. Do not paste it into public places.
- "A 200 means the click was credited." A 2xx only means the request was received; the receiver's own rules decide whether it counts.
- Mixing up the meanings. A web-form postback and an ad postback share a word and nothing else.
Postbacks and TapCub
Suppose the 487 installs above come from an app campaign. TapCub does not decide whether a click matches an install and is not an attribution provider; it receives the result your attribution platform computed and puts it next to the rest of your data.
- Copy the receive URL. Open the MMP tab in App analytics › Configuration › Business settings and copy the endpoint. It is
POST /api/v1/mmp/plus the project's token. If you rotate the token, the old URL stops working immediately, and the token should not be published. - Send the fields. Include
media_source,campaign,install_source_status(organicornon-organic),match_type,platformandinstall_time. If you omitevent_name, the event is stored as$app_install. A custom event name keeps the install off the installs tab. A non-organic install also copiesmedia_sourceintoutm_source, with mediummmp. - Read the installs. Open All-platform analytics › Business › Channel ROI and choose the Installs tab: installs by media source, organic versus non-organic, campaign and platform. In event analysis you will find
$app_install. - Fix the usual failures. No install rows means the token is wrong or a custom
event_namewas set. Everything under organic meansmedia_sourceis missing or the status isorganic. - Keep the two attribution ideas apart. The attribution analysis in All-platform analytics › Behavior › Behavior analysis shares credit across website sessions before a conversion; it does not use install postbacks.
Sources
- Apple Developer Documentation, Receiving ad attributions and postbacks: SKAdNetwork postback counts, winning and nonwinning postbacks, timing and the developer copy.
- Singular, What is a postback?: install and in-app event postbacks, the alias "callback", and the SKAdNetwork delay.
- Adjust Help Center, article "Install callbacks" (help.adjust.com/en/article/install-callbacks; given as text because the site redirects automated requests in a loop): when the callback fires and which placeholders it carries.
- Microsoft Learn, Page.IsPostBack property: the web-form meaning of postback.
- MDN Web Docs, HTTP response status codes: meaning of 2xx, 4xx and 5xx.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Growth Strategist
Explores acquisition channels, activation, and conversion experiments, turning data insights into actionable growth hypotheses and evaluation methods.