...
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. |
...
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 should be used 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
Consent
For users who accept cookies via the OneTrust cookie banner, a ‘Consent Given’ event is sent to Amplitude with a ‘Purpose’ property which represents the cookie category, an event is sent per category
For users who reject cookies via the OneTrust cookie banner, a ‘Consent Rejected’ event is sent to Amplitude with a ‘Purpose’ property which represents the cookie category, an event is sent per category
Deprecated User Properties
# | Event Property | Comment |
|---|---|---|
1 | $Age | Use 'Age' property |
2 | Birthday Date | Use ‘dob’ property ('Birthday' in Braze segments) |
3 | Email Opt In | Use ‘email_subscribe’ property ('Email Subscription Status' in Braze segments) |
4 | firstName | Use ‘FirstName’ property |
5 | Language | Use ‘language’ property |
6 | Last Order Date | Use ‘Date Last Order’ property |
7 | lastName | Use LastName instead |
8 | loyalty | Where loyalty id is not null can be used as a filter |
9 | Name | Use ‘FirstName’ and ‘LastName’ properties |
10 | Push Notifications | Use ‘push_subscribe’ property ('Push Subscription Status' in Braze segments) |
11 | rewardsEmail | Use ‘email_subscribe’ property ('Email Subscription Status' in Braze segments) |
12 | userId | Use 'user_id' property |
13 | web_os_name | Use ‘OS’ and ‘Platform’ properties |
14 | zipcode | Use ‘Zip’ property |
15 | marketingEmail | Use ‘email_subscribe’ property ('Email Subscription Status' in Braze segments) |
16 | marketingPush | Use ‘push_subscribe’ property ('Push Subscription Status' in Braze segments) |