Versions Compared

Key

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

Purchase event optimizations will be implemented under the assumption that

i) the ‘Backend Purchase’ event will become the source of truth since cookie settings are expected to significantly impact the volume of front-end events forwarded to Amplitude

ii) the ‘eCommerce Purchase’ front-end event will be deprecated after the optimisations to the back-end event are completed

...

Ecommerce Event Property

Conclusion

Comment

Address Type

Has Upsell

hasSavedDeliveryAddress

It’s important information to know the # of users making order with a saved delivery address to gather insights on store locator features

hasSelectedRecentAddress

It’s important information to know the # of users making order with a recent delivery address to gather insights on store locator features

Rewards

totalDeliveryOrderFeeAmount

Upsell Total

Product Count

Loyalty Cart Data

products

Loyalty Cart Data

products.added_to_cart_time_ms

Loyalty Cart Data

products.cartId

Loyalty Cart Data

products.comboChild

Loyalty Cart Data

products.custom_attributes.cartId

Loyalty Cart Data

products.custom_attributes.comboChild

Loyalty Cart Data

products.custom_attributes.isDonation

Loyalty Cart Data

products.custom_attributes.isExtra

Loyalty Cart Data

products.custom_attributes.Item Level

Loyalty Cart Data

products.custom_attributes.L1

Loyalty Cart Data

products.custom_attributes.L2

Loyalty Cart Data

products.custom_attributes.L3

Loyalty Cart Data

products.custom_attributes.L4

Loyalty Cart Data

products.custom_attributes.L5

Loyalty Cart Data

products.custom_attributes.rewardItem

Loyalty Cart Data

products.custom_attributes.sublevelItems

Loyalty Cart Data

products.id

Loyalty Cart Data

products.isDonation

Loyalty Cart Data

products.isExtra

Loyalty Cart Data

products.Item Level

Loyalty Cart Data

products.L1

Loyalty Cart Data

products.L2

Loyalty Cart Data

products.L3

Loyalty Cart Data

products.L4

Loyalty Cart Data

products.L5

Loyalty Cart Data

products.name

Loyalty Cart Data

products.position

Loyalty Cart Data

products.price

Loyalty Cart Data

products.quantity

Loyalty Cart Data

products.rewardItem

Loyalty Cart Data

products.sublevelItems

Loyalty Cart Data

products.total_product_amount

Loyalty Cart Data

Table 2: Event properties to deprecate for Backend Purchase

Info

In the Excel file, all the properties for the Backend Purchase event are listed.

rbi does not recommend to deprecate any event properties from the Backend Purchase event.

Please check whether there is any property that should you recommend to be deprecated and add it to the table with a justification why.

As a reference, the Excel file also contains the FE eCommerce Purchase event along with its properties.

View file
nameBackend Purchase Properties.xlsx

Ecommerce Event Property

Conclusion

Comment

Table 3: Event properties to add to Backend Purchase (rbiberia requests)

Ecommerce Event Property

Conclusion

Comment

Promotional Code 

Status
colourGreen
titleADD

If a user makes a purchase with a promo code, we don’t save that attribute in the purchase event

Promotional Code Submitted
(Succesful|Fail)

Status
colourRed
titlewon't do

Not clear what’s the difference vs the 1st one. Once making the purchase, the promotional code will be used. Code applied status should be a property of an interaction event

Detail Promo Code Submited

Status
colourRed
titlewon't do

Not clear how to have it implemented in the Backend Purchase as the purchase is the final state. The promo code being submitted comes at an earlier stage and would be covered as a property of the interaction event

Coupons

Status
colourRed
titleWon't ADD

We already have a property called Offer Applied (True/False) and a property called Offer ID with the Sanity ID of the coupon applied.

Delivery fee
(True|False)

Status
colourRed
titleWon't ADD

We already have that property where we specify the amount of delivery fee the user has been charged

Device Date

Status
colourRed
titleWon't ADD

At the time of the purchase, the event will fire with a certain timestamp. As it is a BE event, it won’t record information from the FE (Device)

Donation amount 

Status
colourRed
titleWon't ADD

We already have exactly the Donation Amount property live in Backend Purchase. It is currently showing value 0 because there are no donations.

Payment Status
(pending|done)

Status
titleunclear

We have 2 events: order_status_change and delivery_status_change where the order status is recorded. We can potentially show whether the Payment was pending for delivery orders when users trigger the Backend Purchase.

Tax Amount

Status
colourYellow
titlevalidate

Already exists in the Backend Purchase event, validate the implementation is correctly done

Info

Any requirement for additional BE Purchase related events to be assessed at a later date