Our SDKs provide several overloaded methods to measure in-app events. Some of the methods allow you to enter the Event ID and Reference ID, which serve different purposes in the method and should not be confused (to ensure proper functioning). This page describes how you can use each of these IDs.
When measuring an event from the SDK, you can choose to measure either a pre-defined event or a dynamically created event. To measure a pre-defined event, simply use the TMC Event ID for the event. To measure a dynamically created event, use its name (for example, “HighScoresPageViewed”). If an event by this name does not exist, then MAT automatically creates one.
To manage pre-defined events, login to TMC, go to the Mobile Apps tab, and select an app. There you can view existing Event Ids in the Events List or create a new event by clicking Add Event.
Only the Event IDs listed in the Event ID column (of the Events List table) may be used for corresponding pre-defined events. If you use any other value, then Attribution Analytics treats it as a dynamic event name.
When measuring an event from the SDK, you can optionally include a unique Reference Id that might match your internal system. These unique Reference Ids can serve two purposes: to reconcile with your internal system, and to make sure that Attribution Analytics does not ignore the event as a duplicate.
Normally, Attribution Analytics ignores duplicate events received during a specified time period after the first event. For information, please see Block Duplicate Request Setting for Events.
If you want to measure multiple events with the same name or Event Id during the Block Duplicate Length setting (as mentioned in the link above), then you can assign unique Reference Ids to the events to indicate to Attribution Analytics that these events are unique.
Android & iOS Setup
Select a preferred platform.