Using Marketing Attribution¶
Events are all activities that users perform while playing games, such as game installations, game updates, and item purchases. Marketing attribution is a function that collects these event logs and sends them to the server to track user activities. The tracking data from marketing attribution can be analyzed and utilized in various ways. For example, you can track events such as level-ups and item enhancements that occur within the game to predict user behavior and guide users to enjoy the game more.
Using the Hive SDK, you can use third-party app marketing attribution that can track user entry paths into user apps and user activities. The third-party app marketing attribution supported by the SDK includes five options: Adjust, Singular, AppsFlyer, Firebase Analytics, and Airbridge.
Features and support scope¶
The features provided by marketing attribution are as follows:
- Automatic event tracking: Automatically tracks basic events such as app installation, app opening, app updates, and in-app purchases, and sends data to the attribution server.
- Manual event tracking: Directly defines events that you want to collect in the game, tracks them, and sends data to the attribution server.
- PG payment purchase completion information collection: Purchase completion events can be collected even when using PG payments.
- Attribute transmission: When manually tracking events, additional event information can be collected through attributes.
- Ad exposure information transmission: When ads are displayed in games, measures and transmits ad platform type, ad exposure location, exposure timing, ad revenue per exposure, etc.
- SDK Signature: A solution to prevent spoofing (ad fraud that sends false events to ad servers). Prevents ad fraud by verifying valid signature information to distinguish between true/false events.
- App uninstall tracking: Sends silent push notifications once a day to check whether the app has been uninstalled.
- Deferred deep link: Directs users who have not installed the app to the app store to encourage installation, and when they run the installed app, redirects users to the designated content location.
- Market-specific traffic measurement settings: Sets identifiers to analyze app installation performance for markets (Google Play Store, One Store, Huawei Store, Galaxy Store, etc.).
Note
Ad information transmission, SDK Signature, app uninstall tracking, deferred deep link, and market-specific traffic measurement settings are features supported only in mobile game apps.
The types and features of supported marketing attribution third-party apps differ depending on whether the game app is in a mobile or PC environment.
Mobile¶
The mobile environment supports all five marketing attribution apps, and the features provided by each app are as follows:
Feature | Adjust | Airbridge | Appsflyer | Firebase Analytics | Singular |
---|---|---|---|---|---|
Automatic event tracking | O | O | O | O | O |
Manual event tracking | O | O | O | O | O |
PG payment purchase completion information collection | O | O | O | O | O |
Attribute transmission | O | O | O | O | O |
Ad information transmission | O | O | O | O | O |
SDK Signature | O | O | - | - | - |
App uninstall tracking | O | O | O | - | - |
Deferred deep link | - | O | - | - | - |
Market-specific traffic measurement settings | - | O | - | - | - |
PC¶
The PC environment supports only two options: Airbridge and Appsflyer (Steam).
Feature | Airbridge | Appsflyer |
---|---|---|
Automatic event tracking | O | O |
Manual event tracking | O | O |
PG payment purchase completion information collection | O | O |
Attribute transmission | O | O |
Community and web shop¶
In Community & Web Shop, only Airbridge's automatic event tracking feature is available for marketing attribution. Additionally, events can be collected in both mobile and PC environments.
Note
In Community & Web Shop, event collection is possible not only with Airbridge but also with Google Tag Manager (GTM). You can collect events by issuing a GTM code and registering it in the Hive console. For detailed information, please refer to the console guide.
Community automatic collection events¶
The events that Airbridge can automatically collect from community sites are as follows:
Event | Event details | Trigger point | Components (reference) | Airbridge event list matching |
---|---|---|---|---|
Login | Login | When entering the page normally after login completion | - | Login (Standard) |
Login | Sign up | When creating a community ID | - | Sign up (Standard) |
Login | Logout | When selecting the logout button | - | Logout (Standard) |
Post (Content) | Main screen view | When selecting a post displayed on the main screen | • Post information (title, image/video, nickname, registration date, view count, comments) • Board type • Exposure position in list | Home screen view (Standard) |
Post (Content) | Category/menu selection | When selecting category/menu button | • Category/menu name | Product list view (Standard) |
Post (Content) | Write button selection | When selecting the write button in side navigation/category | • Category • Format | (Custom event) |
Post (Content) | Post registration | When selecting registration after completing post writing | • Length (writing volume) • Number of attachments • Time required for writing • Writing date | (Custom event) |
Post (Content) | Post deletion | When selecting the delete button of a registered post | • Post information (title, image/video, nickname, registration date, view count, comments) | (Custom event) |
Post (Content) | Post temporary registration | When selecting temporary registration while writing a post | - | (Custom event) |
Post (Content) | Sort/filter application | When selecting a method other than default sort/filter in the post list | • Selected sorting method • Selected filter | (Custom event) |
Post (Content) | Community activity | • When selecting the register button after completing comment/reply writing • When selecting the comment/reply delete button • When selecting report, like, dislike | • Post information | (Custom event) |
Post (Content) | Post sharing | When selecting sharing method in the sharing popup after selecting the post share button | • Post information • Selected sharing method | Share (Standard) |
Post (Content) | Search result view | When selecting a post from the search result list | • Post information • Page number | Search result view (Standard) |
Post (Content) | Hashtag usage | • When selecting registration after entering hashtags while writing a post • When starting search after entering hashtags (#) | • Post information • Number of entered hashtags • Number of posts related to the hashtag | (Custom event) |
User | Profile settings | • When profile modification is completed • When viewing other users' profiles | • Profile image • Nickname | (Custom event) |
User | Withdrawal | When selecting the withdrawal button in the community withdrawal notice popup | - | (Custom event) |
Others | Web shop entry | When selecting the web shop button in header/side navigation | - | (Custom event) |
Others | Purchase history check | When selecting the purchase history button in header/side navigation | - | (Custom event) |
Others | Play on PC entry (web) | When selecting the play on PC button in side navigation | - | (Custom event) |
Others | Coupon exchange entry | When selecting the coupon exchange button in side navigation | - | (Custom event) |
Others | Brand site entry | When selecting the brand site button in side navigation | - | (Custom event) |
Others | Market navigation | When selecting the market navigation button in footer/side navigation | - | (Custom event) |
Web shop automatic collection events
The events that Airbridge can automatically collect from web shop sites are as follows:
Event | Trigger point | Components |
---|---|---|
Login | When entering the page after login completion | - |
Sign up | Based on the time of community ID creation | - |
Home screen view | When entering the home screen page | - |
Product list view | When product list is displayed | • Category name • Page number |
Category selection | When selecting category button | Category name |
Product detail view | When entering the product detail information page after clicking product information | • Product market • Product name • Currency • Product price |
Purchase button click | When clicking the purchase button in product detail information | • Product market • Product name • Currency • Product price |
Payment start | When clicking the purchase button in the server information selection popup | • Product market • Product name • Currency • Product price • Product quantity |
Purchase completion | When receiving payment completion information from billing after web PG payment completion | • Currency • Order number • Product market • Product name • Product price • Purchase quantity |
Enabling third-party attribution¶
You can enable or disable third-party attribution using the Hive API. To enable or disable third-party attribution, call the setEnableTracker() function of the Analytics API. For the first parameter of the function, define the attribution you want to enable or disable with the following strings:
- Adjust:
ADJUST
- Singular:
SINGULAR
- AppsFlyer:
APPSFLYER
- Firebase:
FIREBASE
- Airbridge:
AIRBRIDGE
Note
If you have defined the third-party attribution you want to use in hive_config.xml, the third-party attribution is enabled by default. Therefore, you do not need to directly enable third-party attribution after Hive initialization.
The following is example code to disable specific attribution:
API Reference: hive.Analytics.setEnableTracker
API Reference: Analytics::setEnableTracker
API Reference: Analytics.setEnableTracker
API Reference: AnalyticsInterface.setEnableTracker
API Reference: setEnableTracker(name:enable:)
API Reference: HIVEAnalytics:setEnableTracker
Applying marketing attribution to Windows¶
The steps to apply marketing attribution in a Windows environment are as follows:
- Go to Releases > Plugins > Marketing Attribution > Windows.
- Download the marketing attribution plugin you want to use.
- Extract the downloaded file.
- Add the DLL files from the extracted files to {game app executable path}/plugins/trackers.