在 Airbridge 面板进行的 SDK 测试

您可以在 Airbridge 面板测试 Airbridge SDK 是否正常运行。请在测试前先安装 Airbridge SDK。

• 为营销人员的 Airbridge SDK 测试指南

After completing the Airbridge Android SDK setup, you can test whether it works properly using real-time logs, test sites, etc. Prepare the following information before testing the Android SDK.

测试设备的 GAID

注意

为了区分要监测广告绩效的 App 数据和仅用于测试 Airbridge 功能的 App 数据，需要在 Airbridge 面板中选择不同的 Airbridge App 模式。

对于开发用的 App，需要在 Airbridge 面板中直接输入 App 的包名（Package Name）。有关更多信息请参阅 本指南。

Check whether the Airbridge Android SDK is operating properly.

Follow the steps below to check whether the Install events are being collected by the Android SDK.

1. Prepare a test device where the app is not installed, or if the app is already installed, delete it before testing.

2. Set the SDK log level to DEBUG.

3. Install the app on the test device. After installing the app, launch it so that the Install event is collected.

The first Open event collected by Airbridge is recorded as an Install event. Therefore, the Open may not be recorded when the app install event is collected.

4. Navigate to [Raw Data]>[App Real-Time Log] in the Airbridge dashboard and find the events with the test device's GAID in the real-time logs. If the Install event can be found in the real-time log, you can confirm that the SDK is working as intended. It may take up to 10 minutes to check the Install event in the [App Real-time Log].

5. If the Install event is not confirmed in the [App Real-time Log] even after a sufficient amount of time, check whether the Install event is in the SDK log. When the Install event is in the SDK log, delete the app from the test device and reinstall it.

If the Install event is still not confirmed, contact your Airbridge CSM and share your SDK logs. If you don't have a designated Airbridge CSM, contact the Airbridge Help Center.

Airbridge initiates the attribution process when a Target Event occurs. The Install event is a typical Target Event. By checking the attribution result of the Install event, you can confirm whether the process from event collection to attribution is operated successfully.

1. Prepare a test device where the app is not installed, or if the app is already installed, delete it before testing.

2. Set the SDK log level to DEBUG.

val option = AirbridgeOptionBuilder("YOUR_APP_NAME", "YOUR_APP_SDK_TOKEN")
    .setLogLevel(AirbridgeLogLevel.DEBUG)
    .build()
Airbridge.initializeSDK(this, option)

3. Access the Attribution Integration Test site on your test device.

4. Enter the App Name and GAID, then click Submit. The App Name can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.

5. Click Test Install Attribution to move to the Google Play Store. If the Airbridge Android SDK is not installed on the app that is available for download in the Google Play Store, use tools like Android Debug Bridge to install the app with the SDK.

6. Install the app on your test device. You must launch the app after install to collect the Install event.

The first Open event is recorded as an Install event in Airbridge. Therefore, the Open event may not be recorded if the Install event is collected.

7. Navigate to [Raw Data]>[App Real-Time Log] in the Airbridge dashboard and find the events with the test device's GAID in the real-time logs. If the Install event can be found in the real-time log, you can confirm that the SDK is working as intended. It may take up to 10 minutes to check the Install event in the [App Real-time Log].

8. Check whether the Install event data is collected as follows. The data must match the details below to confirm that the attribution process has been completed successfully.

• Event Category: Install

• gaid: GAID entered in the attribution test site

• attributionResult.channel: test_sdk

• attributionResult.attributedTouchpointOriginURL: https://abr.ge/@${YOUR_APP_NAME}/test_sdk?campaign=test_sdk_campaign&device_uuid=${YOUR_GAID}

9. If the Install event is not confirmed in the [App Real-time Log] even after sufficient time, check whether the Install event is in the SDK log. When the Install event is in the SDK log, uninstall the application on the test device and reinstall it.

If the Install event is still not confirmed, contact your Airbridge CSM and share your SDK logs. If you don't have a designated Airbridge CSM, contact the Airbridge Help Center.

Check whether the event and user data are being collected as intended.

Check whether the events are being collected by the Airbridge Android SDK as defined in your Airbridge event taxonomy by following the steps below.

{
   ...
   "eventData": {
      ...
      "goal": {
         "category": "airbridge.ecommerce.order.completed",
         "semanticAttributes": {
            "value": 10000.0,
            "totalQuantity": 1000,
            "currency": "krw",
            "transactionID": "transaction_1",
            "products": [
               {
                  "quantity": 10,
                  "productID": "coca_1",
                  "price": 1.99,
                  "name": "Coca cola",
                  "currency": "usd",
                  "position": 1
               },
               {
                  "quantity": 5,
                  "productID": "fanta_1",
                  "price": 2.5,
                  "name": "Fanta Orange",
                  "currency": "usd",
                  "position": 2
               },
               {
                  "quantity": 1,
                  "productID": "terra_pack_1",
                  "price": 10.99,
                  "name": "Terra 12 Pack",
                  "currency": "usd",
                  "position": 3
               }
            ],
            "inAppPurchased": true
         }
      }
   },
   ...
}

提示

如果未在 Airbridge Android SDK 设置用户信息收集，则无需以下检查。通过 Airbridge Android SDK 收集用户 ID、邮箱等用户信息，有助于更丰富地使用 Airbridge，例如与第三方解决方案集成。

Check whether the user data is collected as intended by the Android SDK.

{
    ...
    "eventData": {
        ...
    },
    "user": {
        "externalUserID": {User ID},
        "externalUserPhone": {User Phone},
        "alias": {
            "key": {value}
        },
        "attributes": {
            "key": {value}
        },
        "isClientSideHashed": true
    },
    ...
}

Check whether the deep linking feature configured in the Airbridge Android SDK is working properly.

Before testing the deep link, make sure the following items have been set up.

Airbridge provides a website for testing deep links. If you want to test deferred deep links, you need to uninstall the app from your test device.

1. Visit the deep link testing site from your test device. You can access the website directly by using the QR code below.

2. Enter the App Name you registered with Airbridge. You can find it on the [Settings]>[Tokens] page in the Airbridge dashboard.

If you want to test a specific deep link address, enter the scheme deep link into the Deeplink URL field. The scheme deep link format is {YOUR_SCHEME}://...

If you're using a custom domain, make sure to enter your custom domain.

3. Click one of the buttons listed below. Click the button depending on the deep link type you are testing.

Note that you can only test deferred deep links if the app is not installed on your test device.

4. When the Deep Link Open event is successfully collected, you can find it on the [Raw Data]>[App Real-time Log] page in the Airbridge dashboard.

Once you find the Deeplink Open event on the [Raw Data]>[App Real-time Log] page in the Airbridge dashboard, additional items must be confirmed. The items vary depending on the button that was clicked. If the deep link is functioning as intended, all items should be confirmed. Refer to the below information for the items that should be confirmed.

Refer to the information below for troubleshooting regarding deep links.