Set up Aarki

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

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

Basic setup

To turn on Adjust’s integration with Aarki, 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 Aarki
  4. Enter your NETWORK ID (contact your Aarki 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 Aarki to launch your campaign.

Aarki will receive callbacks for these activities:

  • ad revenue
  • event
  • install
  • reattribution
  • rejected install
  • session

Advanced setup

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

Only forward data attributed to Aarki

Adjust sends Aarki your installs and reattributions across all ad platforms.

To stop Aarki 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 > Aarki
  3. Turn on Attributed Only

Now Aarki will only receive data attributed to their own platform.

 

Forward in-app revenue

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

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

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

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

 

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

 

Forward ad revenue

Ad revenue forwarding lets Aarki receive user ad revenue data. This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.

To forward ad revenue to Aarki, follow these steps.

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

Now Aarki can use ad revenue data to optimize your user targeting and campaigns.

 

Forward sessions

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

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

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

Now Aarki will receive your app’s session activity.

 

Forward app events

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

To forward app events to Aarki, follow these steps.

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

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

List of all parameters forwarded to Aarki

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

Placeholder Information
{android_id} Android ID (Android only)
{app_id} Store App ID or Google Play Store
{app_name} Name of the app
{city} Device city
{click_time} Attributed click timestamp
{connection_type} Internet connection type
{conversion_duration} Time between click and install or reattribution in seconds
{country_subdivision} Device subdivision of country, e.g., state
{country} Device two
{created_at} Activity timestamp
{device_name} Device model number
{device_type} Device type
{idfa||gps_adid} IDFA, or GPS ADID if IDFA is empty
{impression_based} 1 if impression
{installed_at} Install (i.e., first app open) timestamp
{ip_address} Device IP address
{isp} Device internet service provider
{language} Device two
{match_type} Attribution method
{os_name} Device operating system
{os_version} Operating system version number
{postal_code} Device postal code of IP address
{random} Random number (unique per callback)
{reattributed_at} Reattribution timestamp
{rejection_reason} Reason for a rejected attribution
{revenue} Revenue, as sent from Adjust SDK in cents
{timezone} Device time zone
{user_agent} Incoming raw user agent