This FAQ covers the most common questions media partners have when integrating with Airbridge, including the integration process, postback configuration, testing, and troubleshooting.
Integration with Airbridge follows the steps below:
Yes. A copy of the form is sent to the email address you provided.
The two options differ in who redirects users to the final destination after they click the ad. With C2S clicks, Airbridge handles the redirect. With S2S clicks, the ad channels do. See this article for details.
If you select S2S clicks, the ad channels need to implement the redirect. We recommend using C2S clicks, which requires no extra implementation, unless you have a specific reason to use S2S clicks.
They are parameters that must be included in your tracking link template. They're automatically added based on what you selected under [What to track with tracking links].
We also recommend including sub_id, ad_id, ifa_raw, and gaid_raw, plus as many other parameters as possible. For more details, see this article.
Yes. To send impression IDs, select Impression under [What to track with tracking links]. Airbridge then provides impression tracking links for the ad channel, and the impression ID will be populated as the click_id parameter value whenever an impression event occurs.
No, you should not include the hash symbol (#) in tracking link templates.
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.
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.
Contact the Airbridge integration team at integration@airbridge.io. See the Postback spec spreadsheet for the list of supported parameters.
See the Postback server IP addresses for media partners article.
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.
3. Run tests with Airbridge to verify that postbacks are sent via POST.
4. 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.
You can, but it’s not recommended. Without a device ID, device ID matching cannot identify users, which means the test can’t reliably verify whether attribution is working correctly.
Check the possible causes below. If you’ve checked everything but the issue persists, contact the Airbridge integration team at integration@airbridge.io.
Check whether you've selected Server-to-Server (S2S) clicks under [Tracking Link Template]>[What to track with tracking links] in the integration request form. This option requires the ad channel to handle redirection. Without that implementation, the tracking link can't redirect users. To change your selection, 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.
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.
Yes, it does. See the Cross-platform measurement article for details.
Yes, it does. See the CTV campaign tracking article for details.
Yes. The parameter that carries the IP address is required, since Airbridge uses the IP Matching Only method to identify users for CTV campaign measurement.
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.
Step | Owner | Description |
|---|---|---|
1. Submit the integration request form | Media partner | Fill out and submit the integration request form. See this article for instructions. |
2. Review the submitted form | Airbridge | Airbridge reviews the submitted form. This takes approximately 5 business days. |
3. Prepare for testing | Airbridge | Airbridge provides the tracking link and postback templates for testing. |
4. Run tests | Media partner, Airbridge | Using the provided templates, you and Airbridge verify that the tracking link and postback work correctly. |
5. Complete integration | Airbridge | Once testing is complete, Airbridge registers your ad channels on the Airbridge dashboard. |
C2S clicks | S2S clicks | Impressions | |
|---|---|---|---|
Required parameters | · | · · · | · · · |
Possible cause | What to do |
|---|---|
Endpoint error | Check that the endpoint URL you entered in the integration request form is correct and that the receiving endpoint is working. |
Missing required parameters | Check that all required parameters, including |
Missing authentication credentials | Check that all required credentials are registered in Airbridge. |
Test procedure not followed | Check that the test was run correctly following the Testing postback sending article. |
Item |
Description | Example |
|---|---|---|
Endpoint URL | Server address that will receive the data |
|
Headers | Media type of the resource |
|
Body | Structure of the data to receive |
|
Possible cause | What to do |
|---|---|
Airbridge SDK not collecting the event | Ask the advertiser to confirm that the Airbridge SDK is collecting the event. |
Event rules not followed | Confirm that the advertiser is following the event rules agreed upon between the ad channel and Airbridge, such as event name and postback URL format. |
Postback sending disabled | Ask the advertiser to confirm that postback sending is enabled on the Airbridge dashboard. |
このページは役に立ちましたか？