Ad revenue callbacks

With our Ad Revenue solution, you can view aggregated ad revenue data in Datascape and send unaggregated device-level data with your callbacks.

Growth solution:
Ad Revenue reporting is available as an Adjust Growth Solution. To get Ad Revenue reporting on your account, contact sales@adjust.com.

Recommended placeholders

PlaceholderDescriptionExample
{revenue}Revenue as sent from the Adjust SDK or via S2S (in cents)345
{currency}Original ISO 4217 currency code sent from the Adjust SDKusd
{revenue_float}Revenue as sent from the Adjust SDK or via S2S (in whole currency units)3.99
{ad_impressions_count}Number of mobile ads served to end users4
{ad_mediation_platform}Mediation platform nameironSource
{ad_revenue_placement}User placement, as defined on the platformhome_screen
{ad_revenue_network}Ad network that displayed the adAdmob
{ad_revenue_unit}Ad unit that generated the revenuerewarded_video
{ad_revenue_payload}Impression-level revenue data (ILRD) as a JSON%7B%22currency%22%3A%22USD%22%2C%22id%22%3A%221be0c337ae3548b3af67339ca5d5d0fe_005edb230021181d%22%2C%22network_placement_id%22%3A%22%22%2C%22adgroup_id%22%3A%22ed1c58b7d95040d3959b35f6e727d409%22%2C%22adgroup_priority%22%3A13%2C%22adunit_format%22%3A%22Banner%22%2C%22adunit_name%22%3A%22RR_iOS_Banner%22%2C%22adgroup_type%22%3A%22network%22%2C%22network_name%22%3A%22custom_native%22%2C%22precision%22%3A%22publisher_defined%22%2C%22publisher_revenue%22%3A0.00020000000000000001%2C%22country%22%3A%22US%22%2C%22adgroup_name%22%3A%22Fyber_RR_iOS_Banner_0.2%22%2C%22adunit_id%22%3A%2263e2003f128a4c8693c963d8c788c5a3%22%7D
Note:
If placeholder data is not available, it will be dropped from the callback.

Callback example

Callback URL with placeholdersUnencoded (Do not use as is)
Callback URL populated with values
https://serverendpoint.com/mobile_attribution?gps_adid={gps_adid}&idfa={idfa}&idfv={idfv}&adid={adid}&tracker_token={tracker_token}&tracker_name={tracker_name}&app_name={app_name}&activity_kind={activity_kind}&created_at={created_at}&event_token={event}&event_name={event_name}&revenue={revenue}&currency={currency}&revenue_float={revenue_float}&ad_impressions_count={ad_impressions_count}&ad_mediation_platform={ad_mediation_platform}&ad_revenue_placement=(ad_revenue_placement}&ad_revenue_network={ad_revenue_network}&ad_revenue_unit={ad_revenue_unit}&ad_revenue_payload={ad_revenue_payload}

Other recommended placeholders

We also advise that you include the following placeholders in all callback URLs. These placeholders will ensure that you always receive basic information that you can use to identify the app, link, data point, and device to which the rest of your callback data belongs.

PlaceholderDescriptionExample
{gps_adid}Google Play Store advertising ID (Android only)38400000-8cf0-11bd-b23e-10b96e40000d
{idfa}ID for advertisers (iOS only)8C6CBCOD-5F43-4765-A6E6-84DFF3D24707
{idfv}ID for vendors (iOS only)CCB300A0-DE1B-4D48-BC7E-599E453B8DD4
{adid}Adjust device ID18546f6171f67e29d1cb983322ad1329
{tracker}Adjust link tokenabc123
{tracker_name}Current link name as defined in Campaign LabNetwork1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en
{app_name}Name of the appMyApp
{activity_kind}This will allow you to determine the data point: impression, click, install, rejected install, rejected reattribution, session, reattribution, uninstall, reinstall, reattribution reinstall, updated attribution, in-app event, or ad spend (cost_updated)rejected_reattribution
{created_at}The timestamp for when the data point occurred1404214665