We constantly publish updates to our documentation, which may not yet be available in your language. For the most current information, use the English version.

for Marketers

Set up Discord

Discord is an ad network integrated with Adjust. Our integration lets Discord receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with Discord for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Discord.

Before you begin

Requirements

Admin, Editor, or Custom Editor permissions in Adjust.
Adjust SDK v4.0.0 and later to map SDK parameters to Discord parameters. Follow the guides linked below to use this feature.

Select Discord and your app in Campaign Lab

Under Campaign Lab, select Partners.
Select New partner > Discord. Select Next to move to the next screen.
In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Discord.
Select Next.

Enable data sharing

Enable data sharing to activate the integration with Discord. To enable data sharing:

Turn on Enabled

Once you enable data sharing with Discord, Adjust automatically sends Discord the following data, by default:

install
session
reattribution
event
rejectedInstall
rejectedReattribution

Set your data sharing options

If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:

Separate data sharing options at the platform-level by selecting Use platform-specific settings.
Set the same data sharing settings for multiple platforms by selecting Use global settings.

Now, under What will be shared by default?, review the activities that Adjust shares with Discord by default.

install
session
reattribution
event
rejectedInstall
rejectedReattribution

Send additional data

Choose the amount and type of data that you want to share with Discord through callbacks. Discord may use this information to optimize performance.

Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Discord:

Data from all attribution sources
Only data attributed to Discord

Sessions

Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Discord will receive your app’s session activity.

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Discord receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.

Map events

Map events that you want to share to the values that Discord can receive. Data for unmapped events is not shared with Discord.

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with Discord. This lets you:

Set individual events to manage campaign strategies for each platform.
Customize data sharing per platform.

Under Map events, follow these steps to choose the in-app events you want to directly send to Discord.

Select Map event.
In the Adjust event list, choose the Adjust event that you want to share with Discord.
Under Partner event, you need to select the Discord event that corresponds to the Adjust event.
1. For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
  - Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
  - Select Use global mapping to map the same events for all platforms.
2. In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
Select Apply.

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

Map all events

If Discord supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now Discord will receive in-app event data for all your linked events.

Configure your link and settings

You have the option to set your:

Create your link and share it with Discord

In the Setup review screen, you can review your choices. You can also go back and make changes to:

Your selected app
Data sharing options
Link structure parameters
User destinations
Attribution settings

Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Discord.

Once you’ve created your link, share it with Discord for placement in campaigns.

List of all parameters forwarded to Discord

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

Placeholder	Information
`{click_attribution_window}`	Attribution window settings for device matching (hours)
`{country}`	Device two-character country code
`{impression_attribution_window}`	Attribution window settings for impression matching (hours)
`{ip_address}`	Device IP address
`{is_reattributed}`	1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed
`{match_type}`	Attribution method
`{os_name}`	Device operating system
`{os_version}`	Operating system version number
`{reattribution_attribution_window}`	Attribution window settings for reattribution (hours)
`{reporting_currency}`	Dashboard reporting ISO 4217 currency code
`{revenue_float}`	Revenue, as sent from Adjust SDK, in whole currency units
`{revenue_usd}`	Revenue, in US dollars
`{tracking_enabled}`	1 if tracking is enabled, 0 if not
`{tracking_limited}`	1 if tracking is limited, 0 if not
`{user_agent}`	Incoming raw user agent
`{activity_kind}`	Type of user activity
`{app_id}`	Store App ID or Google Play Store
`{app_name}`	Name of the app
`{app_version}`	App version number (Android), build-version-number for the bundle (iOS)
`{conversion_duration}`	Time between click and install or reattribution in seconds
`{created_at}`	Activity timestamp
`{impression_based}`	1 if impression-based engagement, 0 if not
`{installed_at}`	Install (i.e., first app open) timestamp
`{is_organic}`	1 if organic traffic, 0 if non-organic
`{rejection_reason}`	Reason for a rejected attribution
`{is_s2s}`	1 if server to server engagement, 0 if not