Testing the Airbridge SDK Integration for Marketers

Run one of these 4 tests to confirm the Airbridge SDK is working as intended. Choose the test that matches your purpose.

Before you begin

Make sure the following are in place before you test.

  • Install the Airbridge SDK.

  • For iOS apps, confirm that the ATT (App Tracking Transparency) prompt is implemented.

  • For iOS apps, confirm that the Tracking Authorize Timeout is long enough to wait for the ATT response.

  • Prepare a test device that does not have the app installed.

  • Make sure you have access to [Settings]>[Testing Console] in the Airbridge dashboard.

Test attributed installs

This test confirms that app install events from a campaign tracking link are attributed to Airbridge as expected.

Attention

When testing on iOS, tap Allow on the ATT prompt. If Airbridge sends the install event before the ATT response, the IDFA is not collected and attribution cannot be verified. If the IDFA is still not collected, check with your developer whether the Tracking Authorize Timeout is long enough to wait for the ATT response.

  1. Prepare a test device without the app installed, or uninstall any existing app.

  2. In the Airbridge dashboard, go to [Settings]>[Testing Console] and open the [Attributed Installs] tab. Enter the device ID, such as GAID or IDFA, of the test device in its original format including hyphens (-), then select Register to generate a QR code.

  3. Scan the QR code with the test device, or select Copy URL and open the copied address on the device.

  4. Once the temporary web page loads, install the app. For released apps, install from the app store. For unreleased apps, download the file directly or use a testing program such as Google Play Console or TestFlight.

  5. After installing the app, launch it. On iOS, tap 'Allow' on the ATT prompt.

  6. Check the test result in the dashboard. If no result appears or the test fails after a reasonable wait, uninstall the app and try again.

  7. To review detailed data, select View real-time logs. You can check the test device's information in [Raw Data]>[App Real-time Logs].

Choose one of the three methods below to verify the result, depending on your purpose.

Test organic installs

This test confirms that install events from direct app store installs, without clicking an ad with a tracking link, are collected correctly.

  1. Prepare a test device without the app installed, or uninstall any existing app.

  2. Install the app on the test device and launch it.

  3. In the Airbridge dashboard, go to [Raw Data]>[App Real-time Logs] and look for events from the device ID. Event collection can take up to 10 minutes.

  4. If Install does not appear after a reasonable wait, uninstall the app and try again.

Note

The first launch after installing the app is recorded as an Install event, not an Open event. Launches after the Install event is collected are recorded as Open events.

Test event taxonomy

This test confirms that events other than app installs are collected according to the event taxonomy.

Note

Airbridge users with Agency or Media Partner app roles cannot access [App Real-time Logs].

  1. Go to [Raw Data]>[App Real-time Logs] in the Airbridge dashboard.

  2. Enter the deviceUUIDof the test device in the search bar. You can also search by user ID or event category.

  3. Check the event details at the following fields.

    • Category: eventData.goal.category

    • Action: eventData.goal.action

    • Label: eventData.goal.label

    • Value: eventData.goal.value

    • Semantic attributes: eventData.goal.semanticAttributes

    • Custom attributes: eventData.goal.customAttributes

Test deep linking

This test confirms that users are routed to the intended in-app page via the configured deep link after clicking an ad with a tracking link. You can run this test in the Airbridge dashboard under [Settings]>[Testing Console] on the [Deep Linking] tab. For details, see the Airbridge Deep Linking Test for Marketers guide.

Common mistakes checklist

If attribution cannot be verified, review the following items in order.

  • Make sure the SDK is installed correctly, and ask your developer for help if needed. For details, see the

    SDK Quickstart guide.

  • Confirm that you launched the app after installing it on the test device.

  • For iOS apps, confirm that you tapped Allow for app tracking on the ATT prompt.

  • If the Install event was sent before the ATT response, the IDFA may have been missed. Check whether the Tracking Authorize Timeout is long enough to wait for the ATT response.