Versions Compared

Old Version 4

changes.mady.by.user Lopes da Costa, Valentina

Saved on

compared with

New Version 5

changes.mady.by.user Lopes da Costa, Valentina

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Contents

Table of Contents

Overview

Currently, In-Store orders represent the largest percentage of orders done in our app. Before this improvement our FZs and Business Teams had no visibility on products purchased in In-Store loyalty transactions. This means we could not use basket content to drive decisions such as which campaigns to launch based on specific items guests have purchased. With this feature this is now possible. We have also extended this cart analysis for other Online Loyalty Event transactions.

How does it work?

image (169).png

Events

To see the events related to this feature, please refer to:

  • Go to Loyalty Conversion events and Search for Loyalty Cart Data property to check information that is available on cart data of the orders: https://rbictg.atlassian.net/wiki/spaces/COG/pages/4041605275/Loyalty+Offers+Events+Conversion#Transactions

    • All events that contain Loyalty Cart Data property:

      • In-Store Loyalty Transaction Claimed

      • Loyalty Transaction Claimed

      • Max Transaction Limit Reached

      • Offer Redeemed Confirmed

      • Offer Redeemed In-store

      • Offer Redeemed Online

      • Online Loyalty Transaction Claimed

      • Reward Redeemed In-store

      • Reward Redeemed Online

  • Additionally, you can confirm all events that have this property on your Amplitude dashboard by going to:

    • Data > Properties > Loyalty Cart Data > Used by

Note

For In-Store Loyalty Transactions, the data that is ingested by Amplitude is the data that is sent by Kiosk / POS vendors to RBI Loyalty. If Kiosk / POS vendors do not send all information on cart data of the order (e.g. product names, prices, plus, etc.), then there will be missing data in Amplitude.

How is it configured?

Tip

In order to enable the feature please follow the below steps

mParticle Setup

  • Login to your market’s mParticle dashboard, then click on Connections > Connect and choose your backend input.

Note

If you would like to setup the property only in Staging environment choose backend-dev. If you would like to setup the property only in Production environment choose backend-prod. If you would like to configure both environments please repeat all the below steps for both inputs (backend-dev and then backend-prod).

  • Once you have selected your input, click on Amplitude

  • Then, click on Settings

  • Ensure the item Send Event Attributes as Objects is checked for the brand/environment that will be used

image-20231213-173825.png

Amplitude Setup

Info

For more information, please follow Amplitude’s properties splitting guide: https://help.amplitude.com/hc/en-us/articles/9623000954907-Cart-analysis-Use-object-arrays-to-drive-behavioral-insights#h_01GGX3KMYSJX6EBW6WHRC7PEMH

  1. First, ensure your Amplitude plan has capacity to introduce a new property. To check this, go to Data > Properties > Event Properties and check that the number of event properties is below the Quote for your Amplitude account

Note

Note: if the number of event properties exceeds the capacity available, then the property Loyalty Cart Data will not flow into Amplitude and cannot be used for cart analysis.

  1. Then, setup property splitting for the Event Property Loyalty Cart Data. Go to Data > Properties > Event Properties > Search for event property Loyalty Cart Data > Click on Loyalty Cart Data > on Details tab set Item Type to Any

  1. In the Loyalty Cart Data event property information, go to Details tab > Type > and set Type to Array

  2. Last but not least, click on the Splitting Tab > Review the splitting of the data and when you confirm the splitting is correct > Click on the button Start Splitting Save on the bottom right

Note

Please note, after all the above steps have been completed expect approximately 24 hours for the data to begin flowing into Amplitude for analysis. It takes time for the data to begin being ingested.