WebEngage integration with AppsFlyer

For:
Marketers
Last update:

At a glance: WebEngage, an AppsFlyer integrated partner, is an Intelligent Marketing Cloud built for the mobile-first world.

 Important!

Some media sources restrict sharing data with third parties. Therefore, postbacks for restricted events won't be sent to this partner, regardless of the configured selection for sending postbacks.

Setting up WebEngage

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 WebEngage configuration window only makes use of the Integration tab.

Learn more about setting the partner page header.

Integration tab

The Integration tab is divided into different sections, as described below.

Activate partner

On your first visit, turn Activate Partner on to set up the integration. The toggle must be on for as long as you work with the partner. Learn more about partner activation.

General settings

WebEngage connects with AppsFlyer via an API key and the data center region of WebEngage. 

  • api_key: Enter the API key. To obtain it, log in to your WebEngage account, and follow the instructions. 
  • Region: Enter the region where your data is to be hosted: US (for the USA Data Center) or IN (for the India Data Center). By default, all data is stored in the US data center.

web_mo_engage_general_settings_en-us.png 

Default postbacks

AppsFlyer can send automatic postbacks to WebEngage following user installs and re-engagements.

  • Off: Don't send any install postbacks.
  • All media sources, including organic: Send postbacks for events attributed to any partner and for organic events.

web_mo_engage_default_postbacks_en-us.png

 Note

As an all-installs network, WebEngage prefers to receive postbacks for all new installs of your app from any source, including organic. WebEngage recommends selecting All media sources, including organic.

In-app event settings 

Map AppsFlyer events with WebEngage via postbacks. If postback sending is enabled, this includes rejected in-app events (events blocked by Protect360 or events found to be non-compliant by target validation rules).

To configure in-app event postbacks

  1. Enter the api_key and Region.
  2. Enable In-app event postbacks.
  3. Click Add event to add an SDK or server-to-server event to the list.
  4. Complete the parameters required.
  5. [Optional] Clickconditional-iae-postbacks-icon.pngto set conditions for sending certain in-app events to the partner.
    Learn more about conditional in-app event postbacks. 
Parameter Name Description
AppsFlyer event

The event name, 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.
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, including organic events.
including
  • No data (default): send only the event itself without the event value.
  • 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.

Attribution link tab

Attribution link isn't supported in the integration with this partner.

Cost tab

Cost data isn't supported in the integration with this partner.

Ad revenue tab

Ad revenue isn't supported in the integration with this partner.

Permissions tab

Permissions isn't supported in the integration with this partner.