Integrated monetization partners
Here are the integrations we have for our monetization partners:
| Provider | Revenue estimates | Server-to-server push | Aggregated import | User-level import |
|---|---|---|---|---|
| AdGem |  |  | | |
| AppLovin | | | | |
| BitLabs | | | | |
| Chartboost | | | | |
| Cint | | | | |
| CPX Research | | | | |
| Dalia | | | | |
| Fyber | | | | |
| inBrain | | | | |
| ironSource | | | | |
| Torox | | | | |
| Pollfish | | | | |
| Revenue Universe | | | | |
| TapJoy | | | | |
| TapResearch | | | | |
| Unity | | | | |
AdGem
Our integration with AdGem supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Ad Type Parameter | s2s | | The parameter in justtracks revenue URL to receive the adType from AdGem | Documentation |
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by AdGem | - |
| Placement Parameter | s2s | | The parameter in justtracks revenue URL to receive the placement from AdGem | Documentation |
| Revenue Parameter | s2s | | The parameter in justtracks revenue URL to receive the revenue value from AdGem | Documentation |
| Transaction ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the transation id from AdGem | Documentation |
| User ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the user id from AdGem. Both justtrack issued and custom user ids are supported. | Documentation |
AppLovin
Our integration with AppLovin supports:
Here's what you'll need to configure this partner for your preferred method in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Management API Key | import | | The API key to access Applovin's management APIs, used to retrieve your ad units | Documentation |
| Reporting API Key | import | | The API key to access Applovin's reporting APIs, used to retrieve the revenue | Documentation |
| Ad Type Parameter | s2s | | The parameter in justtracks revenue URL to receive the ad type from AppLovin | Documentation |
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by AppLovin | - |
| Network Parameter | s2s | | The parameter in justtracks revenue URL to receive the monetization network from AppLovin | Documentation |
| Placement Parameter | s2s | | The parameter in justtracks revenue URL to receive the placement from AppLovin | Documentation |
| Revenue Parameter | s2s | | The parameter in justtracks revenue URL to receive the revenue value from AppLovin | Documentation |
| Transaction ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the transaction id from AppLovin | Documentation |
| User ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the user id from AppLovin. Both justtrack issued and custom user ids are supported. | Documentation |
For AppLovin, you can choose between either the aggregated import or the user level import. Both require the appropriate configuration in the SDK.
BitLabs
Our integration with AdGem supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by BitLabs | - |
| Revenue Parameter | s2s | | The parameter in justtracks revenue URL to receive the revenue value from BitLabs | Documentation |
| Transaction ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the transaction id from BitLabs | Documentation |
| User ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the user id from BitLabs. Both justtrack issued and custom user ids are supported. | Documentation |
ChartBoost
Our integration with ChartBoost supports the aggregated import method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| ID | import | | Chartboost unique id for you as a supply partner | Documentation |
| Signature | import | | Chartboost's signature granting justtrack access to their monetization data | Documentation |
Cint
Our integration with Cint supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by Cint | - |
| Revenue Parameter | s2s | | The parameter in justtracks revenue URL to receive the revenue value from Cint | Ask your account manager for this value |
| Transaction ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the transaction id from Cint | Ask your account manager for this value |
| User ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the user id from Cint. Both justtrack issued and custom user ids are supported | Ask your account manager for this value |
CPX Research
Our integration with CPX Research supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by CPX Research | - |
| Revenue Parameter | s2s | | The parameter in justtracks revenue URL to receive the revenue value from CPX Research | Ask your account manager for this value |
| Transaction ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the transaction id from CPX Research | Ask your account manager for this value |
| User ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the user id from CPX Research. Both justtrack issued and custom user ids are supported. | Ask your account manager for this value |
Dalia
Our integration with Dalia supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by Dalia | - |
| Revenue Parameter | s2s | | The parameter in justtracks revenue URL to receive the revenue value from Dalia Research | Ask your account manager for this value |
| Transaction ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the transaction id from Dalia Research | Ask your account manager for this value |
| User ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the user id from Dalia Research. Both justtrack issued and custom user ids are supported. | Ask your account manager for this value |
Fyber
Our integration with Fyber supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Security Token | s2s | | The security token used to verify the incoming revenue data from Fyber (Product of Digital Turbine) | Ask your account manager for this value |
inBrain
Our integration with inBrain supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by InBrain | - |
ironSource
Our integration with ironSource supports:
Here's what you'll need to configure this partner for your preferred method in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Refresh Token | import | | Ironsource's refresh token granting justtrack access to their monetization data | Documentation |
| Secret Key | import | | Ironsource's secret key granting justtrack access to their monetization data | Documentation |
Torox
Our integration with Torox supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by Offer Toro | - |
Pollfish
Our integration with Pollfish supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Device ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the device id from Pollfish | Documentation |
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by Pollfish | - |
| Revenue Parameter | s2s | | The parameter in justtracks revenue URL to receive the revenue value from Pollfish | Documentation |
| Transaction ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the transaction id from Pollfish | Documentation |
Revenue Universe
Our integration with Revenue Universe supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Forward URL | s2s | | The URL you want justtrack to forward raw revenue data received by RevU | - |
| Revenue Parameter | s2s | | The parameter in justtracks revenue URL to receive the revenue value from RevU | Documentation |
| Transaction ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the transaction id from RevU | Documentation |
| User ID Parameter | s2s | | The parameter in justtracks revenue URL to receive the user id from RevU. Both justtrack issued and custom user ids are supported. | Documentation |
TapJoy
Our integration with TapJoy supports the user-level import method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| Marketing API Key | import | | The tapjoy marketing api key, allowing justtrack access to their monetization data | - |
| Publisher App ID | import | | Tapjoy's id for your app in their system | - |
To find these values:
- Navigate to Monetization
- Pick your app
- Navigate to APP SETTINGS > App Info
TapResearch
Our integration with TapResearch supports the server-to-server push method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| API Secret | s2s | | The parameter in justtracks revenue URL to receive the revenue value from RevU | Documentation |
| Forward URL | s2s | | The URL you want justtrack to forward the raw revenue data received by RevU | - |
Unity
Our integration with Unity supports the aggregated import method for receiving revenue.
Here's what you'll need to configure this partner in justtrack:
| Field | Feature | Required | Description | Help |
|---|---|---|---|---|
| API Key | import | | Unity's API key allowing justtrack access to their monetization data | Documentation |
| Game ID | import | | Unity's id for your app in their system | Documentation |
| Organization Core ID | import | | Unity's id for your business in their system | Documentation |