DFINERY Self-Verification Guide
About this document
This document is a guide for checking basic integration and event integration after linking with DFINERY.
References before viewing the document
Before viewing this document, you can check whether the SDK integration is working properly using the preliminary checklist below.
4 ways to self-verify
There are three ways to check whether integration is complete.
- Application management menu
- LiveBrix Menu
- Check event report figures
- Utilize RAW data using the bigdata export function (recommended)
(1) Application management menu
Once event linking is complete, the first menu you can check is the Application Management menu.
After linking adbrix SDK, you can check the details of events called at least once and User / Event Property details.
-
Click Applications menu in Setting & SDK
-
Click the management button at the top right of the app list
-
You can check the list of called events
You can check the details below in this event list.
- PreDefined Events : Shows event call history predefined in adbrix SDK. All such events will be marked as abx:XXXX .
- Custom Events : Displays events customized by the user in addition to PreDefined Events. All such events will be marked as custom:XXXX .
- Trigger Events : This is an event called by the server when certain conditions are met in Growth Action. All such events are marked as trg:XXXX.
- User Properties : User information set through the setUserProperty API of adbrix SDK. Details pre-defined by adbrix SDK are defined as abx:xxxx / properties custom entered by the user are defined as custom:xxxx.
- Event Properties : Displays information within events called from adbrix SDK. Details predefined by adbrix SDK are defined as abx:xxxx / event information custom entered by the user is defined as custom:xxxx.
(2) LiveBrix
In LiveBrix, you can view the details of events called from the adbrix SDK in real-time streaming in 1-minute increments for up to 25 minutes. In this menu, you can quickly check only the event call details, but you cannot check the Event / UserProperty details.
1) Click the Analytics -> LiveBrix menu on the left menu of the Dfinery console.
2) When you click, you can check the details of what is currently being called through the advertising action/event.
- Advertising Action: You can check the click and conversion history of the tracking link.
- Event: You can check the event that is currently being called.
(3) Check event report
You can check reports by date and time through the event report. The event report is the most accurate way to check when testing SDK integration after SDK integration is completed.
[[Citation:Information]] Report is updated every hour. (Ex. If the test was conducted at 14:05, the report can be checked after 15:00)
1) Click the Analytics -> Data Explorer menu on the left menu of the Dfinery console.
2) Click the Create New Report button in the upper right corner and select General Event Analytics from the report creation menu.
3) Edit the Group by menu in Report Builder and set Group by as Daily -> Platform -> Event Name as shown below. If you want to check the event call history by time zone, set Daily -> Hourly -> Platform -> Event Name.
[[Quote: Information]] If you want to check the event call history by time zone, set Daily -> Hourly -> Platform -> Event Name.
[[Quote: Information]] In Group By, you can set Event properties / User properties called for each event.
4) You can select the report date and details as options in the Conditions menu of Report Builder. After selection, click the Create Report button.
[[Citation: Information]] By entering the ADID (ADID/IDFA settings) or device model (set as Model) of the test device you are using in Analytics Conditions, you can check only the details corresponding to the set conditions in the report.
5) Check the event call history in the generated report.
(4) Utilize RAW data using the Bigdata export function (recommended)
You can verify the data in raw data form by adding the column you wish to extract as shown in the image below.
-
Data studio > Bigdata export > Create Export (top right) > Create new task > Select App Event
-
Table Design - Add the condition values required for verification to the group by condition.
If it is an event verification, the event name is required among the condition values, and if it is a property verification, the property name entered by your company's development team is added.
-
Conditions - You can set the period for which an event was called or filter out only specific events.
Please check with your company's development team to see if the connection is working properly.
Deep link verification
Deep linking is a function that opens an app for users who already have the app installed. In adbrix SDK, you can analyze this through deeplinkOpen API, and through this, you can check user re-engagement, which is one of the important indicators of marketing.
To verify this, both Android and iOS must be connected to the deeplinkOpen API.
(1) Creating a tracking link
To verify deep links, a tracking link with deep links must first be created. Please refer to the guide below to create a tracking link.
(2) Deep link test
Once the deep link-enabled tracking link is created, you can perform a deep link test through it. Deep link testing follows the procedures below.
-
The test app must be installed on your test device.
- The test is conducted by setting the following two cases.
- The app is completely terminated and moved from memory.
- The app is switched using the home button.
- Click the tracking link on your test device. (We recommend clicking this in your Mail client.)
- The app opens with a deep link and moves to a screen set up as a deep link.
(3) Check DeeplinkOpen API integration.
If you see that you are moving to a screen set up as a deep link through a deep link, you must check whether the linked DeeplinikOpen API has been opened properly. The API call can be confirmed through the tracking link report.
[[Quote:Warning]] Report is updated every hour. (Ex. If the test was conducted at 14:05, the report can be checked after 15:00)
1) Click the Action button on the tracking link you tested and click Report.
2) In Report Builder -> Conditions, select New Install, Re-install, and Deeplink Open for Open Attribution Type. Then, set the test date and click the Run button.
3) Check Deeplink Open figures through the generated report.
inquiry
If you have any additional questions regarding integration and verification, please contact us by email below.
Integration and verification inquiries: support-tracker@adbrixsupport.zendesk.com