Awin campaign configuration

At a glance: Awin (affiliatewindow_int) is an integrated partner that allows advertisers to run UA and retargeting campaigns. Awin's marketing platform helps connect merchants (advertisers) with affiliates (publishers).

awin icon.png

Activate partner

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.

Setting up Awin

The integration with Awin supports click-through attribution.

The general configuration window includes the following tabs: Integration, Attribution link, Cost, Ad revenue, and Permissions. For Awin, the available tabs are Integration, Attribution link, and Permissions.



Before setting up the integration, make sure to implement the required "commission group" parameters in the SDK, as specified in the Awin documentation.


Integration tab

The Integration tab includes a number of sections, as described below.

Activate partner

To configure the integration, you must first turn on the Activate partner toggle. Learn more about activating and deactivating partner integrations

Advanced Privacy

For iOS apps only: Your control over data shared with the partner via postbacks and reports depends on the Advanced Privacy (for iOS 14.5+ and later) toggle state:

Advanced Privacy: On Advanced Privacy: Off

Postbacks are sent only for events attributed to the partner

Postbacks are sent according to your configuration:

  • All media sources, including organic
  • This partner only

Postbacks are sent according to the Advanced Privacy template 


Aggregated and anonymous data is shared with the partner, meaning no user-level data (device ID) is shared.


General settings

Awin advertiser ID

Add your Awin merchant ID.

Default postbacks

Install postbacks are sent to this partner only. 

In-app event settings

Awin advertiser ID

Add your Awin merchant ID.

In-app event postbacks

Configure mapping of in-app events with Awin events, sent via 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

    This partner only: You can send in-app event postbacks only when the event is attributed to this partner—meaning, the user who performed it came from this partner.

    • 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. Set the In-app event postback window, if required (read more about in-app event postback window configuration).
  5. Click Save integration.
  6. [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.


For iOS apps only: Your control over data shared with the partner via postbacks and reports depends on the Advanced Privacy (for iOS 14.5+ and later) toggle state.

Attribution link tab

Generate and save attribution links and send them to the partner for attributing specific campaigns, ad sets, or single ads - both for UA and retargeting campaigns. You can use either a single-platform link or a OneLinkLearn more about attribution link structure and parametersTo generate an attribution link, follow these instructions.

Cost tab

Cost data isn't available for Awin.

Ad revenue tab

Ad revenue isn't available for Awin.

Permissions tab

Select which permissions to grant Awin to access your data and perform various actions.


Deep linking and deferred deep linking using OneLink

AWIN wraps any link used in their platform so that they can provide analytics data to their customers. This means the link will be redirected to AWIN’s site before sending users to their final destination. Learn more about link wrapping.
AWIN as a platform supports a URI scheme but doesn’t support handling the iOS Universal links and Android app link methods of deep linking. This applies to any link used within AWIN.

To deep link with OneLink via AWIN:


For iOS apps, use the af_force_deeplink=true parameter on the OneLink URL to activate the deep link URI scheme.