Page Comparison

...

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

Table of Contents

style	none

Table 1: Event properties to

...

add to Backend Purchase from eCommerce Purchase

Ecommerce Event Property	Conclusion	Comment

deliverySurchargeFeeAmount

Status

colour	Green
title	kill

mparticle_amplitude_should_split

Status

colour	Green
title	kill

products.added_to_cart_time_ms

Status

colour	Green
title	kill

Transaction POS

Status

colour	Green
title	kill

Info already logged in Restaurant POS property

Value Threshold 10 Met

Status

colour	Green
title	kill

Value Threshold 5 Met

Status

colour	Green
title	kill

baseDeliveryFeeAmount

Status

colour	Green
title	kill

Duplicate

branch_service_mode

Status

colour	Green
title	kill

Duplicate

customer_event_alias

Status

colour	Green
title	kill

Duplicate

quotedFeeAmount

Status

colour	Green
title	kill

Duplicate

totalDeliveryOrderFeeAmount

Status

colour	Green
title	kill

Duplicate

hasSavedDeliveryAddress

StatuscolourRedtitleWon't kill

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

status

colour	Red
title	Won't kill

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

Pickup Mode

Rewards

status


totalDeliveryOrderFeeAmount

colour


Upsell Total

RedtitleWon't kill

Service Mode indicates between Pick up and Delivery. Pick up mode indicates whether the Pick up was Eat in, Take away, Table service.

revenue

Status

colour	Yellow
title	hold

Only kill after deprecating Ecommerce Purchase event

Restaurant Name

Status

colour	Blue
title	usr property

Restaurant Number

Status

colour	Blue
title	usr property

products.id

Status

colour	Blue
title	TO BE REVIEWED

products.position

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Drive Thru Lane Type

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Front Counter Closed

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Breakfast

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Burgers For Breakfast

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Catering

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Curbside

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Dine In

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Drive Thru

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Front Counter Closed

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Home Delivery

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Mobile Ordering

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Parking

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Playground

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Table Service

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Take Out

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Has Wifi

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Latitude

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Longitude

Status

colour	Blue
title	TO BE REVIEWED

Restaurant Number Drive Thru Windows

Status

colour	Blue
title	TO BE REVIEWED

Restaurant POS

Status

colour	Blue
title	TO BE REVIEWED

Timed Fire Minutes

Status

colour	Blue
title	TO BE REVIEWED

Could be related to queuing system and thus needed on a global state

products.cartId

Status

title	to double check

Duplicate?

products.comboChild

Status

title	to double check

Duplicate?

Product Count	Cart Data
products	Cart Data
products.added_to_cart_time_ms	Cart Data
products.cartId	Cart Data
products.comboChild	Cart Data
products.custom_attributes.cartId

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.comboChild

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.isDonation

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.isExtra

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.Item Level

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.L1

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.L2

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.L3

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.L4

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.L5

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.rewardItem

Status

title	to double check

Duplicate?

Cart Data
products.custom_attributes.sublevelItems

Status

title	to double check

Duplicate?

Cart Data
products.id	Cart Data
products.isDonation

Status

title	to double check

Duplicate?

	Cart Data
products.isExtra	Cart Data
products.Item Level	Cart Data
products.L1

Status

title	to double check

Duplicate?

	Cart Data
products.L2	Cart Data
products.L3	Cart Data
products.

L2

L4

Status

title	to double check

Duplicate?

products.L3

Status

title	to double check

Duplicate?

products.L4

Status

title	to double check

Duplicate?

products.L5

Status

title	to double check

Duplicate?

Cart Data
products.L5	Cart Data
products.name	Cart Data
products.position	Cart Data
products.price	Cart Data
products.quantity	Cart Data
products.rewardItem	Cart Data
products.sublevelItems	Cart Data
products.total_product_amount

Status

title	to double check

Duplicate?

...

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 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

name	Backend 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

colour	Green
title	ADD

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

colour	Red
title	unclearwon'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 another an interaction event

Detail Promo Code Submited

Status

colour	Red
title	unclearwon'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

colour	Red
title	Won't ADD

We already have a property called Coupon Offer Applied (True/False) and a property called Coupon Offer ID with the Sanity ID of the coupon applied.PS: For naming consistency in the code, Coupon Applied and Coupon ID will be changed to Offer Applied and Offer ID

Delivery fee
(True|False)

Status

colour	Red
title	Won't ADD

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

Device Date

Status

colour	Red
title	Won't ADD

At the time of the purchase, the event will fire with a certain timestamp. Device Time is planned to be a user property as wellAs it is a BE event, it won’t record information from the FE (Device)

Donation amount

Status

colour	Red
title	Won'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. Once we have donations, check the values are being logged correctly.

Payment Status
(pending|done)

Red

Status

colour

title	Won't ADDunclear

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

colour	Yellow
title	validate

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

Versions Compared

Old Version 4

New Version 11

Key

Table 1: Event properties to

add to Backend Purchase from eCommerce Purchase

Table 2: Event properties to deprecate for Backend Purchase

Table 3: Event properties to add to

Backend Purchase (rbiberia requests)