...
These events have less detail since they don’t know which UI component was used to trigger the event, but they are more reliable since they are only captured once a request has actually been processed by the RBI platform (while some User Interaction events may be lost in case the web/app loses connectivity). Examples of Conversion events are:
Sign Up In CompleteOrder Complete
Backend Purchase
Item Added to Cart
Offer Redeemed
Reward Redeemed
...
In addition to the above, we group events according to the user flow they belong to. In Amplitude these are called Categories, while in mParticle they are called Tags. Events are categorised categorized as follows:
User Flow | Description |
|---|---|
Authentication | Events related to the Sign Up, Sign In and Sign out flow |
Branch | Events that have Branch as a source |
CRM | Related to campaign management (Email Opens, bounces, etc) |
Session | Used for events related to the start and and of a session, flags evaluated, user attributes updates |
Loyalty | Events related to the Loyalty program (transactions claimed, users created, points expiring) |
Offers | Events related to the Offers features (e.g. offer selected, offer added to cart) |
Rewards | Related to the reward flow in the loyalty program (reward selected, reward added to order) |
Marketing | Used for ad-hoc marketing campaigns |
Navigation | Used to understand our users interaction with clickable and viewable components (e.g. Page View, Button Click) |
Orders | Related to transactional events, e.g. add to cart, checkout, purchase |
Deprecated | Used for events that will be replaced by new ones or are related to deprecated features. See more details here: Deprecated Events |
How it works
Amplitude
In Amplitude the event categories appears in charts and dropdown menus:
...