Aarki campaign configuration

At a glance: Aarki, an AppsFlyer ad network integrated partner, is a well-known mobile DSP. Aarki offers both click-based and view-through mobile attribution. In addition, Aarki also offers click-based retargeting which you can record with AppsFlyer.

Aarki-logo.png

Setting up Aarki

Prerequisite: Before setting up the integration, make sure you contact the partner and open an account with them.

To activate or edit the integration:

  1. To activate: In AppsFlyer, from the side menu, select Collaborate Partner Marketplace.
    To edit: In AppsFlyer, from the side menu, select Collaborate Active Integrations.
  2. Search for the partner and select it.
  3. Click Set up integration. You’re directed to the integration setup page.
  4. In the Integration tab, select the app for the integration and turn Activate partner on.
    Note: The toggle must be on (activated) for as long as you work with the partner.
  5. Complete the configuration using the relevant tabs, as described below.

The Aarki configuration window includes 4 active tabs: Integration, Attribution link, Cost, and Permissions. Click on the items below to read about the tabs setup.

For a detailed description of the Partner Configuration Window Header, click here.

 Tip

  • The General Settings step in the Integration tab is mandatory for all partners
  • All the rest of the steps are either descriptive or optional

Integration tab

Activate partner

On the first visit, you will need to toggle ON the Activate Partner button to enable setup of the integration tab's parameters. The toggle MUST be ON for as long as you work with the partner. For more details about partner activation please click here.

 Note

As an ALL-Installs network, Aarki prefers to receive postbacks for all new installs of your app from ANY source, including organic. It is recommended to select Events attributed to any partner to send all install postbacks to Aarki.

General settings

Partner ID

Aarki connects with AppsFlyer via a unique network ID. If you don't already have the Network ID, you must obtain it from Aarki to continue with the integration.

Enable View-Through attribution

Toggle this to ON if you want to attribute view-through installs from Aarki. The view-through lookback slider is available on the attribution link tab (described below).

Default postbacks

Send automatic postbacks to Aarki following user installs and re-engagements. Use this section to define the source of the users that allow sending these postbacks.

Select Only events attributed to this partner for events coming only from users attributed to Aarki. Select Events attributed to any partner or organic to have your entire user base available to be reported to Aarki.

In-app events settings

In this section you can map your AppsFlyer events with Aarki via postbacks.

To configure in-app event postbacks:

  1. Turn on In-app event postbacks.
  2. Click Add event to add an SDK or server-to-server event to the list. The following table describes the fields to complete:
    Parameter name Description
    AppsFlyer event

    The name of the event, as received by AppsFlyer either from the SDK integrated into your app or from server-to-server events.
    Tip: Don't see the event you are looking for?

    • Make sure to activate the event on a device with a non-organic installation, and recheck.
    • Type it in AppsFlyer event, then click Create custom. Read more about custom event mapping.
    mapped to partner event

    The unique name or ID of each event, as defined on the partner's side. Possible mapping configurations are:

    • Text field: Get the corresponding event ID from the partner.
    • Drop-down box: Select the most suitable pre-defined AppsFlyer event.
    • As is: Send the events as they are, without name mapping.
    for users from

    Select the sending option for the event:

    • This partner only: Send postbacks only when this event is attributed to this partner.
    • All media sources including organic: Send postbacks for events attributed to any partner, as well as organic events.
    including
    • No data (default): Send only the event itself without any event values.
    • Values and revenue: Send all the event parameters, including the revenue value (if exists in the event).
    • Values without revenue: Send all the parameters excluding the revenue value.
  3. [Optional] Click the Add conditionconditional-iae-postbacks-icon.pngicon to set conditions for an event.
  4. Click Save integration.
  5. [Optional]After saving the integration, while remaining on the configuration page, you can integrate more of your apps with the partner:
    1. From the top-left corner, under the partner name, click the app name to open the list of apps. 
    2. Select a different app from the drop-down list.
    3. Repeat the integration steps for the selected app.

Attribution link tab

In this tab, you can create the attribution links you want to send to Aarki for attributing Aarki's campaigns, ad sets or even single ads. Note that AppsFlyer DOES NOT save your generated partner's attribution links.

This tab is divided into different sections:

Attribution link parameters

In this section, select which parameters you want to add to the attribution link.

