The following document offers insight into BI data forwarding to Remerge via the Remerge Event Tracking API. You may employ the below information to provide Remerge with a variety of supplemental data that are not in-app user events (e.g., whale/churn risk users or certain postbacks). In case of any questions, please reach out to your Remerge Account Manager.
General
- To provide us with lists, please utilize our Recurring List Import guide.
- Limit your GET request to 1k per second.
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}).
Flag
- The presence of a non_app_event=true flag differentiates your BI events from your user in-app events (e.g., received clicks or other BI data). Therefore, ensure to flag the data you would like to forward to Remerge with a True tag, which enables Remerge to employ said data for the below purposes:
- Targeting (e.g., we should target only certain users).
- General Information (e.g., a click postback).
| Name | Content | Examples |
|---|---|---|
| non_app_event |
The event is not created by the app (i.e., a click postback) |
true |
Naming Conventions
- The event name should reflect its nature (e.g., click/whales/churn risk).
| Name | Content | Examples |
|---|---|---|
| event |
The name of your BI event |
click, whales, churn_risk |
Example
- A Non-App Event Postback Example:
https://remerge.events/event?app_id={GooglePlay or AppstoreID}&event=whales_user&partner=yourname&key=yourkey&idfa={IDFA}&aaid={AAID}&idfv={IDFV}&os_name={OSName}&non_app_event=true