Page Comparison

Main points to discuss

1. Loyalty Transaction Claimed is not triggered when an in-store loyalty is done (it triggers the in-store loyalty transaction instead)

2. Unsubscription is not covered as an event

3. Clarify difference between “offer” and “offerSanityID”

4. Currently to identify if the transaction is made at kiosk or not, we are relying on the property ‘POS system’ but the naming is misleading. See here: https://app.eu.amplitude.com/analytics/rbiberia/chart/e-nmil52n4

5. Can we add Total Amount?

   1. Validate what amount is sent as ‘subtotal’

      1. We should have total amount (net + vat)

      2. Net

      3. VAT

   2. Ensure format is consistent, e.g. 27.45 instead of 2745

6. Missing attributes for points earned/deducted:

   1. points earned via remediation

   2. points deducted due to un-subscription

   3. points earned via support

Reference ticket: PLK ES - Discrepancy in Amplitude vs Snowflake loyalty data due to missing data fields in Amplitude - International Tech Service Desk - Jira Service Management (atlassian.net)

7. Fraud events Max Transaction Limit Reached and Max Points Earned Limit Reached “

   1. Merge events into one event with 2 different types OR

   2. Add these as user attributes

8. Deprecate the Offer Redeemed Confirmed event since the Legacy Offer Redeemed In-Store event is already used

9. Change all “In-store” wording to “In-Restaurant”