Navigation
The ‘Page View’ event with a filter based on its event property ‘path’ can be used as an alternative to all the deprecated ‘Viewed’ events
...
Sign up
To measure the conversion rate of guests who have successfully signed up, please compare events ‘Sign Up Submitted' and 'Sign In Complete’
To measure the conversion rate of guests who have successfully signed up or signed in, please compare events ‘Sign Up Submitted/Sign In Submitted' and 'Sign In Complete’
| Info |
|---|
Existing users who will try to sign up instead of sign in will trigger the ‘Error’ event where Response Description = email already exists, please sign in. To account for all users that are indeed trying to sign up and not sign in, the users who got that specific error should be filtered out. |
Offers
To track promo codes being used, we should rely on the events ‘Action Sheet View’ and ‘Action Sheet Submission’ (for instance, when using Voucherify).
If a market is leveraging on the Partner API to assign promo codes, it should be used the ‘Promo Code Applied’ event instead.
Further information on the events to use can be found in the FZ KB here, along with the associated attributes: https://rbictg.atlassian.net/wiki/spaces/COG/pages/4041605275/Loyalty+Offers+Events+Conversion#Promo-Codes