Post-Install Analytics — Third Parties

Last Update:

For a more complete analysis of in-app purchase (IAP) data across platforms or networks, you can also set up a S2S integration to import IAP information from third-party tracking services. After the integration, you'll be able to view the third-party data in the Chartboost dashboard.

Using both Chartboost SDK and a 3rd Party integration?

The default behavior is to continue listening to the SDK for PIA events and ignore S2S PIA events. You can reach out to Support or your Account Manager and ask them to switch you over from SDK to 3rd Party integration, at which point we begin listening to S2S events and ignoring the Chartboost SDK events. This prevents duplication of events and maintains a single channel for incoming data. Apps can be switched back at any time by Support.


Adjust Instructions

1. Open the app whose IAP data you'd like to send to Chartboost

2. Click Settings, then Partner Setup

3. Under Networks, pick Chartboost

4. Set the Revenue Forwarding toggle to ON and Attributed Only to OFF.  Parameter Forwarding should also be left off unless you are mapping the Event Label value from the Adjust SDK.

5. Type "purchase" in the EVENT LABEL field for any in-app purchase events you're tracking with Adjust, under the Chartboost Event Linking section.  Leave EVENT FIELD, MAIN LEVEL, and SUB LEVEL fields blank.

Adjust FAQ

Are all the fields shown in the Adjust dashboard's "Event Linking" section sent to Chartboost automatically in the IAP Postback?

No, only Event Label is sent as the "product_id" to Chartboost. 

What are the text fields to the right of each event name for?

Add the event value to these fields; when these events are sent to Chartboost, they are recorded with the event value in the text field.

Is there a limit of events that can be listed in the Events Linking section?

No. The window is scrollable, so you can add all purchase events you're already tracking with Adjust.

AppsFlyer Instructions

1. Log in to your AppsFlyer app dashboard and click Media Source Configuration on the left side

2. Search for and click Chartboost S2S, then switch to the In App Events tab

3. Complete the Send In-App Events to Chartboost section as shown below and add your own Chartboost app ID to the chartboost_app_id field.

4. You'll also need to contact Support to receive the token you'll add to the Chartboost Event Tag field:

Note: AppsFlyer currently only supports sending purchase events to Chartboost.  Level/Event Tracking will be supported in the future.

Apsalar Instructions

To receive IAP data from Apsalar, you should create a new postback (Setup > Attribution Tracking > Create New Postback) with the following settings:

  • Postback Recipient: Chartboost
  • Application: Select Application
  • Event Type: Custom event (then select the specific revenue event from the drop-down)
  • Postback Status: Active, begin sending immediately
  • Attribution Rules: Send all events from all sources

You'll also need to add your Chartboost app ID, token (contact Support if you don't already have it), and key that identifies IAP product names to the three fields in the Preview section:

Kochava Instructions

You'll find event postback instructions in Kochava's Support Center.

TUNE Instructions

  • Open the Chartboost configuration panel from the Integrated Partners tab.
  • Select Postbacks and click Add Postback URL.



  • Search for Chartboost in the Advertising Partner Postback Template section.
  • In the Chartboost Postback Template section, choose iOS or Android from the Platform dropdown.
  • Choose Chartboost IAP Postback | purchase | All from the Postback Template dropdown.
  • Add your Chartboost app ID and app signature, then save.



Other Third Parties

If you're a developer and want to take advantage of this functionality – but don't see your third-party tracking service above – please send the information below to the service:

Third-party S2S PIA calls contain IAP information and an API token (contact us for your token) to verify the request:


    "app_id": "54ecc0535beacdc1e1eff778"
    "ifa": "8c2d20ef2f4248209f65b35e3c398731"
    "iap": {
        "product_id": "com.sample.gems.001"
"currency": "EUR", "price": 3.99, "localized_description": "TheFirstGemsPack", "localized_title": "GemsPack" } }

Below is information about the S2S call itself; to receive your API token, contact us.

PIA S2S Request Details







(Note that headers contain authentication information.)

Header Name Example Description
X-Chartboost-Token 2782f24948b6dff2551ff321f70266c415e0d251 Your API Token
X-Chartboost-Signature 173e6aeff28e4b76b488d5acf49ed8ebb8e95559 See this gist to generate. This is NOT the same value as your Chartboost app signature!

JSON Body: IAP Object Parameters

Parameters iOS Apps Android Apps Example Description
currency Required Required "USD" 3-letter ISO 4217 currency code
localized_description Optional Optional "A small pack of coins" Description of item in player's language
price Required Required 0.99 Price of item in the currency defined in currency parameter
localized_title Optional Optional "Small Coin Pack" Title of item in player's language
product_id Required Required "" SKU

JSON Body: Request Parameters

Parameters iOS Apps Android Apps Example Description
Required Required "54ecc0535b1acdc1e1eff778" Chartboost app ID (found in the Chartboost dashboard) 
ifa Required N/A "61109b4c0f164fbc82ec5475313ae000" (32 characters; dashes OK; case insensitive) Identifier for Advertising 
gaid N/A Required "38400000-8cf0-11bd-b23e-10b96e40000d" (32 characters, plus 4 dashes) Google Services Advertising ID (Android Only)
uuid N/A Optional (if GAID is not sent, or if Amazon app) "358414046356276" For legacy Android IDs or Amazon games
iap Required Required   JSON of in-app purchase details; see IAP section below

Public Key/Secret Key (Google Play/Amazon Only)

If you're setting up S2S PIA for Google Play or Amazon Appstore games, you'll need also need to add your app's public key or your Amazon Developer Secret key, respectively, to a field on the game's Edit App page:

Building the Request

First, start with the endpoint:

Add the Headers and add the parameters in the JSON body:


    "app_id": "54ecc0535b1acdc1e1eff778"
    "ifa": "61109b4c0f164fbc82ec5475313ae000"
    "iap": {
        "product_id": "com.sample.gems.001"
"currency": "EUR", "price": 3.99, "localized_description": "TheFirstGemsPack", "localized_title": "GemsPack" } }

And then you're done – successful requests will receive: {"status":200,"message":"Success"}.

If your call receives a 500 HTTP error code, your server should reattempt the S2S call, but at a later time: Try again in 2 seconds, then 4 seconds, then 8 seconds, then 16 seconds until successful.