REMERGE - App Retargeting FAQs

You may grant Remerge with access to reports, which can be achieved either by sharing a report externally or via the Singular dashboard. The latter enables you to add and assign roles to users (and as such, permission to perform certain tasks). Both methods permit data sharing without compromising any information.

The following is a step-by-step guide for the implementation of both options. In case of any questions, please reach out to your Remerge Account Manager.

1. External Report Sharing (Temporary Access)

Selecting this method enables you to create your report, generate a sharable link to this report and share it with others, including those without a Singular account.In order to generate a sharable link, please run your report first, after which follow the below steps:

Log in to your Singular Account and create your report.

Go to the toolbar at the top right of the page and select Create Link.

Data Connectors FAQ

Enter a password (not a requirement, but rather an option) in the Protect with password (optional) box to make your link password-protected.

Select the link's expiration timeframe.Please note: The link expires after 7 days, by default. You may, however, modify the number of days by entering your preferred timeframe in the Link expiration box.

Toggle ON Allow changing date rage to enable the link recipients to view data regarding different dates.

Click on Generate link >Copy Link, and share your newly created link with your recipients.

For further information on external report sharing please visit Singular's Sharing a Report Externally page.

2. Dashboard Access (Permanent Access)

Selecting this method enables you to create/remove users or edit their permissions to access specific trackers and/or apps. Users can be assignedAdmin (full access & team management),Standard(full access), orRestricted(custom access to some of the functionality/data and pages on Singular's platform) roles.

In this section of our support page, we take you through the process of adding Remerge aRestricteduser, which you may achieve by following the below steps. For further information on each role and its permissions, please visit Singular's Team Management page.

1. Add your Remerge User

Log in to your Singular Account, from the upper left-hand corner of the dashboard click onSettings> Manage Team >Team Management.Go to the top right-hand corner and click on theCreate New Userbutton, which opens theNew User wizard, as displayed below:

2. Assign a Role

You should find yourself on the Invite New User page and view the various role options. Click on Restricted> Next, which takes you to theUser Detailsstep.

In the User Details step, enter [email protected] address, name, last name, and description, as displayed below (the latter three are optional). Click onNextto define your user'sPermissions.

3. Configure Access & User Permissions

In the App Selectionstep, add the apps your user should have access to / Select All(you may also toggle ON theAutomatically add future appscheckbox) > Next.

In theSource Selectionstep,enter Remerge as your media source (data connector) your user should have access to / Select All (you may also toggle ON theAutomatically add future sourcescheckbox) > Next. For further information on data connectors, please visit the.

In theMetrics Selectionstep, add the metrics your user should have access to/ Select All(you may also toggle ONtheAutomatically add future metricscheckbox)> Next.

In theScreen Selectionstep, select thepages your user should have access to/ Select All(you may also toggle ON theAutomatically add future screenscheckbox)> Next. Please note:The pages marked with a warning icon will ALWAYS show data related toALLapps and sources, regardless of the access restrictions you may have placed on your user.

Review your setup and selectCreate User. Your newly created user is added to the pending users' list and should select a password upon receiving an email from Singular.

Remerge utilizes the Singular click tracking link to achieve the following goals:

Ensure the most optimal user experience by deep linking the user directly to a specific in-app location.

Notify Singular of a Remerge click.

The following guide takes you through the process of iOS tracking link generation with Singular.We have split this guide into two parts: Legacy Links, and Singular Links. Ensure to review the below-mentioned deep linking and dynamicdeep linking points, our introductory section on Universal Links, and iOS Prerequisites, after which, adhere to the steps in the accompanying guide. In case of any questions, please reach out to your Remerge Account Manager.

General & Dynamic Deep Linking InformationGuidelines

Universal Links- Utilize Universal Links as your deep linking method (iOS version 9 and above).

Enable [x] Retargetingbytoggling ONEnable Reengagementupon tracking link creation. This automatically adds&re=1 to your tracking link, as displayed below. Examples can be found by visiting Singular's Configuring Retargeting and Reattribution page.

Singular Links

In case your tracking link needs to beDynamic, ensure that it contains a variable (e.g.{product_id}) that Remerge can replace dynamically,as this enables us to reroute your users to the exact product page within the app.

Universal Links

In 2015, with the launch of iOS 9, Apple has introduced UniversalLinks to the market and changed the way deep linksare handled in iOS.Universal Linkshave become a standard for iOS 10 and above. They are part of the deep linking ecosystem (and as such offer a deep linking functionality), yetunique to theiOSecosystem.

Legacy Links

Legacy Links are tracking links that are most commonly used by Singular's clients.

Please note:Legacy Links ARE NOTequivalent touniversal links. In fact, universal linksneed to be configured in the iOS app first. That being said, including the universal links upon tracking link creation, adds the benefits ofdeep linking and mobile fallback functionalities.

In the tracking link User Interface, clients may insert their own Custom Raw Scheme and Universal Links.In case the tracking link needs to beDynamicmake sure to add a variableto your User Interface upon deep link creationand append it to your final tracking link.

For step-by-step instructions on Legacy Links creation please follow the below guide.

1. Select App Settings

Log in to your Singular Account, and go toAttribution > Create Link, located on the upper left-hand corner of the dashboard's menu.

Select yourApp,Site, andDestination URL, as displayed below(In case you are unable to find the site and/or destination URL in the drop-down of the corresponding lists, please refer to the Apps screen and update the missing data).

2. Configure Deep Linking

Upon selecting your deep link destination URL:

Select yourdeep linkfrom the corresponding Deeplink Destination URLdrop-down menu.

Ensure your deep link can beutilized as a deferred deep link, by checking the corresponding Deferreddestination option, as displayed below:

3.Locate Remerge

Select Remerge from the list of sources by typing it in thecorresponding Source field, as displayed below.

4.Generate your Tracking Link

Enter Campaign Name,click onGenerate Linkand copy your newly created tracking link by clicking on theCopybutton, located on thebottomright-hand corner, as displayed below:

5. Test yourTracking Link

Send yourself the created tracking link (for example, via an email or slack) and click on it from your mobile phone. You should be able to open the link, and thus, your app. If this is not the case, please review and repeat steps 1-4.

6.Share your Tracking Link with Remerge

Upon completion of the above-mentioned steps and prior to going live, ensure to provide your Remerge Account Manager with the following:

Click tracking link (and impression tracking link if available).

Screenshot of your attribution windows.

Singular Links

* Rolled out to clients as of 01.08.19

Singular Links are tracking links that automatically leverage iOSUniversal Linkstechnology to create deep links.

In order to make yourSingular LinkDynamic,a certain variable (parameter) should be appended to the link. In most cases, clients should simply add&_p={product_id}to their tracking link. Nonetheless, we encourage clients to consult internally on the topic of their redirect method, the exact placement of the variable (e.g. {product_id} or other) as well as the path parameter,&_dl={asdf}.

That being said, we advise to ensure the following:

The path to the exact landing page is placed behind the_dl=parameter.

The exact same path is also placed behind the_ddl=parameter, which ensures that in a deferred deep linking scenario, your user is nevertheless forwarded to the correct location.

Please be advised: In case you have the option of creating both Legacy Links and, please provide Remerge with both, as Remerge benefits from a variety of options.

Remerge utilizes the Singular click tracking link to achieve the following goals:

Ensure the most optimal user experience by deep linking the user directly to a specific in-app location.

Notify Singular of a Remerge click.

The following guide takes you through the process of Android tracking link generation with Singular.We have split this guide into two parts: Legacy Links, and Singular Links. Ensure to review the below-mentioned deep linking and dynamicdeep linking pointsand Android Prerequisites, after which, adhere to the steps in the accompanying guide. In case of any questions, please reach out to your Remerge Account Manager.

General & Dynamic Deep Linking InformationGuidelines

Enable [x] Retargetingbytoggling ONEnable Reengagementupon tracking link creation, as displayed below. This automatically adds&re=1 to your tracking link.Examples can be found by visiting Singular's Configuring Retargeting and Reattribution page:

Singular Links

In case your tracking link needs to beDynamic, ensure that it contains a variable (e.g.{product_id}) that Remerge can replace dynamically,as this enables us to reroute your users to the exact product page within the app.

Legacy Links

Legacy Links are tracking links that are most commonly used by Singular's clients.

In the tracking link User Interface, clients may insert their own Custom Raw Scheme.In case the tracking link needs to beDynamicmake sure to add a variableto your User Interface upon deep link creationand append it to your final tracking link. For step-by-step instructions on Legacy Links creation please follow the below guide.

1. Select App Settings

Log in to your Singular Account, and go toAttribution > Create Link, located on the upper left-hand corner of the dashboard's menu.

Select yourApp,Site, andDestination URL, as displayed below(In case you are unable to find the site and/or destination URL in the drop-down of the corresponding lists, please refer to the Apps screen and update the missing data).

2. Configure Deep Linking

Upon selecting your deep link destination URL:

Select yourdeep linkfrom the corresponding Deeplink Destination URLdrop-down menu.

Ensure your deep link can beutilized as a deferred deep link, by checking the corresponding Deferreddestination option, as displayed below:

3.Locate Remerge

Select Remerge from the list of sources by typing it in thecorresponding Source field, as displayed below.

4.Generate your Tracking Link

Enter Campaign Name,click onGenerate Linkand copy your newly created tracking link by clicking on theCopybutton, located on thebottomright-hand corner, as displayed below:

5. Test yourTracking Link

Send yourself the created trackinglink (for example, via an email or slack) and click on it from your mobile phone. You should be able to open the link, and thus, your app. If this is not the case, please review and repeat steps 1-4.

6.Share your Tracking Link with Remerge

Upon completion of the above-mentioned steps and prior to going live, ensure to provide your Remerge Account Manager with the following:

Click tracking link (and impression trackinglink if available).

Screenshot of your attribution windows.

Singular Links

* Rolled out to clients as of 01.08.19

Singular Links are tracking links that automatically leverage Android intent technology to create deep links.

In order to make yourSingular Links Dynamic,a certain variable (parameter) should be appended to the link. In most cases, clients should simply add&_p={product_id}to their tracking link. Nonetheless, we encourage clients to consult internally on the topic of their redirect method, the exact placement of the variable (e.g. {product_id} or other) as well as the path parameter,&_dl={asdf}.

That being said, we advise to ensure the following:

The path to the exact landing page is placed behind the_dl=parameter.

The exact same path is also placed behind the_ddl=parameter, which ensures that in a deferred deep linking scenario, your user is nevertheless forwarded to the correct location.

Please be advised: In case you have the option of creating both Legacy Links and, please provide Remerge with both, as Remerge benefits from a variety of options.

Below is our step-by-step guide to activation of event forwarding from Singular to Remerge. In case of any questions, please reach out to your Remerge Account Manager.

1.Locate & Activate Remerge

Go to Attribution > Partner Configuration, located on the upper left-hand corner of the dashboard's menu and findRemergeby entering itin thePartner Configuration search field, as displayed below:

https://remerge.events/event?app_id={{sng_app_id}}&event={EVTNAME}&partner=singular&key=43f23mn99&idfa={IDFA}&os_name={PLATFORM}&os_version={OS_VERSION}&ts={UTC}&revenue={MULTIPLY|{AMOUNT},1000000}&currency={CURRENCY}&attributed={NETWORK=Remerge}&creative={pcrn?Remerge}&click_id={cl?Remerge}&app_version={APP_VERSION}&data={GOOGLE_EVTATTR}&campaign={pcn?Remerge}&ad={pscn?Remerge}&country={EVENT_COUNTRY}&country_subdivision={EVENT_STATE}&city={EVENT_CITY}

2. Configure Event Forwarding

Go to theApp-specific Configurationsection, located on thePartner Configuration page and create your event postbacks, as instructed below and displayed in the accompanying screenshots:

Add App name and Site(Platform) to their corresponding fields.

Ensure the Enable Re-engagement Postbacks and Send Postbacks to REMERGEon all installs boxes are ticked.

Add your App store ID and select your Click-through attribution lookback window.

Go to the Event postbacks section, select All from the Send in-app events to REMERGE,and click on the Save button upon completion. Repeat said steps for the rest of your postback configurations. Please note:

Postback configuration is app-specific and as such, might differ from client to client.

Should your event include a Revenue value, we recommend providing Remerge with this value.

The following are examples of the final event postback template for Android & iOS:

Global Postback Android URL:

https://remerge.events/event?app_id={LONGNAME}&event={EVTNAME}&partner=singular&key=43f23mn99&aaid={AIFA}&os_name={PLATFORM}&os_version={OS_VERSION}&ts={UTC}&revenue={MULTIPLY|{AMOUNT},1000000}&currency={CURRENCY}&attributed={NETWORK=Remerge}&creative={pcrn?Remerge}&click_id={cl?Remerge}&app_version={APP_VERSION}&data={GOOGLE_EVTATTR}&campaign={pcn?Remerge}&ad={pscn?Remerge}&country={EVENT_COUNTRY}&country_subdivision={EVENT_STATE}&city={EVENT_CITY}

Global Postback iOS URL:

Dynamic Ad Campaign:As of August 2019 and going forward,&data={GOOGLE_EVTATTR}is automatically appended to clients' postback template URLs. Clients that have initiated event forwarding prior to August 2019, should simply click on SAVE,whichactivates the new postback template URL.

3. Confirm Setup

Provide your Remerge Account Manager with a screenshot of your final configuration, as per the below example, to confirm the arrival of events and alignment of attribution windows.

Naming conventions and attribution models are both subjected to a partner's preference and marketing strategy and therefore can vary from partner to partner.

We have decided to share the following clarifications to ensure alignment between the different parties with respect to the exchanged information and expected performance. Below you should find insight into Adjustvs. Remerge specific terminology, followed by answers to the most frequently asked questions.

Terminology

Adjust

Click -Adjust counts a click each time a tracking link hits Adjust's serverin one of the following ways:

A desktop click.

A campaign click.

In the case of a double click (either due to an issuewith an operating system, SDK implementation and/or versionbug or a userclicking the same ad twice), all server hits will appear on the Adjust dashboard.

Attribution - You are most likely to run with multiple ad networks and/or agencies, and as such, Adjust utilizes the combined knowledge of all your marketing activities for the purpose of attribution. Adjust is not limited to Remerge clicks for attribution. This means that Adjust reviews and displays any potential attribution coming in from partners. However, once an event is attributed to Remerge, it maintains its status as alife-long attributed (to Remerge) event until said event is attributed to a different partner.

Dashboard- Reattribution & Inactivity:

Reattribution

Reattribution Window- Defines the timeframe in which events triggered by either an ad impression or a click should be reattributed to a certain partner.

Reattribution Settings - Adjust offers a default 7-day reattribution window, on an App-level. That being said, Adjust also offers adjustable app-based reattribution settings, and allows you to customize both your reattribution windowsand inactivityperiod, based on the pricing plan you have agreed upon with Adjust, as follows:

Basic&Business-7-Day App-levelreattributionwindow (NOTcustomizable).

Business Pro,Enterprise & Flat- Customizablereattributionwindow (onApp- Level).

Enterprise & Flat- Customizablereattributionwindow (onTracker-level).

Please note: The tracking links can be created on three different levels:Network (top-level),Campaign (sublevel 1),Adgroup (sublevel 2). However,we advise you to utilize the top-levelupon tracking link creation, as it guarantees that you provide us with the correct level.

Inactivity

Inactivity Period- Defines the number of consecutive days a user must be inactive (lapsed) in order to be eligible for a retargeting campaign. In order tomaximize the impact of your retargeting campaign, ensure to set the inactivity period to 0.

That being said, we recommend performing the following two steps for both reattribution windows and inactivity period:

Set your reattribution window and inactivity period on theApp-levelin order for all of your tracking links (levels) to inherit the inactivity period and attribution windows from theApp-level.

Provide Remerge with a Network-leveltracking link (and thus inherit the inactivity period and attribution windows from theApp-level).

These two requests stem from the fact that utilizing tracking links on multiple levels might bring about confusion (which we would strongly like to avoid), as the various level-based windows override each other.

You may retrieve theinactivity period and attribution windows from either the App or Networklevelas follows:

App Level

Log in to your Adjust Account, go toMENU>Apps, and select your app.

Click on the bottom drop-down arrow, go toSET UP YOUR APPand select All Settings> Attribution.

From theAttribution Settingsscreen:

Click on Reattribution for Clicks.

Click onReattribution for Impressions.

Network (Partner)Level

Log in to your Adjust Account, go toMENU>Apps, and select your app.

Click on the bottom drop-down arrow, go toSET UP YOUR APPand selectAll Settings >Trackers.

Locate your tracking link from the Network-Level Trackers list and click on the wheel symbol > EDIT.

From theAttribution Settingsscreen:

Click on Reattribution for Clicks.

Click onReattribution for Impressions.

Remerge

Click-Remerge countsone click per an OpenRTB impression ID. In case of an issue with an operating system, SDK implementation or a user clicking the same ad twice, we deduplicate the click and count it only once.

Attribution-You are most likely to run with multiple ad networks and/or agencies.However, Remerge does not have visibility or insight into any other campaigns you could potentially be running with other partners. In fact, our dashboard takesALLof the clicks that were triggered by Remerge (and that fall within the attribution windows and inactivity period communicated to us) into account, and as such you are able to see the full effect of your Remerge campaign activity.Ensure to keep Remerge updated on any changes in your windows.

Frequently Asked Questions

1. Why are there several clicks on the Adjustdashboard, even though the Remerge campaign is no longer running?

Certain publishers purchase an ad with the click URL and wait for the optimal moment in order to display it to a user. When a campaign is stopped on Remerge's side, we stop displayingads to publishers. However, when a certain publisher already owns an ad, we have no influence on when the admight be displayed. In this scenario, certain impressions and clicks might arrive delayed and thus appear on the Adjust dashboard.

2.Why is there acontinuously growingnumber of clicks on theAdjustdashboard,even though the Remerge campaign is no longer running?

These are non-Remerge clicks. In fact, the click tracking link is being executed outside of our campaign.

This might occur eitheraccidentally or if someone tries to trick the system by catching the click tracking link and use it repeatedly. As previously mentioned, these clicks are not triggered by users clicking your ad in a Remerge campaign. If the URL got caught in the wide ecosystem and is being employed, Remerge can, unfortunately, neither influence nor stop this from taking place.

3.What should I do ifI have my own universal link?

We are happy to support you in this case.Please provide us with information on your link's functionality as well as the fallbacks (in case a certain user has uninstalled the app), in order for us to test the link.

In order to attribute the events correctly via your own link, ensure to append the Adjust tracking link to your own custom URL (&adjust_tracker=f0ob4r). This enables the Adjust SDK to attribute conversions to the correct partner. Additionally, we employ the standard tracking link to notify Adjust of the clicks server side.

4. Should I enable Ad Spend on the Adjust dashboard?

Please note: TheAd Spend valuesdisplayed on theAdjustdashboard slightly differ from the ones displayed on our dashboard, for the following reasons:

iOS- The expected discrepancy is roughlybelow 1 \%, as Remerge utilizes the JSR solution for your universal links. This functionality enables Remerge to send clicks to Adjust from their Own Server, which ensures a high level of accuracy and quality of sent clicks. In other words, Remerge is able to avoid potential click duplications, delays, or interruptions/losses.

Android - The expected discrepancy is roughly below 5\%, as Remerge sends the click information to Adjust via the Android Standard Tracker. This process is executed from the client's mobile phone, which implies that Remerge cannot control potential duplication, delays, or interruptions/losses. As a general rule, an (up to) 5\% loss of click costs is to be expected.

If you wish to track cost data, ensure to enable this functionality on the Adjust dashboard as follows:

Log in to your Adjust Account, go toMENU>Apps, and select your app.

Click on the bottom drop-down arrow, go toSET UP YOUR APPand selectAll Settings >Trackers.

Locate your tracking link from the Network-Level Trackers list and click on the wheel symbol > EDIT.

Go to Additional Parameters,toggle ON AD SPENDand click on APPLY.

5.Should I enable Device Matching on the Adjust dashboard?

Yes, you should. Remerge relies onDevice Matchingfor attribution, and as such, it must be enabled. The belowinstructions guide you through the process ofDevice Matchingenablement on an App-level,as it ensures that more granular campaign levels (e.g., tracking link), inherit the mentioned functionality by default:

Log in to your Adjust Account, go toMENU>Apps, and select your app.

Click on the bottom drop-down arrow, go toSET UP YOUR APPand selectAll Settings >SETTINGS > Attribution.Youshould find yourself on the Attribution Settings page.

Review the toggled options located on the Attribution Settings page, and ensure that all of the below-listed functionalities are toggled ON. If this is not the case, please toggle them ON and click on the SAVE button, located on the bottom of the functionality's corresponding window:

CLICK BASEDsection:

Device Matching

Reattribution for Clicks

IMPRESSION BASED section:

Device Matching

Reattribution for Impressions

Please note:

Configuration ona more granular level requiresDevice Matching enablementon the corresponding level.

The device matching window should be at the very least as long as or longer than your reattribution window.

You may grant Remerge with access to reports as well as permission to perform certain tasks (such as tracking link configuration and in-app event mapping), which can be achieved upon clicking on the fifth tab of AppsFlyer's configurationwindow, the Permissionstab. The tab you are located on is always both highlighted and underlined as shown below:

Event Forwarding with AppsFlyer Guide

The following is a step-by-step guide to grant portal access and permissions to Remerge. In case of any questions, please reach out to your Remerge Account Manager.

1. Enable In-App Retargeting

Log in to your AppsFlyer Account andselect your app.

Click onApp Settingsand toggleONEnable Re-Targeting Campaign Measurement,located on the bottom of the page.

2. Locate & Activate Remerge

Go to thenavigation menu, located on the left-hand corner of the dashboard, scroll down toConfigurationand selectIntegrated Partners.

FindRemergeby entering itin the search field and click on itslogoto open ourconfigurationwindow, as displayed below:

Toggle ONActivate Partner. Please note:Each partner integration (advertisers & agencies) requires an initial manual activation.The Activate Partner toggle MUSTremain ONat ALL TIMES.For a step-by-step guide and further information on the Integration tab please visit our.

3. EnablePartner Permissions

Click on the Permissions tab, and toggle ONAd Network Permissions.

4. Configure Partner Permissions

You may activate various functionalities by toggling them ON,which provides us with as much access as you see fit. HOWEVER:

In order for us to support your app configuration, remain on the Permissionstab and ensure to at least activate the following two permissions:

Allow to configure integration(which enables Remerge to generate tracking link URLs), and

Allow to configure in-app event postbacks(which enables Remerge to set up in-app event postbacks mapping to itself on the integration tab).

Introduction

Remerge is an app retargeting platform. In addition to our dashboard and analytical capabilities, clients are able to pull JSON-based reports from the Remerge Reporting API for their active campaigns to their internal BI on a daily granularity basis.

A client's performance is broken down into five dimensions: Timestamp, Country, App, Campaign and Related Ads. Therefore, the results can be easily imported, split into smaller parts and distributed according to the provided dimensions to any Business Intelligence platform chosen by the client. For further information on specific parameters and fields, we strongly recommend reviewing our Index sectionbelow.

Endpoint

The API is accessible via the following endpoint:

https://api.remerge.io/report

Request Parameters

Remerge Reporting API provides a simple interface to query data. A start and end date are the only parameters required.

Name

Content

Examples

Mandatory

*start_date

Report start date (YYYY-MM-DD)

2017-01-09

x

*end_date

Report end date (YYYY-MM-DD)

2017-01-10

x

dimensions

A comma-separated list of dimensions to split the aggregates by defaulttoaudience, country, campaign, and adif not passed. Possible dimensions:audience, country, campaign, ad, ad_label or platform.

country, platform

A valid request would look as follows: https://api.remerge.io/report?start_date=2017-01-10&end_date=2017-01-11&dimensions=campaign,ad

Note:

We recommend that you utilize a text editing program (such as Sublime or Atom) to ensure that all of the symbols in your query are transferred to the terminal correctly.

Unless you limit the dimensions in your request URL, the response will generate all potential dimensions.

Authorization

The request must be authorized. In case you already have access to your dashboard login, please issue a sign-in request to api.remerge.io, in order to receive the necessary information for the authorization token.If this is not the case, please contact your Remerge Account Manager in order to obtain your dashboard login.

Example

Sign-in Request

curl -H 'Content-Type: application/json' -H 'Accept: application/json' -X POST

-d '{"user" : { "email" : "[email protected]", "password": "password"}}' https://api.remerge.io/users/sign_in

Returning the needed token as JSON

{"email":"[email protected]","token":"J-QeJxyza7JH19QUDb4","user_id":1234,"user_name":"Peter Example","user_token":"J-QeJ49Yasdf219QUDb4"}

Mandatory Request Headers for a Valid Reporting Request

Name

Content

Example

Mandatory

Request Header

Content-Type

'Content-Type: application/json'

x

Request Header

Acceptance

'Accept: application/json'

x

Request Header

Authorization Token

'Authorization: Token user_token="HJn4OYViZv", email="[email protected]"'

x

Request Type

POST

POST

x

Example Request

Below is an example of aPOSTrequest to theRemerge Reporting APIusing the data transfer tool curl :

curl -H 'Content-Type: application/json' -H 'Accept: application/json' -H 'Authorization: Token user_token="HJn4OYViZv", email="[email protected]"' -X POST "https://api.remerge.io/report?start_date=2017-01-10&end_date=2017-01-11" -v

Response Fields

The response returns a JSON object containing a results array and an element count. Each array element consists of the following fields:

Name

Content

Example

timestamp

UTC Timestamp

2017-01-11T00:00:00.000Z

event.platform

Platform (iOS /Android)

ios

event.country

RTB Geo-Information

de

event.campaign

Internal Remerge Campaign ID

42

event.campaign_name

External Remerge Campaign Name

Test Campaign

**event.cost_currency

Internal Remerge Campaign Currency

EUR

***event.audience

App Store Reference

12345678

event.ad_id

Creative ID

1406561

event.ad_name

The unsanitized file name of the image/video asset

banner_300_50.png

event.ad_label_id

Creative Label ID

18304

event.ad_label_name

Creative Label Name

non_purchasers_it

****event.ad_creative_url

Creative URL

https://assets.remerge.io/ad_assets/files/000/006/696/original/banner_300_50.png?1478088208

event.impressions

Daily Impression Counter on App.Country.Campaign.Ad Level

2

event.clicks

Daily Click Counter on App.Country.Campaign.Ad Level

1

event.app_open_rate

Counted App-Opens for Clicks in percent

83.57

event.cost

Cost in Customer Currency on App.Country.Campaign.Ad Level

0.12

event.conversions

Daily Target Conversion Event Counter on App.Country.Campaign.Ad Level

1

event.unique_user

Daily Unique User Counter on App.Country.Campaign.Ad Level

2

Example JSON Response (two display option of the same query)

Option 1:

{results: [{"timestamp":"2017-01-11T00:00:00.000Z","event":{"impressions":2,"audience":"12345678","app_open_rate":1.0,"clicks":1,"ad":"test.jpg","user_id":2,"conversions":1,"campaign":"42","country":"de","cost":0.12,"campaign_name":"Test Campaign"}}],count:1}

Option 2:

In case of no existing data for the given interval, the request returns an empty results array and counts: 0

List of Potential Errors

Status

Message

Explanation

200

OK

Query results returned as JSON

401

Unauthorized

The provided Authorization token was invalid

422

start_date: Format YYYY-MM-DD required

Start Date ill-formed

422

end_date: Format YYYY-MM-DD required

End Date ill-formed

422

start_date: must be a valid date

No real date provided, e.g. 2015-33-09

422

end_date: must be a valid date

No real date provided, e.g. 2015-33-09

422

end_date: end date must be greater or equal to the start date

End date is earlier than start date

422

queryID: queryId already exists

The user has already sent a request which is still processed by the API, i.e query rate limit per user is 1.

504

Gateway Timeout

The request took to long for the web server to process. This is typically due to a too broad of a query interval. In this case, please try again with an interval of 14 days, at most.

Index

* API Timestamp-The start_date and end_date are both set by default to00:00 midnight of that day. This means that if, for instance, you would like to query exactly one day, use that day as start_date and the next day as end_date. Make sure to only request one day of data at a time(For instance, request every day the data for yesterday and store it in your internal database).

**Ensure to split your report by campaign, in case you are employingdifferent currencies for different campaigns.

*** Remerge uses the term Audience as a reference to your entire application (unlike in some contexts, where an audience refers to a segment). Upon pulling a report,Remerge Reporting API will give back a field called Audience. This simply means that the said report contains static data for your entire app.

**** In the case of Dynamic Ads, the creative URL displayed is only a placeholder as the real creative URLs are dynamically taken from the feed. Unfortunately, they cannot be displayed in this reporting.

The Video Adis a form of digitalad that contains a video with a clear Call-To-Action (CTA) and due to its disruptive nature implies by default that the user is usually required to view the video to the fullest extent.

Remerge delivers video ads compliant with the IAB VAST 3 standard and offers this ad format to clients who have video assets for retargeting campaigns.In favor of maximizing on scale and performance, we strongly advise that you always provide us withboth Portrait & LandscapeVideos.

Video[Portrait + Landscape]

Dimensions

Smartphone- 9:16, 16:9[max file size: 30Mb].

Tablet- 3:4, 4:3[max file size: 30Mb].

In the interest of optimal user experience, we donot crop/stretchvideo assets to match the required partner dimensions. For that reason, and in case you are running campaigns on both smartphone + tablet, please provide us with all of the above-mentioned video formats.

File Type

Supported media MIME types: We support .mp4 and .webm file types.

Length

Required Length -530 seconds.We have found 10-15 and 25-30 second videos to be the most effective. Manypublishers treat 0-15 second videos as non-skippable videos.For scalability reasons, we support only videos of up to 30 seconds in length.

Companion Banners (End Cards)

Dimensions

Remerge supports companion banners (end cards) and as such requires the following dimensions:

Smartphone-1280 x 720,720 x 1280 [max file size: 200kb].

Tablet-1280 x 960,960 x 1280 [max file size: 200kb].

Templates

Below are downloadable templates your creative team may utilize in order to create the banners:

Photoshop (.psd)

Illustrators (.ai)

In case that your design team is unable to provide us with companion banners, please reach out to your Remerge Account Manager and provide them with your brand assets and guidelines (such as logo, fonts, color palettes). Remerge will then create the banners on your behalf.

Companion Banner Examples

Smartphone:

Tablet:

Pro Tip:Static banners from your previous campaigns could potentially be repurposed into end cards!

Video Best Practice Guidelines

1. Refrain from ending your videos with the app store icon, as we will redirect your user to the app.

2. Ensure to provideboth Portrait & Landscapeformats.

3. Ensure to provide video end cards.

The Native Ad format matches both the form and function of the user experience of the app in which it is placed. Implementing Native Ads is a great way of adding scale to your Remerge campaigns and retargeting your users through amore engaging channel.

Remerge is compliant with Native 1.0 as used in the OpenRTB 2.4.We support the in-app IAB Standard with the Native Element Units Ad Format. For your convenience, please find information on an especially useful Native Preview Tool and its implementation, courtesy of one of our SSPs, Mopub.

In order to leverage native ads for your campaigns, please provide us with the Main Image, Copy (title, description, and a call-to-action), and Star Rating, as listed below.For further information, please reach out to your Remerge Account Manager.

1. Main ImageExample (1200x627 or 1200x628)

2. Copy

Title-Ad headline (consisting of up to 25 characters).

Description-Open text field describing the ad (consisting of up to 100 characters).

Call to Action- Text field for the call-to-action button (consisting of up to 15 characters).

3. Star Rating

User rating

The following are examples of the mentioned-above CreativeAssets and a Native Ad:

App Icon is one of thecomponents of a native ad, and as such, it needs to be utilized by the publisher in order to assemble the ad. That being said, you do not need to provide this component toRemerge. Instead, we retrieve it from the respective digital store (App/Google Play Store) and forward it to the publisher.

Below is an overview of the three action steps we suggest you take in order to start running Static Ads with Remerge.

Please note: Google conducts an initial inspection and validation of your creatives. In order to carry out this inspection, Google needs to be able to checkyourbid response domain, by employing a crawling Google bot. In other words,your website URLMUSTbe crawlable for a Google bot. In case this bot is unable to crawl (inspect) your site, your creatives might remain unvalidated or potentially even getrejected.

Prior to taking the action steps specified in this document, and in order to avoid any potential issues associated with the rejection of your creatives, ensure your URL is in fact crawlable.

The following is a list of common crawl errors: robots.txt failures, DNS, server, or unreachable URLerrors.

For further information on ensuring website crawlability, please visit the Common Errors FAQ and Best Practice pages.

Action Steps

1. Target Audience Analysis

A clear understanding of your audience is an integral part of a successful marketing campaign. We strongly recommend that you conduct an analysis of your target audience andconsider answering the following questions:

Who is your target audience?

What is the goal of your campaign?

At What Point of the customer journey are you communicating with them?

What Actions has your user taken so far?

What is youruser doing right now?

Where will they be taken to upon clicking?

2. Digital Store Research

Once you have collected theabove-mentioned information, please visit the digital store (App Store/Google Play)of the platform/s on which your app is located. This is an especially important step, as the creative material found in these stores renders useful and unique to your app information, such as:

Unique app features and highlights.

App updates.

Special promotions and offerings.

3. Creative Guidelines

Next, please comply with the following best practice guidelines:

Do Not Recycle User Acquisition Ads

The Click-Through-Ratefor user acquisition banners is two times lower thanfor retargeting banners. That being said, should you nevertheless decide to use the same images, ensure to change the Call-To-Action text to best fit your campaign needs.

Offer Additional Value

Promotional codes and limited time offers create a sense of urgency that leaves a strong impression on your user and prompts them to take action.

Make your Call-To-Action Visible

We recommend utilizing the same color for both your logo and the Call-To-Action (CTA) button.

Optimize your Message

Perfect your messaging by putting yourself in your user's shoes. Consider which messaging style might appeal to your user.

Opt for aShort Call-To-Action

Limit your Call-To-Action to a maximum of 15 characters. Short and relevant Call-To-Actions outperform long and overly descriptive messages.

Static Ads are the advertising images (banners) that Remerge uses in order to run retargeting campaigns.

These types of ads are easily maintained as they contain permanent (static) content that needs to be assembled only once, which makes for an easily monitored ad format that requires a relatively low time commitment.That being said, and especially since the content of such ads is of an unvarying nature, their creation requires accuracy and precision.

Static adsmight appearin a variety of formats, such as image, video, or animation. However, and regardless of the displayed format, static adsare referred to as static since all of the users are exposed to the same set of ads.

Clients can provide us with more than just one set of static ads.We group all of the differentsizes/formats of a certain ad and combine them into a single Ad Label.

TheAd Label can have timers, and as such, be turned ON and OFF by the system. This means that if, for instance, a client would like to show Valentines' Day ads, we can ensure to exclusively displaysaid adswithin the requested timeframe.

Below is an example of the dashboard settings you may choose in order to view the performance of your campaign per ad and/or ad label:

Prohibited Content

For further information on our creative guidelines, supported ad formats and sizes, as well as prohibited content rules, please visit our Best Practice Principles, Static Assets, Native Assets, Video Assets, and pages.

Many of our suppliers and partners place restrictions on the type of content they prefer to display. Therefore, please refrain from utilizing ads which promote content or pictures that resemble any of the mentioned in the following list *:

Ads making misleading or deceptive claims: IAB26-1 (Illegal Content)

Adult sexual content: IAB25-3 (Pornography)

Copyrighted materials: IAB26-4 (Copyright Infringement)

Counterfeit goods: IAB26-4 (Copyright Infringement)

Drugs and drug paraphernalia: IAB26-1 (Illegal Content)

Endangered species products: IAB26-1 (Illegal Content)

Hate content, sensitive topics, and violence: IAB25-5 (Hate Content), IAB25-2 (Extreme Graphic/Explicit Violence)

Illegal products and services: IAB26-1 (Illegal Content)

Incentivized clicks and downloads: IAB25-7 (Incentivized)*

Spyware and illegal hacking: IAB26-3 (Spyware/Malware)

Tobacco and tobacco accessories: IAB9-9 (Cigars)

P2P file-sharing apps, torrent or any apps that facilitate or promote copyright infringement :

IAB26-4 (Copyright Infringement)

Unauthorized ticket sales: IAB26-1 (Illegal Content)

Weapons and weapons accessories: IAB26-1 (Illegal Content)

* Please note: Any content and/or image that can potentially be associated with the mentioned list of categories (e.g., a lingerie creative can be mistaken for adult content or a smoking monster advertising your new video game can be mistaken for a tobacco ad) are prohibited by default.

For more information please refer to our partners' documentation:

MoPub Policies for Demand Side Partners

IAB Categories

Remerge supports the implementation of Flexible Sized Ads (also known as Aspect Ratio Ads).Please provide us with the four ad dimensions specified in our Flexible Sized Ad Dimensions list.In case you require support in the creation of said dimensions, we can create them on your behalf, as mentioned in our In-house Design Solutions section.

What are Flexible Sized Ads?

Flexible Sized Ads (or Flexible Sized Ad Units) are ads, developed from IAB Standards, and based on width: height aspect ratio and size range (rather than fixed pixel creatives). For more information on Flexible Sized Ads please visit the IAB New Ad Portfolio and the IAB New Ad Portfolio Transition Guidance pages.

Aspect Ratio refers to a creative’s width: height ratio. According to the IAB New Ad Portfolio, a Flexible Sized Ad might accommodate different sizes within its defined size range, but it must always maintain its aspect ratio. For instance, a 6:1 (width: height) ad might appear bigger on an iPhone 6 Plus display and smaller on an iPhone 5, but its width and height will always remain in the 6:1 ratio.

Flexible Sized Ads Benefits & Competitive Edge over Fixed Pixel Ads

Ad content delivery across multiple screen sizes and integration with responsive website design.

Scalability of the creative design to different screen sizes:

Ability to scale down using best-fit logic to cover all ad spaces.

0\% loss in creative quality, messaging and impact of the original content, as no stretching or distortion of the image or visual alteration is taking place.

Equality in performance.

The requirement of fewer creative assets (4 instead of up to 15!), which equals:

Faster campaign go-live.

Less effort on your end.

Maximum reach - We maximize your traffic by filling all potential ad slots, available on OpenRTB. By employing the best-fit logic, we are able to display the right-sized ad to the right user and thus cover the entire spectrum of users on the RTB exchange.

Flexible Sized Ad Dimensions

Ratio

Pixels

2:3

800x1200

1:1

500x500

3:2

1200x800

6:1

900x150

Implementation Guidelines

In order to ensure optimal campaign performance, thefile size should not exceed 500 Kb.

In order to download templates with pre-set ad sizes please see Photoshop / Sketch.

Below examples display our ability to fill 3 Ad Spaces(dimentions: 300x50, 320x280, and 320x50) by utilizing only2 Creative Assets(aspect ratio: 6:1 and 1:1):

Remerge is nevertheless also able to accept the following Fixed Pixel assets (in case said assets are already at your disposal) :

32050px, 320480px, 480320px, 250250px,16828px, 30050px, 46860px, 320100px, 300100px, 320280px, 300250px, 72890px, 7681024px,1024768px, 300250

File Support Guidelines

We support .png, .gif and .jpg files.

Animation Specifications

Animation length should be up to 30 seconds or shorter.

Animations can be looped but should also stop after 30 seconds.

Animated GIF ads should be slower than 5 FPS.

In-house Design Solutions

In case you are unable to come up with the above-mentioned sizes, please provide us with the source files of your previous campaigns, alongside brand assets. Our creative team utilizes said information and assembles the ads on your behalf. We accept source files in the following formats: Photoshop (.psd), Illustrator (.ai), and Sketch (.sketch). Prior to sending us the files, please ensure the following:

All potentially linked objects are embedded - no layers are linked to objects in external files.

The fonts you have provided us with are either not free or on Typekit / Google Fonts.

Remerge utilizes the IGAWorks: Adbrix Remaster click tracking link to achieve the following goals:

Ensure the most optimal user experience by deep linking the user directly to a specific in-app location.

Notify IGAWorks: Adbrix Remaster of a Remerge click.

The following guide takes you through the process of Android and iOS tracking link generation with IGAWorks: Adbrix Remaster.To support you with an especially user-friendly implementation, we have split this guide into two parts: the first is meant for your Developer, while the latter, Marketer.

Developer Guide

Follow the belowinstructions toensure your app is configured to handle deep linking.

1. Set Up Deep Linking forAndroid

Configure Deep Linking

Intent Filter- Add the 'intent-filter' to the AndroidManifest.xml file, as displayed below:

Event Forwarding

App Key- In case you have yet to decide on the scheme value, you may edit the AndroidMadifest.xml file by utilizing the AdbrixApp Keyinstead, as displayed below (inourspecificexample,Adbrix App Key=123456):

Test yourDeep Link

Build and open the app you have configured fordeep linking (Configure Deep Linkingstep).

Open the Window Command (Win+R key, enter 'cmd').

Run thedb shell:

Enter the adb command. In case you are utilizing the Adbrix App Key, enter the ''adbrix123456://'' in the [URI}:

A functioning app during the testing phase indicates a successful deep linking configuration. For further information on setting up deep linking, please visit Android's Deep Linking Training and How To Set Deeplinking pages.

2. Set Up Deep Linking foriOS

Configure Deep Linking - Edit theinfo.plistfile by following the below steps:

Go toXcodeand open theInfo Panel.

Scroll down, open theURL Typessection, and add theURL Schemes.

In case you have yet to decide on the scheme value, you may utilize the AdbrixApp Keyinstead, as displayed below(inourspecificexample,Adbrix App Key=123456):

Test yourDeep Link

Build and open the app you have configured fordeep linking (Configure Deep Linkingstep).

Open the app using the Safari browser andenter the scheme value in the address bar. In case of using an Adbrix App Key, enteradbrix123456://.

A functioning app during the testing phase indicates a successful deep linking configuration.For further information on setting up deep linking, please visit our Deep Linking Enablement page.

3. Locate your App

Log in to your IGAWorks: Adbrix Remaster Account, go to the upper left-hand corner of the navigation menu and select your app by clicking on the arrow to the right of your app name.

Go to the search field, enter your app name, and click on its corresponding box, as displayed below. Upon completion, click on the Save button, located on the bottom of the page.

4. Configure Landing Page Settings

Go toAttributions > AD Landing Settings, located onthe upper left-hand corner of the navigation menu.

Android

Go to thedefault URL(Required field)field and enter your fallback URL. Ensure your URL starts with thehttps://extension, as displayed below:

Go to theDeeplink Scheme(Optional)field and enter your custom scheme:

Ensure the custom scheme leads to an app open.

Please refrain from adding :// to thecustom scheme.Your custom scheme should be entered as follows:myapp.

Go to the Package Name fieldand enter your app package name,as displayed below:

You may also select the Enable App Links option, by checking its corresponding box and entering the SHA256 Cert Fingerprintsin its corresponding field.Please note:App Links come with certain limitations. Therefore, in case you choose to utilize App Links, please ensure to inform your dedicated Remerge Account Manager.

iOS

Go to thedefault URL(Required field)field and enter your fallback URL. Ensure your URL starts with thehttps://extension, as displayed below:

Go to theDeeplink Scheme(Optional)field and enter your custom scheme. Ensure your custom scheme leads to an app open.

Ensure the custom scheme leads to an app open.

Please refrain from adding :// to thecustom scheme.Your custom scheme should be entered as follows:myapp.

Go to the App Store ID field and enter the required information.

Select the Enable Universal Links option, by checking its corresponding box and entering the Application Identifierin its corresponding field.

PC

Go to thedefault URL(Required field)field and enter your website's URL. Please note: Remerge is an IN-APP ONLY network. The URL information in this specific field is necessaryto simply enable you to save this part of the configuration and continue to the next step.

Go to the App Download Page field and enter the required information.Upon completion, click on the Save button, located on the top right-hand corner of the page.

Enter your email address and clickon the Save button, located on the bottom of the pop-up window.

Marketer Guide

This part of the guide takes you through the process of Android and iOS tracking link generation with IGAWorks: Adbrix Remaster.

Prerequisites:

Your developer has enabled the deep linking functionality in your app, as instructed in our Developer guide.

Your developer has entered the required information in the AD Landing Settings section of Adbrix Remaster's setup.

You have both enabled event forwarding and created your first campaign, as instructed in our Event Forwarding guide.

1. Locate your App

Log in to your IGAWorks: Adbrix Remaster Account, go to the upper left-hand corner of the navigation menu and select your app by clicking on its logo or the arrow to the right of your app name.

Go to the search field, enter your app name, and click on its corresponding box, as displayed below. Upon completion, click on theSavebutton, located on the bottom of the page.

2. Configure Campaign Settings

Go toAttributions > AD Campaign, located onthe upper left-hand corner of the navigation menu.

You should be able to find a top-level overview of your Remerge campaign, as well as anONstatus next to your postbacks, as per the below example. Should this not be the case, ensure to visit our Event Forwarding page and complete all of the campaign creation steps.

3. Generate your Remerge Tracking Link

Adbrix Remaster's campaign configuration windowconsists of five tabs: Dashboard, Tracking Link,KPI Rule Setting,Postback Final Setting, andFraud Kill-Chain.Click on theTracking Linktab and scroll down.The tab you are located on is always both highlighted and underlined, as displayed below.

A list of integrated partners (networks) will appear under theConnected partnersection. FindRemergeby entering its name inthesearch field, as displayed below. Please note: You should have already enabled Remerge in the earlier setup stages, under the AD Partner Settings tab. Should this not be the case, ensure to complete this step by following the instructions on our Event Forwarding page.

Click on the Remerge logo, to open our configuration window.

Click on the Generate a Tracking Link button, located on the top right-hand corner of the window.

You should find yourself on theTracking Linktab, consisting of the following steps: Define, Configure Options, and Create.

Define

Go to theEnter the name of tracking link field and enter the corresponding name, as per the below example:

Go to theSelect the landing format of tracking linkfield and select theDownload + Deeplink option from the drop-down menu,as displayed below. Upon completion, click on theNextbutton, located on the bottom of the page.

Configure Options

Deep Linking

Adbrix Remaster supports the following two deep linking scenarios:

Ads leading to the same in-app location:

Go to the Deep Link Path Method field, located under the Deep Linking tab, and select the Static path option from the drop-down menu, as displayed below:

Go to the How to use static path field,toggle ON the Android and iOS platforms and select the Default Settingsoption.

Enter the deep link path that takes your user to the exact in-app conversion point. Upon completion, click on the Next button, located on the bottom of the page.

Ads leading to various in-app locations:

Go to the Deep Link Path Method field, located under the Deep Linking tab, and select the Dynamic path option from the drop-down menu, as displayed below:

Go to the How to use dynamic path fieldandtoggle ON the Android and iOS platforms.Upon completion, click on the Next button, located on the bottom of the page.

Ad-Touch Landing

Adbrix Remaster offers a default option, which is automatically activated upon either an unsuccessful deep linking attempt and/or uninstalled app. In both cases, your user is redirected to the digital store of the platform on which your app is located (iOS - Apple AppStore / Android - Google Play).

Go to the Ad-Touch Landing Type field, located under theAd-Touch Landingtab, and select the Static path option from the drop-down menu, as displayed below:

Select theDefault Settingsoption and ensurethe digital store address/addresses are displayed, as per the below example. Should this not be the case, please enter the corresponding address/addresses. Upon completion, click on the Next button, located on the bottom of the page.

Tracking Parameter

Leave the Click and Impression fields empty if you would like to utilize the default parameter setup. In case you would like to customize your parameters, please visit Adbrix's Additional Parameters for Tracking Link page for further information.

Select the ALL option from the drop-down menu of the possible tracking links.Click on the Create button, located on the bottom of the page.

Create

Your Created Click Ad-Touch Tracking Linkand Created Impression Ad-Touch Tracking Link should resemble the below example.

Click on theCopy icon, located to the right of each tracking link, and paste the tracking links in a new browser window or text file for the time being. You will be required to provide the tracking links in the final Share your Remerge Tracking Link & Attribution Windows with Remerge step of this guide.

4. Set Up yourAttribution Windows

Adbrix Remaster's attribution window configuration consists of the following two levels:Partner and Global.

Partner Level

Log in to your IGAWorks: Adbrix Remaster Account, go to the upper left-hand corner of the navigation menu and select your app by clicking on the arrow to the right of your app name.

Go to the search field, enter your app name, and click on its corresponding box, as displayed below. Upon completion, click on theSavebutton, located on the bottom of the page.

Go toAttributions>AD Partner Settings, located onthe upper left-hand corner of the navigation menu.

A list of integrated partners (networks) will appear under theConnected partnersection. FindRemergeby entering its name inthesearch field. Please note: You should have already enabled Remerge in the earlier setup stages, under the AD Partner Settings tab. Should this not be the case, ensure to complete this step by following the instructions on our page.

Adbrix Remaster's configuration window consists of three tabs:AD Partner Information,Postbacks, andAd Touch-Open Attribution.Click on theAd Touch-Open Attributiontab.

Toggle ON the Activate option.

Go to theStatecolumn and ensure to ONLY toggleONtheClick-Identifier(adid/idfa) unit andImpression-Identifier(adid/idfa) unit fields.

Set your Impression Lookback Window to yourView-ThroughAttribution(VTA) value and your Click Lookback Window to yourClick-Through Attribution(CTA) value.Upon completion, click on the Save button, located on the bottom of the page.

Global Level

Go toAttributions> Open Attribution Modeling,located onthe upper left-hand corner of the navigation menu.

Configure your 1-3 Tier settings.Upon completion, click on the Save button, located on the top right-hand corner of the page.

5.Share your Remerge Tracking Link & Attribution Windows with Remerge

Upon completion of the above-mentioned steps and prior to going live, ensure to provide your Remerge Account Manager with the following:

Tracking links (Created Click Ad-TouchTracking Link andCreated ImpressionAd-Touch Tracking Link (if applicable).

Should your ad lead to a variety of in-app locations, provide Remerge with one of the following options:

The path to the exact in-app location (i.e., myapp://store/product/23945few).

The path with a placeholder that Remerge is to replace with the corresponding variable(i.e., myapp://store/product/{id}).

Screenshot of the Attribution Windows:

Partner Level - This screenshot should demonstrate how your Global Level window corresponds with the window you have selected for Remerge (Partner Level). Any alteration to this page requires alteration on our side. Therefore, please ensure to inform your Remerge Account Manager accordingly.

Global Level - This screenshot should display your global settings (Tier 1-3).

Below is our step-by-step guide to activation of event forwarding from IGAWorks: Adbrix Remaster to Remerge. In case of any questions, please reach out to your Remerge Account Manager.

Please note: Successful activation of event forwarding (postbacks) fromIGAWorks: Adbrix Remaster to Remerge is achievedupon the completion of the following two steps:

Postback enablement on the Ad Partner Level.

Postback enablement on the Ad Campaign Level.

1. Locate your App

Log in to your IGAWorks: Adbrix Remaster Account, go to the upper left-hand corner of the navigation menu and select your app by clicking on the arrow to the right of your app name.

Go to the search field, enter your app name, and click on its corresponding box, as displayed below. Upon completion, click on the Save button, located on the bottom of the page.

2. Select & Activate Remerge

Go toAttributions > AD Partner Settings, located onthe upper left-hand corner of the navigation menu.

A list of integrated partners (networks) will appear under theAD Partner Settingssection. FindRemergeby entering its name inthesearch field, as displayed below:

Go to the Is Enabled column and click on the Disabled field to open our configuration window.

Click on the Enablebutton, located on the bottom of the page.

The Enabled status should now appear to the right of the Remerge logo.

3. Configure Event Forwarding

AD Partner Level

The Ad Partner configuration window consists of three tabs: AD Partner Information, Postbacks, and Ad Touch-Open Attribution.Click on thePostbackstab.

ThePostbacktab is divided intoApp Open PostbacksandIn-App Event Postbackssections:

App OpenPostbacks

Go to theState column and ensure to toggle ONNew Install, Re-Install, and Deeplink Option.

Go to thePostback Scope column and selectAllfor all of the attribution types.

In-App EventPostbacks

Go to theState column and ensure to toggle ONall the events you would like Adbrix Remaster to send Remerge, as displayed below.Please note: abx:daily_first_openand Deeplink Open aremandatoryevents, and as such, both should be toggledON.

Go to thePostback Scope column and selectAllfor all of the selected events. Upon completion, click on the Save button, located on the bottom of the page.

AD CampaignLevel

Create your Campaign

Go toAttributions > AD Campaign, located onthe upper left-hand corner of the navigation menu.

Click on the Create a new AD Campaign button, located on the top right-hand corner of the page.

You should find yourself on the Campaign Creation page. Enter yourCampaign Name in its corresponding field, as per the below example. Upon completion, click on the OKbutton, located on the bottom of the page.

Connect your Campaign to Remerge

The AD Campaign configuration windowconsists of five tabs:Dashboard,Tracking Link,KPI Rule Setting,Postback Final Setting, andFraud Kill-Chain.Click on theTracking Linktab and scroll down.

A list of integrated partners (networks) will appear under theConnected partnersection. FindRemergeby entering its name inthesearch field, as displayed below:

Click on theRemergelogo, to open our configuration window.

Go to theIndexsection of Remerge's configuration window, and click on theConnection with AD Campaignbutton, located on the bottom of the page.

Enable Postbacks

Remain on the same page and click on thePostback Final Settingtab, as displayed below:

Go to theState column and ensure to toggle ONall the events you would like Adbrix Remaster to send Remerge, as displayed below.Please note:abx:daily_first_openand Deeplink Open aremandatoryevents, and as such, both should be toggledON. Upon completion, click on the Updatebutton, located on the bottom of the page.

App Open Postbacks

In-App EventPostbacks

Upon completion,go back toAttributions > AD Campaign, located onthe upper left-hand corner of the navigation menu.

You should find an ON status next to your newly configured postbacks, as per the below example:

4.Confirm Setup

Reach out to your Remerge Account Manager to confirm the arrival of events and provide a screenshot of your final settings.

The following guide takes you through the process of historical data transfer from your IGAWorks: Adbrix Original integration to Remerge. In case of any questions, please reach out to your Remerge Account Manager.

1. Locate your App

You should find your app in the search field, located on the top of the page, next to theMenu, as displayed below:

One Time List Upload

2.Download Reports

Log in to your IGAWorks: Adbrix Original Account, and go toAnalytics & Attribution>adbrix Channel-tracking, located on the upper left-hand corner of the main page.

Go to App analytics & Channel Tracking and click onExport Data,locatedon the bottom left-hand corner of the dashboard's navigation.

Click onExport Data > Data List.

Download the New User Data by Channel (ADID/IDFA), Re-install, Re-open(ADID/IDFA)and Paying User Data by Channel(ADID/IDFA)reports, by clicking on the Export button, located to the right of each reporting option.

3.Share your Report with Remerge

Provide Remerge with the downloaded log, which should consist of three files per app.

Please note: You maydelete the channel information from the reports.However,a HIGHER number of device IDsequals aFASTER launch and scalability of your campaign regardless of the time period in which postbacks have been turned ON. Therefore,ensure to provide Remerge with a complete set of the device IDs.

Alternative Solution:

In case you are unable to provide us with the historical data, you may request your Business Intelligence team to create a historical data list on your behalf.For further information on historical data creation as well as file examples, please visit ourpage.

1. URL vs Server

Please provide us with the feed URL, alongside any necessary credentials. The access to your feed can be provided to us via one of the following options:

An external FTP SFTP, HTTP or HTTPS server.

An external S3 bucket. In this case, we need the exact location and password.

Alternatively, we may host your feed on the Remerge Amazon S3 bucket.Upon request, an Amazon S3 bucket and credentials (key and secret access key) will be created for you to upload your feed daily.

Please note:

Feed size should not exceed 40 GB.

The filesshould be compressed with GZIP (*.gz extension).

Authentication:

Please be advised that regardless of the feed's location, the feed *can* (but does not have to) be password-protected.

Remerge also supports IP whitelisting. That being said, Remerge strongly encourages password-protection and prioritizes it over IP whitelisting. This is due to the fact that our IP addresses might change and in that case, we need to contact you with the new IPs to implement the change on your side. The following are Remerge IP addresses for feed whitelisting:

APAC clients:34.87.25.202,35.240.236.35, and 94.75.250.91

EU &America clients:34.77.211.34,34.76.152.90, and 94.75.250.91

2. Speed Requirements

The feed must be available via HTTP/HTTPS or FTP/SFTP at a certain uplink speed:

1mb/s uplink is minimum up to 1GB feed size.

10mb/s or more uplink for 1GB+ feed size.

3. Update Protocol

The feed needs to be updated regularly (e.g., every 24h) and we need to be informed of the exact time & time zone of the update. This is important as the feed needs to match your in-app offerings.

This guide will walk you through generating aKochava Tracking URLthat will run for your marketing activities with Remerge.

1. Select the App

Login to your Kochava account.

Select the App you want to create the Tracking URL for in the top left drop down menu

Clickon “App Tools” and select “Campaign Manager”

2. Create a Reengagement Campaign, Segment and Tracker

Click on“Add a Campaign”, give this new campaign a meaningful name and click “Save”.

Click on “Campaign Tools” and select “Add a Segment” and also here give this new segment ameaningful name and click “Save”.

Click on “SegmentTools” and select “Add a Tracker”.

Give your tracker a name

Select “Reengagement” as Tracker Type.

Select “Remerge” as Network (it will be either Remerge iOS or Remerge Android depending on the selected app)

Enter both Install URL (from the AppStore) and Deeplink-URL (if existing).

Select one or moreAttribution Event(s) that will attribute a user to remerge once generated after the click (Best practice: Select “All”)

Click “Save”

Under Click URL you will find the final link that needs to be shared with your Remerge Account Manager.

3. Click and Impression Lookback Settings

Select the active Remerge Postback, click the right arrow and select “Reconciliation”

Select the correct value for “Device Lookback” (you should have agreed on a value with your Remerge AM).

Impression Reconciliation - NOT AVAILABLE for retargeting

Click Reconciliation (up to 30 days)

You can ignore all the other settings. Remerge does not use fingerprint or ip methodology

Click “Save”.

For confirmation please send a screenshot to your Remerge AM about:

- the Partner Configuration > Reconciliation page

- the Campaign Manager > Overrides page

As you can see it is possible to set the windows in the partners settings as well in the Campaign Overrides section. It is important to send Remerge both so Remerge can be sure to select the correct windows for you in the Remerge Campaigns.

From now on, AppsFlyer also offers the View-Through Attribution (VTA) method to its clients. Below is our step-by-step guide to activation of View-Through Attribution with AppsFlyer. Please note: This guide applies to clients that are already running a Click-Through Attribution (CTA) campaign with AppsFlyer. In case of any questions, please reach out to your Remerge Account Manager.

1. Enable In-App Retargeting

Log in to your AppsFlyer Account andselect your app.

Click onApp Settingsand toggleONEnable Re-Targeting Campaign Measurement,located on the bottom of the page.

iOS Tracker Generation

2. Locate & Activate Remerge

Go to thenavigation menu, located on the left-hand corner of the dashboard, scroll down toConfigurationand select Integrated Partners.

FindRemergeby entering itin the search field and click on itslogoto open ourconfigurationwindow, as displayed below:

Toggle ONActivate Partner. Please note:Each partner integration (advertisers & agencies) requires an initial manual activation.The Activate Partner toggle MUSTremain ONat ALL TIMES.

3. Enable View-Through Attribution

Remain on theIntegrationtab, scroll down to Re-engagement attribution and toggle ON Re-engagement view-through attribution, as displayed below:

4.Generate your Remerge Impression Attribution Link

Click on the AttributionLinktab, as displayed below:

Set up Retargeting - Enable retargeting by togglingON Retargeting Settings,as shown below.Once retargeting is enabled, AppsFlyer will automatically add theis_retargeting=truetracking parameter to the target URL. Your Remerge link is now a Retargeting Attribution Link.

Configure the view-through attribution deep link by selecting theUse a standard tracking linkoption.

No need to add deep linking information - InView-ThroughAttributioncampaigns, the Deep Link URL box may remain empty (InClick-Through Attributioncampaigns, ensure to add deep linking information. For step-by-step instructions, please visit our Android Tracker Generation andpages).

Select your View-Through Lookback Window,as displayed below and reenter yourRe-engagement window. Please note: TheRe-engagement window you select for theView-ThroughAttributionmethodMUSTMATCHthepreviously configured window for theClick-ThroughAttribution method.

Review your newly generated impression tracking link URL and ensure it includes the below parameters:

&af_viewthrough_lookback=1d

&is_retargeting=true

&af_reengagement_window=30d

The following can be viewed as an example of the final version of your Remerge impression tracking link URL:

5. Share your Remerge Attribution Link with Remerge

Copy your newly generated impression tracking link URL from the bottom section of the attribution link generator upon completion of the above-mentioned steps, and provide your Remerge Account Manager with the link.

Dynamic Adsare ads based on and customized to a user's journey within a specific app. These ads are created in real-time by filling an ad template with images and product information from a regularly updated (product)Feed. The feed is a list of all client offerings and details on each product.

For each client, Remerge prepares a uniqueAd Template,filled with product details taken directly from their feed. Clients are then able to review the template and see what their potential users should see upon an ad display.

Remerge has the capability to run Dynamic Ads as HTML banners. Additionally, we employ the Native traffic format, which in turn allows the best use of all existing mobile traffic.No additional work is required from your side for theNative format.

How does it work?

1. Event Forwarding

We collect information about how products are viewed/used from the in-app events, forwarded to us by your attribution provider or your internal BI system.

Once you activate the event stream on your attribution provider's dashboard, we automatically receive both the events and attributes associated with said events from your attribution provider.The event attribute is a piece of additional information concerning a specific event. Let us look at the following example:

If an event is: User Views a Product, then a possible attribute to that particular event could beProduct ID. This Product ID specifies the product viewed by the user. Among the various attributes that could be describing this event, there needs to be one unique attribute that can also be found inyour feed. In our specific example, the unique attribute would be Product ID, and it should be found both in the event attributes andproduct feed.

2. We use that knowledge to create engaging and relevant ads (Dynamic Ads)

Based on the knowledge we have accumulated from the in-app events, we select items from the product feed.We then utilize these items to create a custom HTML ad for each unique user (impression)inreal-time. This ensures that we ONLY showyour usersrelevant and individualized content.

3. Deep LinkingWe bring users back to your app!

Once users click on any of the products displayed in the custom ad, they aredeep linked to the specific page of the product they clicked on earlier.In order to ensure a smooth user experience, we need to test both your deep links and tracking links ahead of time.

The following guide takes you through the process of configuringyour app to handledeep linking. By using deep links,Remergeis able tosend aretargeted user directly to the app landing page of your choice. In case of any questions, please reach out to your Remerge Account Manager.

iOS Deep Link Settings

In order to register a URL scheme, ensure to define it in your app’s information plist file.

In Xcode, open your app information plist file

Add a “URL types” entry:

Expand the “URL type” row.

Expand the “Item 0 row.

Add a new row.

For “URL identifier”, add value as the unique identifier for your app.Try to choose a unique identifier which is unlikely to be used by other apps.

Right-click the “URL identifier”:

Select Add Row.

Select “URL Schemes”.

Set the “Item 0 value to your unique scheme.

Testing & Verification

Run the app on your device or the iPhone simulator.

Open Safari and enter a URL that starts with your unique scheme.For example, myapp://anything.

Thisshould causeyour device to exitSafari and get redirected to your app.

For further information, please visit the Implementing Custom URL schemessection in App Programming Guide for iOS.

Android Deep Link Settings

In order to register a URL scheme, ensure to add an intent filter in your app's manifest.

In your app’s manifest, add the following intent-filterto your relevant activity:

<intentfilter>

<action android:name=”android.intent.action.VIEW” />

<category android:name=”android.intent.category.DEFAULT” />

<category android:name=”android.intent.category.BROWSABLE” />

<data android:scheme=”your unique scheme” />

</intentfilter>

Example:

<activity android:label=”@string/app_name” .. >

<intentfilter >

<action android:name=”android.intent.action.MAIN” />

<category android:name=”android.intent.category.LAUNCHER” />

</intentfilter>

<intentfilter>

<action android:name=”android.intent.action.VIEW” />

<category android:name=”android.intent.category.DEFAULT” />

<category android:name=”android.intent.category.BROWSABLE” />

<data android:scheme=”myscheme” />

</intentfilter>

</activity>

Testing & Verification

Run the app on your device.

Open your default browserand enter a URL that starts with your unique scheme.For example, myapp://anything.

Thisshould causeyour device to leavethe browserand get redirected to your app.

Below is our step-by-step guide to obtaining data from the Remerge Reporting API. For further insights, we also encourage you to visit our Remerge Reporting API page. In case of any questions, please reach out to your Remerge Account Manager.

1. Locate Remerge

Log in to your Singular Account, click onSettings >Data Sources, located on the left-hand corner of the dashboard's menu, andfindRemergeby entering itin theData Sourcessearch field, as displayed below:

2.Enter Remerge Credentials

Click onRemerge,the correspondingEditbutton, located on the right-hand corner of the page andenter the Remerge dashboard login information provided by your Remerge Account Manager (Reach out to your Remerge Account Manager in case you have yet to obtain said credentials).

Click on theSavebutton upon completion.

The Singular Dashboard runs API requests on the Date and Campaign dimensions.

Listed below is the information we kindly ask you to provide us with in order to create your custom ad template.

Please note: We implementGoogle Web-safefonts in our creatives.

CTAandCurrencyper language feed. (e.g.,Shop now and$ can be your tags for the English feed, for the German feed,JetztKaufen, and)

Logo&Brand Guideline(when available).

Product Unique Information(e.g., eco-friendly, certificate unique to your product, free delivery, etc.). Any additional information that is expected to be changed per product or overtime must be part of a column in the feed.

A Templateof your choice from the below options:

T1A

T1B

T2A

T2C

T3

T4

T6

T8

T12

Listed below is the information we kindly ask you to provide us with in order to create your custom ad template.

Please note: We implementGoogle Web-safefonts in our creatives.

CTAandCurrencyper language feed. (e.g.,Shop now and$ can be your tags for the English feed, for the German feed,JetztKaufen, and)

Logo&Brand Guideline(when available).

Product Unique Information(e.g., eco-friendly, certificate unique to your product, free delivery, etc.). Any additional information that is expected to be changed per product or overtime must be part of a column in the feed.

A Templateof your choice from the below options:

T1A

T1B

T2A

T2C

T3

T4

T6

T8

T12

Listed below is the information we kindly ask you to provide us with in order to create your custom ad template.

Please note: We implementGoogle Web-safefonts in our creatives.

CTAandCurrencyper language feed. (e.g.,Shop now and$ can be your tags for the English feed, for the German feed,JetztKaufen, and)

Logo&Brand Guideline(when available).

Product Unique Information(e.g., eco-friendly, certificate unique to your product, free delivery, etc.). Any additional information that is expected to be changed per product or overtime must be part of a column in the feed.

A Templateof your choice from the below options:

T1A

T1B

T2A

T2C

T3

T4

T6

T8

T12

Event attributes* provide additional insight, which Remerge later utilizes for the purpose of retargeting.These attributes are implemented during a standard SDK integration with your attribution provider. This means that once you toggle Event Forwarding on your attribution provider's dashboard, said attributes are automatically sent to Remerge.

In-depth guides on event attribute implementation with the various attribution providers can be found here:

AppsFlyer**

Adjust/iOS

Adjust/Android

Singular/iOS ***

Singular/Android ***

Branch Track Events and Custom Events with Properties

Kochava

* Naming convention is subjected to partner's preferences (also known as "rich in-app events", or "events with arguments").

**Recently, there has been an incident, in which a client needed to toggle the [x] "Send Revenue" button in order for the rich event data to be sent to Remerge. In case you are sending any rich event data that is not visible to your Remerge Account Manager, we kindly ask you to togglethe [x] "Send Revenue" button. AppsFlyer has been notified.

*** Singular's setup requires you to reach out to Singular's support team, as they need to alter Remerge's callback template in order to include the attributes in the callback.

Please adhere to the below feed image guidelines:

1. Consistency

Consistency in the way your product pictures are taken(e.g., retail products on a white background, houses in daylight, food in close-up, and same format pictures).

2. Frames

Focus on the product and refrain from using black/white spaces or frames around the photo.

3. Size

Product images in the feed should not surpass300KB each.Lighter images decrease the loading time.

prohibited content

5 MB

250 KB

Preferred sizes: Between480x480px&700x700px.

Please note: We support image resize API.

1350x1254px

600x600px

5. SSL

Image path MUST support HTTPS (in case a link starts with HTTP, please check in the browser whether the said link works with HTTPS).

6. Prohibited Content

Refrain from utilizing any content or pictures that resemble the ones mentioned in thelist. Let us know if you have an extra column (e.g., adult, alcohol) that can help us filter out this data. Otherwise, Remerge employs a keyword search list to blacklist the content.

Below is an overview of the five feasibility and setup aspects you should consider before starting to run Dynamic Ads.

1. Event Forwarding

The first prerequisite to running Dynamic Ads is us receiving your in-app events, which you can achieve by utilizing the services of an attribution provider. You can read more about event forwarding through different attribution providers by visiting our Partner Integration Guides page.

2. Feed URL

Access to your product feed via a URL.

Time and timezone of the feed's daily update.

Please note: We use a list of keywords to blacklist any prohibited content from the feed. Ideally, we prefer that you exclude said content from the feed as soon as possible.

3. Deep Links

Please confirm internally that your app contains deep links in general and universal links for iOS. You may either create universal links internally or leverage an attribution provider with whom you have implemented universal links for iOS.

Example of a raw deep link path foriOS and Android: myapp://store/view/{product_id}.

Example for iOS UL: https://seatgeek.com/e/events/4551512

Please note:

Universal links require deep links to function.

In order to ensure a smooth deep linking process, we need to be able to test your links. Please make sure to provide us with the links at your earliest convenience.

4. iOS & Android Trackers

Apart from deep links, we also need the click and (if possible) impression trackers from your attribution provider. You can read more about the tracker generation by visiting our Partner Integration Guides page.

5. Preferred Ad Template

We kindly ask you to provide us with your logo and creative guidelines as well as an Ad Template that fits your vertical and offerings.We then create a personalized Ad Template for you, which you can review before going live.

Please note: We implement Google Web-safe fonts in our creatives. For more information on Google-web-safe fonts please visit https://fonts.google.com/.

The following isa Food & Drink Feed Example alongside clarifications of the mentioned content.

Please note: Multiple column options are possible and as such, we do encourage you to check internally and decide on the columns (information you choose to include in your feed) that serve your business needs best. In case of an already existing feed, we kindly ask that you provide us with it for an initial review.

id

restaurant name

city

image_link

deep_link_ios

deep_link_and

cuisine

price

rating

2352cb

Dim Sum and More

Berlin

https://...

myapp://restaurant/view/34fx5

myapp://

Chinese

320.00

5

1ik167

Pasta Extraordinaire

Naples

https://...

myapp://imbiss/sale/55cghm

myapp://

Italian

280.00

5

#ID-A minimum of oneuniqueIDcolumn is required. The unique ID is usually the Vendor ID or Restaurant ID. Remerge Solution Engineers use this column to match it to the event attributes data.The ID must only contain ASCII characters and cannot contain quotation marks.

# City- The location of your app's restaurant and thus user base relevant to the location.

#Image Link -URL of the image to be displayed in the ads (*.jpg, *.jpeg, *.png formats).All symbols must be encoded. For example,"?" needs to be replaced with "\%3F" and & with "\%26". This is true for all non-ASCII characters such as non-English letters.

#Deep Link(iOS & Android)- Deep-link to each offer.

If the campaign is targeting iOS and Android, OS-specific deep link columns are preferred.

If a certain changing part in a deep link can be found in one of the feed's columns, a designated deep link column is not needed and instead, you can simply notify your Remerge Account Manager of your custom deep link path together with your attribution provider trackers.

Please note: For iOS, a Universal Link path to each product will be needed.

#Price- Original price in decimal numbers.

#Rating- A number between 1-5.

# Category- The same restaurant categories should be used consistently within the feed.

# Any additional information, which can enrich the banners.

Food_Feed_Example.csv

One of the first action steps you should take to start runningDynamic Ads with Remerge is:TurnONEvent Forwardingto Remergeonyour attribution provider's platform. Read more about Event Forwarding here.

Below is the preferred list of in-app events and attributes Remerge should receive from your app, alongside clarifications of the mentioned content. Read more about addingAttributes to your Events per attribution provider here.

Please note: The naming convention of an event or its attribute may vary and is subjected to partner's preferences. Therefore, the following should only be viewed as an example of Event Types(not necessarily the actual names) associated with the Food& Drink vertical:

Event Type

Attribute

Send Revenue?

App Opened by User

City/Area

Vendor List Viewed by User

Vendor IDs, City/Area

Specific Vendor Viewed by User

Vendor ID, City

Added to Cartby User

Vendor ID, City

Order Purchasedby User

Vendor ID, City

yes

#Event Type- This is the preferredlist of event types and attributes essential to go live. That being said, you may, of course, send us more events and even more attributes.

# Attribute- Remerge Solution Engineers check if the Item IDs in your event attributes (can be named: ID, Vendor ID, City ID or other) match the Item IDs in one of the columns in your feed. Althoughatthe very least, we need one attribute to be identical to the ID in your feed, we do nevertheless encourage you to share any additional data you see fit.Common attribute examples:

City ID- Any location-oriented data can be defined by you as best suits your business needs. Therefore, the name could also be for instance: City ID, City Name, Area ID or Zip Code. The only prerequisite is that it should match the data in one of your feed's columns.

Vendor ID-Can, also be a Restaurant ID, as long as a match is achievable.

# Revenue- Most attribution providers let you decide on a per-event basis, whether or not to also forward Remerge the in-app revenues. In case information regarding revenues is available, please ensure to enable it for the final OrderPurchased event.

#OrderPurchased- Can also be called, e.g., Order Complete, Order ID or other.

The following isanEntertainment &Media Feed Examplealongside clarifications of the mentioned content.

Please note: Multiple column options are possible and as such, we do encourage you to check internally and decide on the columns (information you choose to include in your feed) that serve your business needs best. In case of an already existing feed, we kindly ask that you provide us with it for an initial review.

id

title

description

location

image_link

deep_link

category

price

sales_price

sale

34fx5hj

Best of Rock Vocalists

"Amazing Show, Get Tickets Now!"

Paris

https://...

myapp://product/view/34fx5

Music

500.00

350.00

30

55cghm

The Dance Fusion Experience

"Best Show Ever!"

Amsterdam

https://...

myapp://store/sale/55cghm

Dance

550.00

220.00

60

#ID-A minimum of oneuniqueIDcolumn is required. The unique ID is usually a Product ID, Item ID, Item Code or Content ID. Remerge Solution Engineers use this column to match it to the event attributes data.The ID must only contain ASCII characters and cannot contain quotation marks.

#Title- Product name.

#Description- Brief product description.

#Image Link- URL of the image to be displayed in the ads (*.jpg, *.jpeg, *.png formats).All symbols must be encoded. For example,"?" needs to be replaced with "\%3F" and & with "\%26". This is true for all non-ASCII characters such as non-English letters.

#Deep Link(iOS & Android)- Deep-link to each offer.

If the campaign is targeting iOS and Android, OS-specific deep link columns are preferred.

If a certain changing part in a deep link can be found in one of the feed's columns, a designated deep link column is not needed and instead, you can simply notify your Remerge Account Manager of your custom deep link path together with your attribution provider trackers.

Please note: For iOS, aUniversal Linkpath to each product will be needed.

#Category- Product category.

#Price- Original price in decimal numbers.

#Sales Price- Promotion/sale price in decimal numbers.

#Sale- The difference between the original price and reduced price in percentage.

#Any other information (such as rating or in-stock), which can enrich the banners.

Entertainment_Feed_Example.csv

Braze is able to define a segment of users you may send to Remerge via Webhooks. Below is our step-by-step guide to activation of event forwarding from Braze to Remerge. In case of any questions, please reach out to your Remerge Account Manager.

Pre-Setup

Braze Does Not automatically collect the device IDs (Google Advertising ID & IDFA) on your behalf. Therefore, ensure to collect and provide us with the device IDs. We kindly ask that you start device ID collection early and ideally at the very least several weeks prior to running with Remerge.

Webhook Setup

Fill in a webhook template with the following credentials and review the below screenshot example of successful implementation:

Event name -Givethe segmented audience an Event Name, which we later utilize in campaigns.

Unique Application Identifier(Android & iOS). Examples:

# App Store - e.g., 911793120

# Google Play - e.g., com.gramgames.tenten

Remerge Event API Key - Please contact your Remerge Account Manager to receive yourRemerge Event API Key.

Uppercased Apple IDFA (Braze's default format), e.g., DBC04712-89D2-4447-9855-559E49ACF8D7.

LowercasedAndroid Google Advertising ID, which you can achieve by employing the|downcasemethod in the webhook template, e.g., 10059fa8-870f-4da9-8183-1b428e92a25e.

How to set up Webhooks in Braze for Remerge

Support & Confirmation

Upon sending the webhooks to Remerge, reach out to your Remerge Account Manager to confirm the arrival of segments.For more in-depth instructions please see.

mParticle is a Customer Data Platform (CDP), providing Remerge with the relevant user base and event data. Remerge requires confirmation of an app open to measure campaign performance. In certain scenarios (and depending on campaign goals), both app open and conversion events are necessary to assess the effectiveness of a marketing campaign.

Below is our step-by-step guide to activation of audience forwarding from mParticle to Remerge.

Please note:Audience forwarding is possible both whether you have integratedmPartical's SDK in your app or not, in which case, you are utilizing mPartical's data warehouse without their SDK. That being said, if you have in fact integrated mPartical's SDK in your app, please followthe instructions on our Event Forwarding page. In case of any questions, please reach out to your Remerge Account Manager.

Build Audiences

1. Capture Data & Define Use Cases

mPartical's Audience Manager enablesaudiences definition from any user-associated data captured with mParticle, as well as the assessment of segmentation and engagement strategies. In order to achieve both goals, please follow the step-by-step instructions on mParticle's Capture Data and Define Use Case guides.

2. Create Audiences

Log in to your mParticleAccount and click onAUDIENCES, located on the lower left-hand corner of the menu.

Select your workspace from theSingle/Multi Workspacetabs and click onNew Audience,located on the upper right-hand corner of the page.

Audience Sharing

3. Name your Audiences

Enter yourAudience NameandExternal Name. External Nameis an optional field, which is intended to be utilized for potential Audience Sharing.

Go to Inputs,check the boxes next to the platforms and feeds you would like to utilize for audience definition, click onCreate, and defineyour audience by following the instructions on mPartical's Audience Criteria Specification page.

Setup Audience Output

1.Initiate Setup

Click onDIRECTORY, located on the lower left-hand corner of the menu, and find Remerge from the search bar located underConnect your data anywhere.

2.Activate Remerge

Select Remerge as your media partner byclicking on+ Add Remerge to Setup, as displayed below:

3. Select Integration Type

Go toChoose an Integration Typeand click onOUTPUT (AUDIENCE)>Send user lists to Remerge from mParticle>Add to Setup, as displayed below:

4. Complete Configuration Settings

Give your configuration a name by entering it in theConfiguration Namebox.

Enter the below-mentioned Remerge authentication protocols in their corresponding boxes, if you have yet to do so:

Remerge API Key(Provided byyour Remerge Account Manager)

Remerge Customer ID(AppStore ID/Package Name, such as 553834731 and Google Play Store App ID, such as com.king.candycrush)

Upon completion click onSaveand find your final result under theAUDIENCE CONFIGURATIONStab, as displayed below:

5. Establish Audience Connection

Go toAUDIENCES, located on the lower left-hand corner of the menu and select the audience which you have created in the earlier stages of the setup. In our specific example, the audience isTest Audience for Remerge.

Click on theCONNECTtab >+ Connect Output,as displayed below:

Select Remerge and click onNext, located on the bottom right-hand corner of the page.

Go to ConfigurationNameandselect your configuration from the drop-down menu.

Ensure the Statusswitch is set toSendingand click on Add Connection.TheNextbutton switches to theAdd Connectionbuttonupon selecting the configuration.

From this point on:

mPartical is streaming audience data to Remerge and any users that fit your audience criteria will become available in the output platform.

Individual change requests in the form of added/removed users are to be expected, as said requests are based on audiencein-app behavior and users' level of engagement.

In case you wish to send Remerge a large number of audiences, you may establish a Bulk Audience Connection and by doing so, send multiple audiences at once, as follows:

Click onSETUP> Outputs>Audience Configurations.

SelectConnect Audienceslocated next to the relevant audience configuration.

Select the audiences and click onNext, as displayed below:

Choose your settings and click onConnect. Upon completion, a status message showing all successful audience connections should appear.

Ensure to review mParticle's Documentation for potential updates, as well as further information on Audience Data Format, Audience A/B Testing, Downloading Audiences, and.

6.Confirm Setup

Reach out to your Remerge Account Manager to confirm the arrival of audiences.

1. File Format

Remerge supports a variety of formats and as such the feed can be anXML, CSV or TSV file.

Please note:

Feed size should not exceed 40 GB.

The filesshould be compressed with GZIP (*.gz extension).

CSV file - Column delimiter should be a comma.

TSV file - Column delimiter should be a tab.

Please note: Remerge does not support an API feed.

API Feed Support

XML, CSV or TSV

2. Encoding

Unicode (UTF-8) should be used as a character set.

euc-kr,gb2312

utf8

3. Obligatory Header

The file must contain a header with column names.

34fx5

"Amazing Sofa"

"Awesome Sofa, Get it Now!"

https://...

myapp://product/view/34fx5

id

title

description

image_url

deep_link

34fx5

"Amazing Sofa"

"Awesome Sofa, Get it Now!"

https://...

myapp://product/view/34fx5

Below Header Requirements:

Column names should be alphanumeric and begin with an alphabetic character.

345

description

Column names can be written in a camel or snake case format.

amazing table

amazing_table

Amazing Table

AmazingTable

Column names should not contain spaces or any other special characters.

Amazing Table

AmazingTable

4. Consistency in Number of Columns

Each row must contain the same number of columns.

Please note: Although the number of columns should be identical, some columns may be empty of content.

id

title

description

image_url

deep_link

category

sales_price

34fx5

"Amazing Sofa"

"Awesome Sofa, Get it Now!"

https://...

myapp://product/view/34fx5

"Sofa"

3209.00

45fx8

"Awesome Sofa, Get it Now!"

https://...

myapp://product/view/34fx5

"Sofa"

3209.00

id

title

description

image_url

deep_link

category

price

sales_price

34fx5

"Amazing Sofa"

"Awesome Sofa, Get it Now!"

https://...

myapp://product/view/34fx5

"Sofa"

5500.00

3209.00

45fx8

"Awesome Sofa, Get it Now!"

https://...

myapp://product/view/34fx5

"Sofa"

5500.00

3209.00

5. Quoted Fields

Fields can be quoted in double-quotes only. Example:

'Amazing Table'

"Amazing Table"

6. Quotes in Quotation Marks

Fields containing a comma (in case of comma-separated files) or quotes, must be quoted with double quotation marks.Example:

Say hi to your new table.

""Say "hi" to your new table.""

The following document provides you with insight into the type of placeholders you may add to your Click and Impression Template URL.Please note:While some placeholders can be viewed as optional, the device_id_raw is a mandatory placeholder,and as such, it must be part of the template URL.

Content

Example

Placeholder

Campaign Name

remerge_i_o_s

{external_campaign_name_raw} *Capital letters should be separated by an underscore.

Campaign ID

235266

{campaign}

Creative Name

creative_banner_320_50.png

{ad_name} This is the file name

Creative ID

34688

{ad} or {creative}

Google Advertiser ID/

Apple IDFA

10059fa8-870f-4da9-8183-1b428e92a25e /

DBC04712-89D2-4447-9855-559E49ACF8D7

{device_id_raw}

Country

de

{country}

Partner

mopub23

{partner}

Publisher

for iOS:911793120

for Android: com.gramgames.tenten

{publisher}

Click ID

(Unique to the impression slot offered by the RTB Ecosystem)

wCvxiqsvjH34EUCD

{click_id} or {clickid}

New! Creative Set (In case you are running two sets of static banners, you are able to see which one was displayed. You may inform your Account Manager of the naming of the sets.)

set_1, set_2, christmas_2017

{{Ad.Label.Name.Encode}}

User-Agent and IP Address

For Client-Side Click URL - you will receive theUser-Agent and IP Address directly from the user's device.

For Server-Side Click & Impression Forwarding - Remerge forwards the User-Agent header and the originating IP Address in the X-Forwarded-For header of the S2S Url. (Remerge does not have separate macros for User-Agent and IP Address).

Cost Macros

Content

Example

Placeholder

cost_type

cpc

cpc

amount

0.23

{{Campaign.BuyingPriceAsMoney.Float32"USD"}}

currency

usd,eur

usd

Introduction

Remerge is an app retargeting platform. Partners and clients can forward events/segments to the remerge tracking API in real time. Remerge will create segments of users that should be targeted/excluded for a campaign in real time using the information from the forwarded events/segments.

Endpoint

https://remerge.events/event

Encryption Method

HTTPS

Request

For every event a GET should be send to one of the given endpoints including the following parameters (in the query string). If the request was successful the API responds withHTTP 204.

Parameters

All mandatory parameters (marked with aM) must be provided to allow proper tracking. Optional parameters can be set to improve retargeting and reporting. Parameters which contain characters which are not web safe have to be encoded properly.

name

content

examples

app_id (M)

iTunes or Google Play Store App ID

553834731, com.king.candycrush

event (M)

name of the event

purchase, add_to_basket, level_2_reached

data

additional data for the event, please put in JSON format (a single string is also acceptable)

{"store":1341, "keywords":["yellow","red"]}

ts (M)

event timestamp as unix epoch, timezone should be UTC and it should be ten digits long

1427976389

partner (M)

name of the tracking partner

supergame

key (M)

key of the partner (provided by remerge)

x34dlx

idfa (M)

Apple IDFA (uppercase) (if a aaid was provided not mandatory)

AEBE52E7-03EE-455A-B3C4-E57283966239

aaid (M)

Android Advertising ID (lowercase) (if a idfa was provided not mandatory)

38400000-8cf0-11bd-b23e-10b96e40000d

country (M)

ISO alpha 2 country code

DE

device_name

Device name

iPad

os_name (M)

OS name

android, ios

os_version (M)

OS version

8.0.1

app_version (M)

App version

1.2

user

customer user id

4838131

revenue

revenue in micro currency units (allows sub cent values and avoids float issues)

revenue=170000 (=0.17), 5750000 (=5.75$)

(revenue_float )

in case your prices are without sub cent values and a decimal separator

revenue_float=49000 (49000)

currency

ISO 4217 currency code

USD

network

if the event is attributes to a partner, the networks name or id

remerge,facebook,organic

click_id

pass through parameter for the unique ad click id (usually appended to a click tracking url by remerge).

iwShT9ec49

non_app_event

if the event is not created by the app (i.e. a click post back) - true or false

false,true

is_attributed

definition whether an event is attributed to remerge or other sources

1 (= remerge) or 0 (=organic or other mediasource)

partner_attribution_method

definition whether an event is attributed to a view or a click

click,view (or empty)

Example

Example with placeholders (whereas {PLACEHOLDER} should be the name of your internal placeholder)

https://remerge.events/event?app_id={PLACEHOLDER}&event={PLACEHOLDER}&partner=yourname&key=yourkey&idfa={PLACEHOLDER}&aaid={PLACEHOLDER}&country={PLACEHOLDER}&device_name={PLACEHOLDER}&os_name={PLACEHOLDER}&os_version={PLACEHOLDER}&ts={PLACEHOLDER}&revenue={PLACEHOLDER}&currency={PLACEHOLDER}&non_app_event=false&is_attributed={PLACEHOLDER}

An example for an purchase event attributed to remerge based on click

...&event=purchase&is_attributed=1&network=remerge&partner_attribution_method=click

An example for an unattributed purchase event:

...&event=purchase&is_attributed=0&network=organic or

...&event=purchase&is_attributed=0&network=mediaB&partner_attribution_method=view

Data

The data parameter can hold a number of unique key value pairs in JSON format. This can be used to send additional meta data about the user action as part of the event itself. As an example in e-Commerce it is often used to send product related information, e.g. product ids, prices, quantity ect., which can be used to show and lookup further relevant products in customized banners from a product feed.

The JSON data structure might look like this:

data={"product_id":"sdf235235dfw3131","cv_type":0}

It needs to be send URL encoded to remerge:

data=\%7B\%22product_id\%22\%3A\%22sdf235235dfw3131\%22\%2C\%22cv_type\%22\%3A0\%7D\%20

If you need to send us multiple product ids, you can do it like this:

data={"products":["23ef23","234fe2d","23dw334"]}and encoded is

data=\%7B\%22products\%22\%3A\%5B\%2223ef23\%22\%2C\%22234fe2d\%22\%2C\%2223dw334\%22\%5D\%7D\%C2\%A0

or

data={"products": [{"item_id":"3343er","other":234},{"item_id":"gt34rt3","other":457},{"item_id":"g334h","other":635}]}and encoded is

data=\%7B\%22products\%22\%3A\%20\%5B\%7B\%22item_id\%22\%3A\%223343er\%22\%2C\%22other\%22\%3A234\%7D\%2C\%7B\%22item_id\%22\%3A\%22gt34rt3\%22\%2C\%22other\%22\%3A457\%7D\%2C\%7B\%22item_id\%22\%3A\%22g334h\%22\%2C\%22other\%22\%3A635\%7D\%5D\%7D

De-duplicate clicks

Remerge will always only count one click per bid request. Even if in the UI the user clicks several times or refreshes the page and the click url is sent out again, for remerge it will just count as one click. Use click_id if you want to de-duplicate the clicks.

Non_App_Events

When the flag is set to false, Remerge can use the events for:

- real time segmentation with the intent of targeting (e.g. target only certain users for a campaign)

- performance measurement and attribution (e.g. check if the purchase event is attributed to remerge or not, if after a click followed an app open etc.)

When the flag is set to true, Remerge can use the event for:

- real time segmentation with the intent of targeting (e.g. target only certain users for a campaign)

When set to true Remerge will not at all use the event for campaign performance measurement and attribution but purely for campaign targeting rules.

Sending Segments via the real time tracking api

You can update us in real-time if a user is inside/outside a segment by flagging active:true (inside the segment) or active:false (left the segment). Then remerge has the updated segment information in real time. Since you are sending a segment and not a user event, please have non_app_event set to true

User entered a segment:{"active":true}

https://remerge.events/event?app_id={PLACEHOLDER_IOS}&event=segment_XYZ&partner=yourname&key=yourkey&idfa=EB3E8776-318F-446F-A7AF-D74599AFAE60&os_name=ios&non_app_event=true&data=\%7B\%22active\%22\%3Atrue\%7D

User left a segment:{"active":false}

https://remerge.events/event?app_id={PLACEHOLDER_Android}&event=segment_XYZ&partner=yourname&key=yourkey&aaid=0e5160b7-e944-491e-9a3e-d9a8376f08cd&os_name=android&non_app_event=true&data=\%7B\%22active\%22\%3Afalse\%7D

Please note:

You need to let us know in advance the name of the event before you start sending the event. The name of the event needs to start with segment_XXX and then filled in with your individual codename for the segment.

The real time event tracking api cannot be used for sending Remerge a list of users only once or twice a day. The purpose of this tracking api is to update Remerge in real time about a user event or segment. Please talk to your Remerge Account Manager in case you need to send lists.

Attribution Time Window for the Click (CTA):

Please let us know if your click time attribution time window is from

Click ToEventAttribution Window or

Click ToReengagement Window

Reengagement being the first postback event received after a click (usually this would be an App Launch but any first postback counts). It triggers the Life Time Value KPI, view it below.

Attribution Time Window for the Impression (VTA):

For impression attribution time window, remerge offers either:

View To EventAttribution Window

View To Reengagement Window

time windows.

Reengagement being the first postback event received after a click (usually this would be an App Launch). It triggers the Life Time Value KPI, view below.

Life Time Value Attribution Window (Post Re-Engagement Attribution Window):

Once the View to Reengagement or Click to Re-engagement window has been triggered Remerge will count all following attributes of that user for the length of the life time value attribution window.

It is called:

Post Reengagement Attribution Window

Below is an overview of the type of events and file examples you may send Remerge as part of the one-time historical data report. Please ensure to share these guidelines with your Business Intelligence Team for the purpose of raw data report creation.

1. Create your Reports

Please define which events you wish to provide us with and create a single file per OS and event. The following are potential file examples:

android_purchasers.csv

ios_purchasers.csv

android_launches.csv

ios_launches.csv

Each of these files should contain the IDFA/Google Ad ID as well as the last timestamp of their last launch/purchase with a header. The following are examples ofpotential ios_purchasers.csv and android_purchasers.csv files:

iOS example file:

ts,device_id

2018-02-22T15:50:02Z,19909C56-B84D-4BA7-8092-8C2BF0BB4A81

2018-02-22T13:36:03Z,D998FEA1-E422-4A02-B330-D220116297B6

2018-02-23T12:32:05Z,C5D6188A-4BCB-4AFB-B434-8AD0DD665C4A

Android example file:

ts,device_id

2018-02-22T15:50:02Z,b9c7fa46-c1cc-4e02-9c90-5f94b3498df1

2018-02-22T13:36:03Z,3b6b0c50-13b0-4dc2-95b9-bdbb1f1fe022

2018-02-23T12:32:05Z,e1e33e32-4396-421b-9606-ddcc1609f0b8

Timestamp: A list of IDs usually suffices and there is no need in a timestamp. In case you would like to provide us with a timestamp, please ensure to do so in a coma separated CVS file.

The timestamp can be in any format that the ruby parse method can handle: https://ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/DateTime.html#method-c-parse

A common format is ISO 8601 => “2018-01-08T13:42:57+01:00”

2. Forward the Reports:

Please forward the reports to your Remerge AccountManager.

Remerge supports Events Forwarding for both:

real-time events

batch transfer of Adobe Audience Manager Segments

Process:

Ask Adobe to activate a server-to-server "Destination" that is specific to your platform. This can only be done by an Adobe representative.

Please send Remerge your Destination ID. Remerge will need to insert the Destination ID into the Remerge platform.

Once Remerge confirms this is done, start sending over your events or AAM Segments.

Please note:

The mobile SDK implementation should be referencing the Global DPIDs mentioned below.

The User ID key must be set to one of the following Global DPIDs :

Apple IDFA (ID for Advertisers) (20915)

Google Ad ID (GAID) (20914)

Listed below is the information we kindly ask you to provide us with in order to create your custom ad template.

Please note: We implementGoogle Web-safefonts in our creatives.

CTAandCurrencyper language feed. (e.g.,Shop now and$ can be your tags for the English feed, for the German feed,JetztKaufen, and)

Logo&Brand Guideline(when available).

Product Unique Information(e.g., eco-friendly, certificate unique to your product, free delivery, etc.). Any additional information that is expected to be changed per product or overtime must be part of a column in the feed.

A Templateof your choice from the below options:

T1A

T1B

T2A

T2B

T2C

T3

T4

T6

T8

T12

Listed below is the information we kindly ask you to provide us with in order to create your custom ad template.

Please note: We implementGoogle Web-safefonts in our creatives.

CTAandCurrencyper language feed. (e.g.,Shop now and$ can be your tags for the English feed, for the German feed,JetztKaufen, and)

Logo&Brand Guideline(when available).

Product Unique Information(e.g., eco-friendly, certificate unique to your product, free delivery, etc.). Any additional information that is expected to be changed per product or overtime must be part of a column in the feed.

A Templateof your choice from the below options:

T1A

T1B

T2A

T2B

T2C

T3

T4

T6

T8

T12

Listed below is the information we kindly ask you to provide us with in order to create your custom ad template.

Please note: We implement Google Web-safe fonts in our creatives.

CTAandCurrencyper language feed. (e.g.,Shop now and$ can be your tags for the English feed, for the German feed,JetztKaufen, and)

Logo&Brand Guideline(when available).

Product Unique Information(e.g., eco-friendly, certificate unique to your product, free delivery, etc.). Any additional information that is expected to be changed per product or overtime must be part of a column in the feed.

A Templateof your choice from the below options:

T1A

T1B

T2A

T2B

T2C

T3

T4

T6

T8

T12