Note
This guide explains how to test whether your tracking links work as expected in Airbridge. We recommend running this test alongside the tests provided by Self-Attributing Networks (SANs) or other ad channels.
Prepare the following before you start testing your tracking link.
You can find the device ID using an app provided by Airbridge.
Download the My Device ID by Airbridge app using the QR code below to find your device ID. The app also shows device information such as the device model and operating system version. The available device ID types vary by operating system, so see the Identifiers guide.
Before you run campaigns on an ad channel, check in advance that events from your ads are collected in Airbridge and attributed as intended. The steps below cover testing for click (ad_type=click) touchpoints.
Paste the test tracking link into a text tool such as Notepad.
Type and add a parameter filled with your test device's device ID. The parameter name is gaid_raw for Android and ifa_raw for iOS.
Test tracking link example https://abr.ge/@app_name/channel?click_id={click_id}&sub_id={sub_id}&tracking_template_id=e08703393962e4ec231d2ff1ff85ef68&routing_short_id=owgq4&ad_type=click
Android example (with gaid_raw)
https://abr.ge/@app_name/channel?click_id={click_id}&sub_id={sub_id}&gaid_raw=a4b7c084-da23-4e80-a9f2-d36c7afa134a&tracking_template_id=e08703393962e4ec231d2ff1ff85ef68&routing_short_id=owgq4&ad_type=click
iOS example (with ifa_raw)
https://abr.ge/@app_name/channel?click_id={click_id}&sub_id={sub_id}&ifa_raw=a4b7c084-da23-4e80-a9f2-d36c7afa134a&tracking_template_id=e08703393962e4ec231d2ff1ff85ef68&routing_short_id=owgq4&ad_type=click
Click the completed test tracking link on your test device to install the test app.
Attention
When testing an iOS app, consent to the ATT prompt. For why ATT consent is needed, see Prerequisites.
If needed, generate the in-app event whose attribution you want to test in the test app.
In the Airbridge dashboard, go to [Raw Data]>[Real-time Log (App)] and search for your test device's device ID. Enter the device ID exactly.
Check the following in the search results.
Event Category: Check whether the name of the event you generated in the test appears. If the event is collected, the event name appears here.
Channel: Check whether the ad channel name for the tracking link appears. If attributed to the ad channel, the channel name appears here.
If the event or ad channel doesn't appear in the real-time logs, check the following.
Item | Description |
|---|---|
Test tracking link | Create a tracking link for the ad channel you want to test in the Airbridge dashboard. For instructions, see the Create Tracking Links in the Airbridge Dashboard guide. |
Test app | The app that users download by clicking your ad. |
Test device | Use a mobile device only. The device must let you check its device ID. |
Device ID of the test device | Prepare the device ID of the mobile device you use for testing. |
ATT consent for iOS testing | To test an iOS app, you need to consent to the ATT prompt. If you don't, the IDFA isn't collected, and you can't verify attribution in this test. |
Checkpoint | What to check |
|---|---|
Device ID match | Make sure the device ID you searched for exactly matches the value you added to the tracking link. |
Missing IDFA (iOS) | Check whether you consented to the ATT prompt. If the IDFA is still missing, ask your developer whether the Tracking Authorize Timeout is long enough to wait for the ATT response. |
Collection time | Data can take a few minutes to appear. Search again in a little while. |
Tracking link parameters | Make sure the tracking link parameters such as |
Was this helpful?