Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

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)

  • No labels