TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What is a postback? Server-to-server postbacks in ads and app attribution

A postback is a server-to-server request sent after an install or purchase to tell another system about it. What it contains, the main types, how to audit delivery with HTTP status classes, and where TapCub receives it.

Chloe Morgan Reviewed by Su He Also called callback Last updated Nov 17, 2026 Glossary

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:

  1. The click. A person taps an ad. The tracking link records the click and its click ID.
  2. The install. The person installs and opens the app. A mobile measurement partner (MMP) matches that first open to the click.
  3. 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.
  4. Event postbacks. Later events, such as a purchase, can trigger further postbacks, usually only if they happen within a set window after the install.
  5. 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

TypeSent whenFrom and toNotes
Install postbackFirst open after the installMMP to ad networkCarries the credited click and install time
In-app event postbackAn event you chose is reported, such as a purchaseMMP to ad networkEach event usually needs its own mapping and is usually sent only inside a window
SKAdNetwork postbackAfter the iOS install and conversion-value windowsApple device to ad networkSee 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

PostbackBrowser pixel or tagWebhook
Where it runsServer to serverThe visitor's browserServer to server
Needs the visitor's browserNoYesNo
Affected by blockers and closed tabsNoYesNo
What it carriesFields chosen through placeholdersWhatever the tag collectsAn event description, usually a request body
Typical useCredit an install or purchase to an ad networkCount a page view or conversion on a pageNotify 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 classPostbacksShareWhat it usually means
2xx48797.4%Received
5xx91.8%The receiving server failed
4xx40.8%The request was refused, often a malformed URL or a rejected value
Total500100.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.

  1. 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.
  2. Send the fields. Include media_source, campaign, install_source_status (organic or non-organic), match_type, platform and install_time. If you omit event_name, the event is stored as $app_install. A custom event name keeps the install off the installs tab. A non-organic install also copies media_source into utm_source, with medium mmp.
  3. 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.
  4. Fix the usual failures. No install rows means the token is wrong or a custom event_name was set. Everything under organic means media_source is missing or the status is organic.
  5. 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.

Chloe Morgan

Growth Strategist

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

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

What is a postback in marketing?

A postback is a server-to-server request sent automatically after an event such as an install or purchase. An attribution tool or advertiser sends it to an ad network's URL, with values like click ID, event name and revenue filled in.

What is the difference between a postback and a pixel?

A pixel runs in the visitor's browser, so blockers and closed tabs can stop it. A postback goes from one server to another and does not need a browser, which is why app installs and server-side purchases use it.

What is an SKAdNetwork postback?

It is a postback sent by an iPhone to an ad network after an ad-driven install. For ads signed with version 3 or later it sends one winning postback and up to five nonwinning ones, with a built-in delay of 24 to 48 hours.

How do you know if a postback was delivered?

Check the HTTP status of the receiver's reply. A 2xx status means it was received; 4xx points to a bad request such as a malformed URL, and 5xx means the receiving server failed.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics