How to Configure a Campaign with Remerge

Introduction

Remerge, one of AppsFlyer's integrated partners, enables app-marketers to deliver better placed, customized advertisements.

In addition to click-based mobile attribution, Remerge also offers retargeting and view-through attribution, which you can track with AppsFlyer.

To configure your campaigns with Remerge, follow the steps below.

Setting Up Remerge

Go to the dashboard of your app and click on Integrated Partners on the left bar.

Integrated_Partners_link.png

Enter "Remerge" in the search field and click on its logo to open Remerge's configuration window.

Remerge's configuration window includes 4 tabs: Integration, Tracking link, Data enrichment 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.

Integration Tab

The Integration Tab is divided into different sections as described below. 

 Note

As an ALL-Installs network, Remerge 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 Remerge. 

 

Default Postbacks

AppsFlyer can send automatic postbacks to Remerge following user installs and re-engagements. Use this section to define the source of the users that allow sending these postbacks. 

remerge2.png

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

In-App Events Settings

In this section you can map your AppsFlyer events with Remerge via postbacks. 
If you choose to map all events (both including and excluding their revenue values) the af_app_opened event will NOT be send to Remerge. 
If you wish to send af_app_opened events to Remerge you must add each event manually.

  1. Toggle In-App Event Postbacks to ON
  2. Select the Sending Option for all SDK defined events.
    - Only events attributed to this partner for events coming only from users attributed to this partner
    - Events attributed to any partner or organic to have your entire user base available to be reported to the partner
  3. Click Add Event to add an SDK Event to the list
  4. Fill in the following parameters:
Parameter Name Description
SDK Event Name The name of the event, as received by AppsFlyer either from the SDK integrated in your app, or from server to server events.
Tip - If you don't see the event you want in the list, make sure to activate the event on a device with a non-organic installation and recheck.
Send Revenue When unchecked - AppsFlyer sends all the parameters of the rich in-app event to the partner, except for the revenue parameter, which is contained in the af_revenue parameter.
When checked - AppsFlyer sends all the parameters including the revenue value (if it exists in the event). 

Tracking Link Tab

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

This tab is divided into different sections:

Tracking Link Parameters

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

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

  • Campaign - add it to compare different campaigns running with Remerge. 
    Tracking link parameter: c
  • Adset - set ad set names to compare different ad sets within specific Remerge campaigns.
    Tracking link parameter: af_adset
  • Ad Name - set ad set names to compare different creatives within specific ad sets within specific campaigns Remerge.
    Tracking 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.
    Tracking 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.
    Tracking link parameters: af_sub1, af_sub2, af_sub3, af_sub4, af_sub5 

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

Retargeting Settings

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

The following setup below is displayed when retargeting is enabled.

msc_new_7.png

1. Standard Link vs. OneLink

Select standard tracking 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 tracking 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.
Tracking 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.

Tracking 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 Remerge.

Tracking link parameter: af_click_lookback

More details about the click lookback window here

Click Tracking Link

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

 

Data Enrichment Tab

Getting Cost Data

Cost Integration is not available for Remerge:

msc_new_12.png  

For the full list of partners supporting cost data, click here.

Permissions Tab

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

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

 

Was this article helpful?
0 out of 0 found this helpful