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 Retail & E-commerce verticals:
|Event Type||Attribute||Send Revenue?|
|App Opened by User||-|
|Product Viewed by User||Product ID|
|Product Added to Wishlist by User||Product ID|
|Product Added to Cart by User||Product ID|
|Purchase Completed by User||Product ID||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, Product ID, Item ID, Content ID, Item Code 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. Common attribute example:
- Product ID - Can also be Item ID, Item Code, and more.
# 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 Purchase Completed event.
# Purchase Completed - Can also be called, e.g., Order Complete, Order Placed Confirmed, Cart Purchased or Checkout Payment.