Chartboost is a gaming-centric performance network. Adjust integrates Chartboost in two ways:
- Session, install, reattribution and rejected install callbacks: Adjust will report all user sessions as well as installs, rejected installs and reattributions attributed to Chartboost. These callbacks are used for S2S Tracking in the Chartboost network.
- Event (or post-install) callbacks: Adjust will report in-app purchases or custom level events to Chartboost so that developers can visualize that data and optimize their Chartboost campaigns based on it. Adjust is integrated so as to provide Chartboost with additional data on level and purchase events, as well as optional install and session callbacks.
To activate the Chartboost module, you’ll need to add your game’s Chartboost app ID and app signature, which you can find here. To start sending session callbacks, turn the Session Forwarding toggle to ON. Please note that Session Forwarding should be turned ON for optimal campaign performance on the Chartboost network. To enable event callbacks, enter Event Label per each event you would like Chartboost to receive. Toggle the module switches to enable Revenue and Parameter Forwarding.
If you would like to send attributed-only traffic to Chartboost, toggle the relevant switch – note that this toggle applies to all activities sent to Chartboost.
- Raw device IDs
- Partial tracker names
- App metadata
- Revenues (Optional)
- Partner Parameters (Optional)
- See below
- Non-zero integer denoting the main level: main_level
- Non-zero integer denoting sublevel: sub_level
- String description of a level: description
- Localized description of a level: localized_description
1Chartboost Event & Level Linking
You can link your purchase events and send them to Chartboost by first adding an event label, then activating revenue sharing in the Settings panel of your dashboard.
Chartboost also offers extended facilities for reporting specific in-app events from Adjust. In particular, you can specifically mark events as level events (wherein the player in your game reaches another level) by using partner parameters.
To do this, you must first activate Event Linking. Simply add an event name in the Chartboost Settings panel in your dashboard. The chart below explains the fields within the Chartboost module:
|Event Label||Any string (excluding
||Mandatory||This is the event name. (If this is a purchase event, enter “purchase” and leave all other fields blank.)|
|Event Field||1 - 5 (single digit)||Mandatory||The data you are transmitting. See below for more about the Event Field value.|
|Main Level||Integer (1+)||Optional||Can be sent as a partner parameter from the SDK. Dashboard module values override values set within the SDK.|
|Sub Level||Integer (0+)||Optional||Can be sent as a partner parameter from the SDK. Dashboard module values override values set within the SDK.|
The Event Field is what specifies the type of level data you are transmitting. When setting up your Event Linking, the Event Field should be set to one of the five values below:
|event_field value||Event Field||Sequential?||Description||Example Event Label|
|1||HIGHEST_LEVEL_REACHED||Y||Hightest numerical level a user has reached.||“Highest level puzzle solved”|
|2||CURRENT_AREA||N||The current level/area that a user is at.||“Area main character is in”|
|3||CHARACTER_LEVEL||Y||The level of the player’s character in game.||“Level of the character class”|
|4||OTHER_SEQUENTIAL||Y||Extra field for developers to send sequential data.||“VIP Reward Level”|
|5||OTHER_NONSEQUENTIAL||N||Extra field for developers to send non-sequential data.||“FTUE Completed?”|
As mentioned above, there are four partner parameters you can set within your SDK.
||Non-zero integer||Denotes main level. (For non-revenue events)|
||Non-zero integer||Denotes sublevel. (For non-revenue events)|
||String||Description of a level. (For non-revenue events)|
||String||Description of a level. (For revenue events)|
If you specify a value for Main Level or Sub Level within the Chartboost dashboard module, the module values will override the
sub_level SDK values, respectively. If you set neither the dashboard nor the SDK values, the predefined fallback values will be used instead.
Syncing Chartboost clicks
The click callback setup in Chartboost’s UI does not use macros; instead, you set up a list of parameters in your Chartboost dashboard. The screenshot below is for iOS. You can see the click callback setup in the Chartboost documentation.
Due to recent iOS 10 limitations, we are NOT sending non-Chartboost attributed data for all LAT enabled users (users with all 0 IDFAs) to Chartboost. This is because Chartboost is not able to process the data if there is no IDFA or Chartboost click ID. This could cause minor discrepancies between Adjust and Chartboost data for your iOS campaigns.