The following document offers insight into the process of Attribution data forwarding to Remerge via the Remerge Event Tracking API. You may employ the below information to provide Remerge with (in-app) user events attributed to Remerge. In case of any questions, please reach out to your Remerge Account Manager.
General
- The attribution of said (in-app) events is based on a user's engagement (in the form of a click/impression) with the ad in question.
- In case you have yet to set up your Click & Impression URL with Remerge, please refer to our list of available placeholders.
- Review our documentation and provide your Remerge Account Manager with your Attribution Windows.
Process
Request
- Utilize the principles and structure depicted in our Event Data Forwarding documentation (e.g.,https://remerge.events/event?app_id={GooglePlay or AppstoreID}&event={PLACEHOLDER}&partner=yourname&key=yourkey&idfa={PLACEHOLDER}&aaid={PLACEHOLDER}&idfv={PLACEHOLDER}&os_name={PLACEHOLDER}&revenue={PLACEHOLDER}¤cy={PLACEHOLDER} ).
Parameters
- Employ any of the below parameters by adding them to your URL.
| Name | Content | Examples |
|---|---|---|
| event (M) |
Name of the event attributed to Remerge |
purchase |
| is_attributed (M) |
Definition of whether an event is attributed to Remerge/other sources |
1 (= Remerge) or 0 (= organic/other media source) |
| partner_attribution_method (M) |
Definition of whether an event is attributed to a view/click |
click, view |
| network |
In case the event is attributed to a partner, the network's name/ID |
Remerge, Facebook, organic |
| click_id (M) |
The click ID you received with our click/impression tracking URL |
iwShT9ec49 |
| partner_match_type |
The method used for matching the attribution to the click/impression engagement |
e.g., deterministic, deep link, or referrer |
| campaign (M) |
The campaign name you received with our click/impression tracking URL |
shopping_global |
| creative |
The creative name you received with our click/impression tracking URL
|
fx_promotion.png |
| ad |
The ad label name you received with our click/impression tracking URL
|
spring_collection |
| label (M) |
The label ID you received with our click/impression tracking URL |
385924 |
* Android-Specific Parameters
| Name | Content | Examples |
|---|---|---|
| referrer |
The referrer URL of the installed package |
utm_source%3Dgoogle-play%26utm_medium%3Dorganic
|
| referrer_click_ts |
Client-side timestamp, in seconds, when the referrer click happened as Unix Epoch. The timezone is in UTC and 10digits long |
1660117832 |
| install_start_ts |
Client-side timestamp, in seconds, when app installation began as Unix Epoch. The timezone is in UTC and 10digits long |
1660118223 |
Rejected Attributions
| Name | Content | Examples |
|---|---|---|
| event (M) |
Append rejected_ to the original name of the event as in rejected_{name of event} (e.g., rejected_install) |
rejected_{name of the event} |
| rejection_reason (M) |
The reason for the rejection |
CTIT_(Click Time To Install)anomalies |
| rejection_sub_reason |
A more detailed reason for the rejection |
short_ctit |
| rejection_sub_value |
The actual value that led to the rejection, e.g., an IP address, a user agent, or the number of seconds for the install |
4 |
Examples
- An Example of a Purchase Event Attributed to Remerge Based on Click:
...&event=purchase&is_attributed=1&network=remerge&partner_attribution_method=click&revenue=7490¤cy=usd&campaign=winterspices&label=23455&click_id=2ed9i93ke9oo - An Example of an Unattributed (organic) Purchase Event:
...&event=purchase&is_attributed=0&network=organic&partner_attribution_method=&revenue=7490¤cy=usd&campaign=&label=&click_id= or - An Example of an Unattributed (another network) Purchase Event:
...&event=purchase&is_attributed=0&network=mediaB&partner_attribution_method=view&revenue=7490¤cy=usd&campaign=wintertheme&label=&click_id=
* Information courtesy of the Android Google Play Install Referrer API for event=install documentation.