Languages 

Set up Atma

Atma is an analytics and Adjust module partner. Our integration lets Atma 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 Atma. Then, use our advanced setup instructions to customize what information Atma receives.

Basic setup

To turn on Adjust’s integration with Atma, 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 Atma
  4. Turn on Enabled
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. Atma will receive callbacks for these activities:

  • install
  • session
  • uninstall
  • reinstall
  • reattribution
  • event

Advanced setup

Choose which data Atma receives from Adjust by customizing your setup.

Forward in-app revenue

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

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

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

Now Atma will receive the revenue amount for every tracked transaction.

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

Forward uninstalls / reinstalls

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

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

Now Atma 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 Atma, follow these steps.

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

Now Atma 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 Atma.

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 Atma, 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 > Atma
  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 Atma name.
  7. Select Save

Now Atma 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 in-app events

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

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

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

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

List of all parameters forwarded to Atma

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

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{city}Device city
{country_subdivision}Device subdivision of country, e.g., state
{country}Device two-character country code
{currency}Original ISO 4217 currency code sent from Adjust SDK
{deeplink}Deeplink URL appended to click URL
{device_type}Device type
{event_name}Event name, as set in the Dashboard
{idfa||gps_adid}IDFA, or GPS ADID if IDFA is empty
{idfv}Uppercase iOS ID for vendors
{ip_address}Device IP address
{isp}Device internet service provider
{mcc}Mobile country code: three-digit code identifying a device's country. Use with the mobile network code to identify a device's carrier.
{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
{user_agent}Incoming raw user agent
{app_id}Store App ID or Google Play Store
{app_name}Name of the app
{created_at}Activity timestamp
{device_manufacturer}Device manufacturer name
{is_organic}1 if organic traffic, 0 if non-organic
{network_type}Network type