Skip to main content
This FAQ covers the most common questions media partners have when integrating with Airbridge, including the integration process, postback configuration, testing, and troubleshooting.

Request integration

Integration with Airbridge follows the steps below:
Yes. A copy of the form is sent to the email address you provided.

Configure postback URL

For event name and device model, add the following parameters to the postback URL:
  • Event name: select {@postback.eventName} as the parameter value.
  • Device model: for Android, select {device.manufacturer} or {device.deviceModel} as the parameter value. For iOS, select {device.deviceIdentifier}.
For any other data you want to receive, add suitable parameters to the postback URL. Refer to the parameter descriptions in the Postback spec spreadsheet to find suitable parameters, and see this article for configuration instructions. Check with the advertiser whether any values, such as Transaction ID, need to be collected through the Airbridge SDK.
Go to [Postback URL]>[Credentials for advertiser authentication] and check the We assign credentials to advertisers checkbox. Enter a credential name, which will be used as the parameter key in the postback URL. The {@postback.apiKeySet} macro will be added as the value of that key. The advertiser will then need to register the credentials on the Airbridge dashboard to send postbacks.

During integration

See the Testing postback sending article.
Check the possible causes below. If you’ve checked everything but the issue persists, contact the Airbridge integration team at integration@airbridge.io.
This is expected during testing. In live campaigns, fraud validation rules are only applied if the advertiser has set them up under [Fraud Validation Rules] on the Airbridge dashboard. We recommend checking the advertiser’s fraud validation rules before campaigns go live.

After integration

Postback

Contact the Airbridge integration team at integration@airbridge.io. See the Postback spec spreadsheet for the list of supported parameters.
Follow the steps below.
  1. Confirm that your ad channel server can receive data via POST.
  2. Reach out to your Airbridge contact to request the change, and provide your endpoint URL, headers, and body following the example below.
  1. Run tests with Airbridge to verify that postbacks are sent via POST.
  2. Once testing is complete, Airbridge will switch the postback method for the ad channel to POST.
Yes. First, the advertiser needs to set up the Airbridge SDK to collect the Custom Event, so confirm the setup with the advertiser. Once the Custom Event is collected by Airbridge, it will automatically be sent via postback.
Yes. Note that ad channels can only receive Semantic Attributes that the advertiser is collecting through the Airbridge SDK.
Yes. See the Web event postback section for details.
Yes. Note that some app-only parameters, such as deviceId and deviceIdType, aren’t supported for web events.
Yes. Web attribution doesn’t apply the lookback window. See the Web attribution section for details.

Troubleshooting

Check the possible causes below. If you’ve checked everything but the issue persists, contact the Airbridge integration team at integration@airbridge.io.
This happens because the two values are determined by different sources. Use whichever fits your needs.
  • {device.country}: based on the language and region set on the device.
  • {device.clientIPCountryCode}: based on the IP address the device is connecting from.
No, you don’t need to. [Events for Attribution] is not related to retargeting campaigns.The default option, All Events, makes all events eligible for attribution, including Installs (App), Deeplink Opens (App), Deeplink Pageviews (App), and their subsequent events. Switching to Specific Events excludes some events from the attribution process. We recommend keeping All Events unless the advertiser wants to either:
  • Exclude Installs (App) and their subsequent events from attribution.
  • Exclude Deeplink Opens (App), Deeplink Pageviews (App), and their subsequent events from attribution.

Dashboard access

As of February 2026, no. Ask the advertiser to grant you access to their apps. Once they grant access, you’ll receive an invitation link that you must accept within 72 hours. By default, you’ll only have access to the data attributed to your ad channels.
Contact the Airbridge integration team at integration@airbridge.io. See the App roles section for the access scope of that role.
Yes. The Airbridge Demo app offers a 30-day free trial.
No. Ablog is a test app and is only available for download from app stores.

Cross-platform measurement

Yes, it does. See the Cross-platform measurement article for details.
Yes, it does. See the CTV campaign tracking article for details.

Other

Yes. To request a change, contact the Airbridge integration team at integration@airbridge.io. Note that the ad channel ID cannot be changed, since it’s the unique identifier that shows which ad channel a tracking link belongs to.
Contact the Airbridge integration team at integration@airbridge.io with the advertiser’s app information.