Adding parameters to the attribution link here enables you to later perform thorough drill-down analyses. Parameters that are already defined on the attribution link can be edited by adding them and their new values here.

  • Campaign - add it to compare different campaigns running with Aarki.Attribution link parameter: c
  • Adset - set ad set names to compare different ad sets within specific Aarki campaigns.Attribution link parameter: af_adset
  • Ad Name - set ad set names to compare different creatives within specific ad sets within specific campaigns Aarki.Attribution link parameter: af_ad
  • Site ID and Sub Site ID - set Site ID parameter to attribute installs to specific publishers. If many publishers exist, we advise on limiting the number of used site IDs and using the sub site ID parameter, to avoid exceeding the site ID limitations.Attribution link parameters: af_siteid and af_sub_siteid
  • Subscriber Parameters - use any of the 5 subscriber parameters to insert useful values. Note that these parameters get parsed and appear in the raw data report, which makes them very handy for performing data aggregation or filtering.Attribution link parameters: af_sub1, af_sub2, af_sub3, af_sub4, af_sub5

Add any other parameter to the attribution link simply by typing it in a new parameter box. For more information about AppsFlyer's Attribution Link Structure and Parameters.

Retargeting settings

When enabled, AppsFlyer recognizes a link as a retargeting attribution link, rather than a user acquisition link, by adding the &is_retargeting=true to the click recording link. Note that retargeting is currently only supported for click-through and not view-through attribution.Attribution link parameter: is_retargeting.

The following setup below is displayed when retargeting is enabled.

1. Standard Link vs. OneLink

Select standard attribution link option if:

  • You don't need to deep link with the URL or
  • Plan to use only URI schemes for deep linking

Select Use OneLink for:

  • Using a single link for both Android and iOS apps or
  • Deep linking using Universal or app links

Note that selecting OneLink changes the click recording link from app specific to a OneLink URL.

2. Deep Link URL

Use this field if the link is meant to deep link users to any specific activity within your app.Attribution link parameter: af_dp You can find more information about AppsFlyer's deep linking solution in this guide.

3. Re-engagement Window

Set the time period following the re-engagement, where the user's in-app events are attributed to the retargeting media source. You can set the value in days (1-90), hours (up to 23), or even lifetime.

Attribution link parameter: af_reengagement_window

Click-through attribution

This slider allows you to set the maximum time from click to install. Only installs (first launches) that take place within the lookback window may be attributed to Aarki.

Attribution link parameter: af_click_lookback

More details about the click lookback window here.

Click attribution link

This is the attribution link that contains all the setup information you have set for it. Send it to Aarki to be activated when leads click on a corresponding ad.

View-through attribution lookback window

This slider allows you to set the maximum time from impression to install. Only installs (first launches) that take place within this lookback window, following an ad impression, are attributed to Aarki, providing there was no other relevant ad click.

You can customize this value to 1-23 hours or 1-7 days.

Attribution link parameter: af_viewthrough_lookback

More details about the view-through attribution here.

Impressions attribution link

The impression attribution link contains similar attribution data to the click recording link (besides the different lookback window). Send it to Aarki to be activated when a corresponding ad is watched, usually for 1 second or more.

Cost tab

AppsFlyer gets cost details by API. See the ad network cost integration table for full details on the supported dimensions, metrics, and features. Note: Cost data requires an ROI360 subscription.

To enable the cost API:

View your cost API status and the last time AppsFlyer managed to pull matching cost data in either the cost (and ad revenue) integration status dashboard, or in the individual ad network dashboard. 

Warning

Once you set Aarki cost do not change the name of any running campaign, ad set or single ad as it may cause serious discrepancies or missing cost data.

Ad revenue tab

Ad Revenue data is not supported by Aarki.

Permissions tab

In this tab, you can select the permissions to grant Aarki, whether the partner acts as an ad network, agency or even both. Note that even if attribution is disabled for Aarki, the permissions tab is active and you can grant control to Aarki.

Use these toggles to give the ad network permissions to handle its own configuration for your app:

Ad network permissions

  • Allow to configure integration - permit the partner to setup the integration tab (except in-app event postbacks)
  • Allow to configure in-app event postbacks - permit the partner to setup in-app event postbacks mapping to itself on the integration tab
  • Allow access to your retention report - only to the partner's own retention data
  • Allow access to your aggregate loyal user data - only to the partner's own loyal user data
  • Allow access to your aggregate in-app events data - only to the partner's own in-app events data
  • Allow access to your aggregate revenue data - only to the revenue data attributed to the partner
  • Allow access to your Protect360 dashboard - only to the partner's own Protect360 data, and providing the feature is enabled for the advertiser

Learn more about granting ad network permissions.

Agency permissions

Use these toggles to give the agency permissions to handle its own configuration for your app:

  • Main toggle - Set to On to reveal the agency permissions options
  • Allow to configure in-app event postbacks - permit the agency to setup in-app event postbacks mapping to itself on the integration tab
  • Allow access to aggregate organic data
  • Allow access to your retention report - only to the agency's own retention data

Learn more about granting agency permissions.