Versions Compared

Old Version 5

changes.mady.by.user Fisher, Luke

Saved on

compared with

New Version 6

changes.mady.by.user Rodrigues da Silva, Manuel

Saved on

Key

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

...

...

...

...

Info

Purchase event optimization is under the assumption that in the medium term, the Backend Purchase will be the source of truth.

Table 1: Event properties to

...

add to Backend Purchase from eCommerce Purchase

Ecommerce Event Property

Conclusion

Comment

deliverySurchargeFeeAmount

Address Type

Status
colourGreen
titlekill

mparticle_amplitude_should_split

Status
colourGreen
titlekill

products.added_to_cart_time_ms

Status
colourGreen
titlekill

Transaction POS

Status
colourGreen
titlekill

Info already logged in Restaurant POS property

Value Threshold 10 Met

Status
colourGreen
titlekill

Value Threshold 5 Met

Status
colourGreen
titlekill

baseDeliveryFeeAmount

Status
colourGreen
titlekill
Duplicate

branch_service_mode

Status
colourGreen
titlekill
Duplicate

customer_event_alias

Status
colourGreen
titlekill
Duplicate

quotedFeeAmount

Status
colourGreen
titlekill
Duplicate

totalDeliveryOrderFeeAmount

Status
colourGreen
titlekill
Duplicate

hasSavedDeliveryAddress

StatuscolourRedtitleWon't kill

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

StatuscolourtitleWon't kill

Red

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.

Restaurant Name

Status
colourRed
titleWON"t KILL
Add as User Property too

Restaurant Number

Status
colourRed
titleWON"t KILL
Add as User Property too

revenue

Status
colourYellow
titlehold
Only kill after deprecating Ecommerce Purchase event

products.id

Status
colourBlue
titleTO BE REVIEWED

products.position

Status
colourBlue
titleTO BE REVIEWED

Restaurant Drive Thru Lane Type

Status
colourBlue
titleTO BE REVIEWED

Restaurant Front Counter Closed

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Breakfast

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Burgers For Breakfast

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Catering

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Curbside

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Dine In

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Drive Thru

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Front Counter Closed

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Home Delivery

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Mobile Ordering

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Parking

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Playground

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Table Service

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Take Out

Status
colourBlue
titleTO BE REVIEWED

Restaurant Has Wifi

Status
colourBlue
titleTO BE REVIEWED

Restaurant Latitude

Status
colourBlue
titleTO BE REVIEWED

Restaurant Longitude

Status
colourBlue
titleTO BE REVIEWED

Restaurant Number Drive Thru Windows

Status
colourBlue
titleTO BE REVIEWED

Restaurant POS

Status
colourBlue
titleTO BE REVIEWED

Timed Fire Minutes

Status
colourBlue
titleTO BE REVIEWED

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

products.cartId

Status
titleto double check
Duplicate?

products.comboChild

Status
titleto double check
Duplicate?

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

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.comboChild

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.isDonation

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.isExtra

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.Item Level

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.L1

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.L2

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.L3

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.L4

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.L5

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.rewardItem

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.custom_attributes.sublevelItems

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.id

Loyalty Cart Data

products.isDonation

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.isExtra

Loyalty Cart Data

products.Item Level

Loyalty Cart Data

products.L1

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.L2

Loyalty Cart Data

products.L3

Loyalty Cart Data

products.

L2

L4

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.L5

Loyalty Cart Data

products.

L3

name

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.position

Loyalty Cart Data

products.

L4

price

Status
titleto double check
Duplicate?

products.L5

Status
titleto double check
Duplicate?

Loyalty Cart Data

products.quantity

Loyalty Cart Data

products.rewardItem

Loyalty Cart Data

products.sublevelItems

Loyalty Cart Data

products.total_product_amount

Status
titleto double check
Duplicate?

...

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. Please check whether there is any property that should be deprecated and add it to the table with a justification why.

View file
nameBackend Purchase Properties.xlsx

Ecommerce Event Property

Conclusion

Comment

Table 3: Event properties to add to

...

Backend Purchase

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
titleunclearwon'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
colourRed
titleunclearwon'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 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
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. 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
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. Once we have donations, check the values are being logged correctly.

Payment Status
(pending|done)

Status
colourRed
titleWon'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
colourYellow
titlevalidate

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