Languages 

Set up Samsung DSP

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

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

Basic setup

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

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select the add (+) icon next to Samsung DSP
  4. Turn on Enabled
  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 Samsung DSP to launch your campaign.

Samsung DSP will receive callbacks for these activities:

  • install
  • session
  • uninstall
  • reinstall
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution

Advanced setup

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

Forward in-app revenue

In-app revenue forwarding lets Samsung DSP receive revenue amounts along with your revenue event data.

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

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

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

Note: Link at least one [revenue event] to Samsung DSP before turning on In-App Revenue Forwarding.

Forward uninstalls / reinstalls

To forward uninstalls and/or reinstalls to Samsung DSP, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Samsung DSP
  3. Turn on Uninstall / Reinstall Forwarding

Now Samsung DSP will receive all of your app’s uninstall and/or reinstall data.

Forward sessions

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

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

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

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

Forward in-app events

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

To forward in-app events to Samsung DSP, follow these steps.

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

Now Samsung DSP will receive in-app event data for each of your linked events.

List of all parameters forwarded to Samsung DSP

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

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{android_id}Android ID (Android only)
{country}Device two-character country code
{currency}Original ISO 4217 currency code sent from Adjust SDK
{device_name}Device model number
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{ip_address}Device IP address
{match_type}Attribution method
{mcc}Mobile country code: three-digit code identifying a device's country. Use with the mobile network code to identify a device's carrier.
{mnc}Mobile network code: two-digit code. Use with the mobile country code to identify a device's carrier.
{os_name}Device operating system
{os_version}Operating system version number
{revenue_float}Revenue, as sent from Adjust SDK, in whole currency units
{session_count}Number of sessions recorded by current Adjust SDK
{time_spent}Length of user's current session, in seconds
{timezone}Device time zone
{tracking_enabled}1 if tracking is enabled, 0 if not
{activity_kind}Type of user activity
{app_id}Store App ID or Google Play Store
{app_version_short}App version number (Android), release-version-number for the bundle (iOS)
{click_time}Attributed click timestamp
{created_at}Activity timestamp
{impression_based}1 if impression-based engagement, 0 if not
{impression_time}Attributed impression timestamp
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{reattributed_at}Reattribution timestamp
{rejection_reason}Reason for a rejected attribution