Set up Appreciate DSP

Appreciate DSP is a network and Adjust module partner. Our integration lets Appreciate DSP receive attribution and app event data through automated callbacks.

Use our basic setup instructions to turn on Adjust’s integration and send callbacks to Appreciate DSP. Then, use our advanced setup instructions to customize what information Appreciate DSP receives.

Basic setup

To turn on Adjust’s integration with Appreciate DSP, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select Add (+icon) next to Appreciate DSP
  4. Enter your APPRECIATE YID (contact your Appreciate DSP representative for help finding this)
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. Now you can create an Adjust tracker URL and submit it to Appreciate DSP to launch your campaign.

Appreciate DSP will receive callbacks for these activities:

  • install
  • rejected install
  • session
  • event

Advanced setup

Choose which data Appreciate DSP receives from Adjust by customizing your setup.

Only forward data attributed to Appreciate DSP

Adjust sends Appreciate DSP your installs and reattributions across all ad platforms.

To stop Appreciate DSP from receiving data attributed to other ad platforms, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Appreciate DSP
  3. Turn on Attributed Only

Now Appreciate DSP will only receive data attributed to their own platform.

 

Forward in-app revenue

Revenue forwarding lets Appreciate DSP receive revenue amounts along with your revenue event data.

To forward in-app revenue to Appreciate DSP, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Appreciate DSP
  3. Turn on In-App Revenue Forwarding

Now Appreciate DSP will receive the revenue amount for every tracked transaction.

 

Note: Link at least one revenue event to Appreciate DSP before turning on Revenue Forwarding

 

Forward sessions

Adjust does not automatically send session callbacks due to the high volume of sessions.

To forward in-app sessions to Appreciate DSP, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Appreciate DSP
  3. Turn on Session Forwarding

Now Appreciate DSP will receive your app’s session activity.

 

Forward custom data

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Appreciate DSP.

Note: Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.

To forward partner parameters to Appreciate DSP, follow these steps.

  1. Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
  2. In the Adjust dashboard, find your app and select your app options caret (^)
  3. Select Partner Setup > Appreciate DSP
  4. Turn on Parameter Forwarding
  5. Select Partner Parameter Mapping
  6. In the FROM APP field, enter the name of your Adjust parameter (as written into the Adjust SDK). In the TO PARTNER field, enter your corresponding Appreciate DSP name.
  7. Select Save

Now Appreciate DSP will receive custom event details for each of your linked events.

 

Note: If you set up partner parameters within the Adjust SDK without turning on Partner Parameter Mapping, Adjust forwards the parameters as named in the Adjust SDK.

 

Forward app events

Event linking lets Appreciate DSP receive app event data. You can link every app event in Adjust to a preset Appreciate DSP name or a custom event name.

To forward app events to Appreciate DSP, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup >Appreciate DSP > Event Linking
  3. Find the event you want to link and update the field with a Appreciate DSP event or your own custom name
  4. When you finish linking events, select OK
  5. Select Save

Now Appreciate DSP will receive app event data for each of your linked events.

Partner specific setup instructions

Appreciate DSP receives detailed campaign level information for campaigns data that is attributed to Appreciate DSP only.

List of all parameters forwarded to Appreciate DSP

Appreciate DSP requires Adjust to send the following parameters (data points) with your callbacks:

Placeholder Information
{activity_kind} Type of user activity
{adgroup_name} Adgroup name, as taken from the tracker
{api_level} API level (Android only)
{app_id} Store App ID or Google Play Store
{campaign_name} Campaign name, as taken from the tracker
{city} Device city
{click_attribution_window} Attribution window settings for device matching (hours)
{click_time} Attributed click timestamp
{connection_type} Internet connection type
{conversion_duration} Time between click and install or reattribution in seconds
{cost_amount} Cost of the user engagement (available for ad spend tracking only)
{cost_currency} ISO 4217 currency code of the cost data (available for ad spend tracking only)
{cost_id_md5} An MD5 hash of the cost ID provided by a network using our ad spend API (available for ad spend tracking only)
{cost_type} The campaign pricing model (available for ad spend tracking only)
{country_subdivision} Device subdivision of country, e.g., state
{country} Device two
{creative_name} Creative name, as taken from the tracker
{currency} Original ISO 4217 currency code sent from Adjust SDK
{deeplink} Deeplink URL appended to click URL
{device_name} Device model number
{device_type} Device type
{engagement_time} Engagement timestamp
{idfa||gps_adid} IDFA, or GPS ADID if IDFA is empty
{impression_attribution_window} Attribution window settings for impression matching (hours)
{impression_based} 1 if impression
{impression_time} Attributed impression timestamp
{installed_at} Install (i.e., first app open) timestamp
{ip_address} Device IP address
{is_organic} 1 if organic traffic, 0 if non
{is_reattributed} 1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed
{isp} Device internet service provider
{language} Device two
{last_session_time} Last session timestamp
{last_time_spent} Length of user's last session, in seconds
{last_tracker} 6
{lifetime_session_count} Number of sessions recorded across entire user lifetime
{match_type} Attribution method
{mcc} Mobile country code: three
{mnc} Mobile network code: two
{network_name} Network name, as taken from the tracker
{os_name} Device operating system
{os_version} Operating system version number
{partner_parameters} Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks
{postal_code} Device postal code of IP address
{reattributed_at} Reattribution timestamp
{reattribution_attribution_window} Attribution window settings for reattribution (hours)
{reftag} Random device reference tag
{region} Device region code
{rejection_reason} Reason for a rejected attribution
{revenue_float} Revenue, as sent from Adjust SDK, in whole currency units
{revenue_usd_cents} Revenue, in US cents
{sdk_version} Adjust SDK version (per app)
{session_count} Number of sessions recorded by current Adjust SDK
{time_spent} Length of user's current session, in seconds
{timezone} Device time zone
{tracker} 6
{tracking_limited} 1 if tracking is limited, 0 if not
{user_agent} Incoming raw user agent
{win_adid} Windows advertising identifier