Note
This article guides you through the postback setup for the following channels.
Affle, Kwai For Business, Ultra, Whiz Adsbay, MOBICONNECT, ADCOLONY, yeahmobi, WIDER PLANET
To learn about the postback setup for ad channels other than the above, refer to this article.
Airbridge collects data and shares it with ad channels via postbacks. The data includes details such as event name, event timestamp, and more.
Using the data sent via postbacks from Airbridge, ad channels can optimize retargeting campaigns and run CPA or CPI campaigns.
The access level varies depending on your app role in Airbridge.
Owner and In-House Marketer users can configure postbacks.
Agency and Media Partner users, if authorized, can view postback URLs.
To configure postbacks, navigate to the [Postback] tab of each ad channel’s page in the Airbridge dashboard.
Postback sending is supported for all ad channels integrated with Airbridge, with the exception of keyword ad channels and custom channels.
Ad channels that support postbacks |
Ad channels that don’t support postbacks |
|---|---|
- All ad channels listed on the [Integrations]>[Ad Channel Integration] page - Google Ads (google.adwords) events are always sent via postbacks following integration, without any additional postback setup. | - Search ad channels such as Apple Search Ads (apple.searchads) - Custom Channels |
To configure postbacks by ad channel, navigate to [Postback] and click Configuration.
You can also find the list of ad channels receiving postbacks in the “Data Sending Status” section on the [Integrations]>[Integration Overview] page. For more details about the [Integration Overview] page, refer to this article.
Note
The postback keys required for enabling postback sending may differ by platform. Depending on the ad channel, you may not need to submit the postback keys for all platforms to enable postback sending.
Some ad channels require postback keys to receive postbacks. Get the key from the respective ad channel, navigate to [Postback]>[Integration Info] or [Postback]>[Event Schema], and click Configuration to submit the key.
Below is the list of ad channels that require postback keys. For guidance on the postback keys, refer to the integration guides for individual ad channels.
Kakao Moment (kakao)
Naver Display Ads (naver.performance_da)
Daangn (danggeun_market)
Unity Ads (unityads)
IronSource (ironsource)
Yandex Direct (yandexdirect)
Toss Ads (Toss)
Select events to send via postbacks and configure the delivery rules.
1. Navigate to [Postback]>[Event Schema] and click Configuration. Submit the postback integration key if necessary, and select the events to send via postbacks.
The events must have been predetermined to be sent by Airbridge and the ad channel. To send events that are not predetermined, you need to create postback URLs.
2. Configure delivery rules for selected events. Click the [gear] icon to specify the events subject to each delivery rule.
The delivery rules are divided into 2 categories, and only 1 rule per category can be configured for each event. Therefore, the selected events are subject to a total of 2 rules.
For more details about the delivery rules and categories, refer to the below.
Postback delivery rules are divided into 2 categories:
The “Attributed to” category allows you to decide whether to send only the events attributed to the respective ad channel or send all events regardless of the attribution results.
The “First only” category allows you to decide whether to send only the events that took place for the first time on a specific device or send all collected events to the ad channel. Ad impression event unable to send only events that occurred for the first time. All Ad impression event are sent.
For instance, you can configure to send only the first app installs attributed to the respective ad channel.
Attention
Airbridge uses the Airbridge Device UUID to identify whether an event took place for the first time on a specific device.
Let’s say an event took place twice on a single device. If different Airbridge Device UUIDs were collected, both occurrences will be counted as “first events.”
For effective retargeting campaigns, it is recommended that you send all collected events via postback, regardless of their attribution results or recurrence. Limiting postback to attributed events may affect the optimization of retargeting campaigns targeted at potential users.
To send all events, configure the delivery rules as below:
Attributed to: Send all events regardless of attribution results
First only: Send all collected events
3. After configuring the rules, click Save.
In the [Postback] tab of each ad channel’s page, you can navigate to [Event Schema], [Delivery Rule], [Postback URL], and [Integration Info] and view your postback configuration.
For more information, refer to the table below.
Page | Description |
|---|---|
Event Schema | For viewing the list of events being sent via postbacks and their event details |
Delivery Rule | For managing delivery rules configured for each event |
Postback URL | For creating and managing postback URLs |
Integration Info | For submitting and viewing postback integration key; Only available in ad channels that require the key |
Attention
Event postbacks have a direct impact on your campaign optimization and budget allocation. Consult with the ad channel before editing the postback URL.
Postback URLs allow you to send some supplementary events via postbacks. The events below require postback URLs:
Standard Events not predetermined to be sent
Custom Events
Navigate to [Postback]>[Postback URL] to create and manage postback URLs.
Follow the steps below to create postback URLs.
1. Navigate to [Postback]>[Postback URL] and click + Create Postback URL.
2. Select one or more events that require postback URLs. Select all events that use the same URL structure.
3. Configure necessary parameters. For detailed instructions, refer to the below. Click Import Existing URL to use preconfigured postback URLs.
Enter the postback URL shared by the ad channel.
Or click Import Existing URL to use preconfigured postback URLs. The process is simpler as these URLs have already been used to send postbacks.
Enter the parameter key and value of the postback URL.
The URL entered under “Set postback URL” is parsed to fill in the keys and values automatically. Click + Add to use additional parameters. You can preview the postback URL on the right.
Note that the postback URL must include parameters for device identification and event timestamp.
Configure the HTTP request method and header of the postback URL.
The request body can’t be modified in the Airbridge dashboard if the ad channel uses the POST method; contact your Airbridge CSM if necessary. It is also recommended to consult with your Airbridge CSM before making changes to other advanced settings.
4. After configuring the URL, click Save.
Navigate to [Postback]>[Postback URL] and click the [gear] icon to modify postback URLs.
Make sure to discuss with the ad channel in advance if you want to make changes to the Event Identifier (Channel) property, which is the postback event name displayed in the respective ad channel’s dashboard.
Was this page helpful?