One of the first action steps you should take to start running Dynamic Ads with Remerge is: Turn ON Event Forwarding to Remerge on your 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 adding Attributes 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 various means of Transportation (Flight, Train or Bus):
|Event Type||Attribute||Send Revenue?|
|App Opened by User||-|
|Trip Viewed by User||Trip specific information|
|Trip Favourited by User||Trip specific information|
|Trip Purchased by User||Trip specific information||yes|
# Event Type - This is the preferred list of event types and attributes essential to go live. With 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, Origin_ID, Destination ID_A, Destination ID_B, Trip ID, Content ID, City Names, Country/City Codes or other) match the Item IDs in one of the columns in your feed. Although at the 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.
Trip specific information:
- Trip Origin: The format in which you send us your trip origin (traveling starting point) does not matter, as long as it is consistent. Possible alternative examples could be, Origin_ID, Trip ID, City Names (Berlin, New York, etc), Airport Codes (TXL, JFK) or Country/City Codes. The decision should be based on what makes the most sense for your product (trip).
- Trip Destination: The format in which you send us your trip destination (traveling endpoint) does not matter, as long as it is consistent. Possible alternative examples could be, Destination ID_A, Destination ID_B, City Names (Berlin, New York), Airport Codes (TXL, JFK) or Country/City Codes. Here, too, the decision should be based on what makes the most sense for your product (trip).
- Trip Dates: Booking (From_To) dates.
- Any further trip-related information you see fit to share with us may be added by you to the Event Attributes section on your attribution provider's dashboard (First Class, Economy or Other).
# 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 Trip Purchased event.
# Trip Purchased - Can also be called, e.g., Trip Booked, Flight Booked or other.