In mobile marketing, a postback is an essential tool needed for measuring user activity and sharing data between ad functions and measurement partners. The information trade allows apps to properly assign attributions when an install occurs and make real-time changes based on user behavior.
For any apps that use server-based systems to communicate information with their partnering ad network or mobile measurement partner (MMP), postbacks are crucial in the sense that it enables the real-time transmission of information between servers, allowing marketers to make data-driven solutions on the go. Postback data helps determine which ads are driving conversions, identify the most profitable traffic sources, and other updates on user activity that may provide indications on changes that need to be made.
There are two types of postback:
Postbacks send data between platforms involved in the ad delivery process, including ad networks, advertisers, and MMPs, depending on which parties are involved. Below are the steps to activating postbacks and communicating user activity.
This procedure occurs continuously in real time, at every instance a user engages with an ad that generates attributions. Based on the MMP, marketers can set custom settings to accurately measure the areas that are important to them. For instance, Airbridge provides a range of events to be sent via postback, including installs, launch, launch deep link, in-app events, and custom events. Marketers can choose which events to track depending on the channel and ad.
Apple’s SKAdNetwork (SKAN) works differently from other postbacks since the introduction of the App Tracking Transparency (ATT) framework. Any app that collects user-level data for ad purposes is required to abide by the ATT framework, which divides users into two categories, consenting iOS users and non-consenting iOS users. Apps are only allowed to track the activity of consenting ones, and Apple also makes sure that this data is anonymized before sharing it and enabling postbacks.
In SKAN 3.0, marketers could only receive one postback with install and in-app event data combined from the first 24 hours of a user’s install. Starting with SKAN 4.0, they can receive up to three postbacks with three measurement windows, if Apple decides there is enough data to maintain crowd anonymity.
While postbacks and callbacks are used interchangeably today, callbacks originally refer to a ping that is requested from one server to another to communicate data on web platforms. Callback requests, also known as http or https requests, are triggered when a user engages with an ad and a subsequent event, similar to a postback. The callback can receive information like web/app data, attribution information, and raw data, and delivers this information using network servers and SDKs. Like postbacks, callback data is used to analyze campaign performances and make timely adjustments to marketing activities if necessary.
As a leading MMP for measuring mobile marketing data, Airbridge partners with multiple ad networks to track and share postbacks. On the Airbridge dashboard, marketers can configure postbacks and set custom parameters to track attributions and in-app events.
Currently, Airbridge supports the postback tracking of various events, from installs, in-app purchases, subscriptions, to custom events. For each campaign, marketers can choose the events they would like to measure and map custom postback URLs for each. These URL parameters will automatically track user activity and return the relevant postbacks to ad networks when certain events are detected.
