Purchase Events & Properties

deliverySurchargeFeeAmount

KILL

mparticle_amplitude_should_split

KILL

products.added_to_cart_time_ms

KILL

Transaction POS

KILL

Info already logged in Restaurant POS property

Value Threshold 10 Met

KILL

Value Threshold 5 Met

KILL

baseDeliveryFeeAmount

KILL Duplicate

branch_service_mode

KILL Duplicate

customer_event_alias

KILL Duplicate

quotedFeeAmount

KILL Duplicate

totalDeliveryOrderFeeAmount

KILL Duplicate

hasSavedDeliveryAddress

WON'T KILL

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

hasSelectedRecentAddress

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

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

WON"T KILL Add as User Property too

Restaurant Number

WON"T KILL Add as User Property too

revenue

HOLD Only kill after deprecating Ecommerce Purchase event

products.id

TO BE REVIEWED

products.position

TO BE REVIEWED

Restaurant Drive Thru Lane Type

TO BE REVIEWED

Restaurant Front Counter Closed

TO BE REVIEWED

Restaurant Has Breakfast

TO BE REVIEWED

Restaurant Has Burgers For Breakfast

TO BE REVIEWED

Restaurant Has Catering

TO BE REVIEWED

Restaurant Has Curbside

TO BE REVIEWED

Restaurant Has Dine In

TO BE REVIEWED

Restaurant Has Drive Thru

TO BE REVIEWED

Restaurant Has Front Counter Closed

TO BE REVIEWED

Restaurant Has Home Delivery

TO BE REVIEWED

Restaurant Has Mobile Ordering

TO BE REVIEWED

Restaurant Has Parking

TO BE REVIEWED

Restaurant Has Playground

TO BE REVIEWED

Restaurant Has Table Service

TO BE REVIEWED

Restaurant Has Take Out

TO BE REVIEWED

Restaurant Has Wifi

TO BE REVIEWED

Restaurant Latitude

TO BE REVIEWED

Restaurant Longitude

TO BE REVIEWED

Restaurant Number Drive Thru Windows

TO BE REVIEWED

Restaurant POS

TO BE REVIEWED

Timed Fire Minutes

TO BE REVIEWED

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

products.cartId

TO DOUBLE CHECK Duplicate?

products.comboChild

TO DOUBLE CHECK Duplicate?

products.custom_attributes.cartId

TO DOUBLE CHECK Duplicate?

products.custom_attributes.comboChild

TO DOUBLE CHECK Duplicate?

products.custom_attributes.isDonation

TO DOUBLE CHECK Duplicate?

products.custom_attributes.isExtra

TO DOUBLE CHECK Duplicate?

products.custom_attributes.Item Level

TO DOUBLE CHECK Duplicate?

products.custom_attributes.L1

TO DOUBLE CHECK Duplicate?

products.custom_attributes.L2

TO DOUBLE CHECK Duplicate?

products.custom_attributes.L3

TO DOUBLE CHECK Duplicate?

products.custom_attributes.L4

TO DOUBLE CHECK Duplicate?

products.custom_attributes.L5

TO DOUBLE CHECK Duplicate?

products.custom_attributes.rewardItem

TO DOUBLE CHECK Duplicate?

products.custom_attributes.sublevelItems

TO DOUBLE CHECK Duplicate?

products.isDonation

TO DOUBLE CHECK Duplicate?

products.L1

TO DOUBLE CHECK Duplicate?

products.L2

TO DOUBLE CHECK Duplicate?

products.L3

TO DOUBLE CHECK Duplicate?

products.L4

TO DOUBLE CHECK Duplicate?

products.L5

TO DOUBLE CHECK Duplicate?

products.total_product_amount

TO DOUBLE CHECK Duplicate?

Promotional Code 

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)

UNCLEAR

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 event

Detail Promo Code Submited

UNCLEAR

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

Coupons

WON'T ADD

We already have a property called Coupon Applied (True/False) and a property called Coupon 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)

WON'T ADD

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

Device Date

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 well

Donation amount 

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)

WON'T ADD

We have 2 events: order_status_change and delivery_status_change where the order status is recorded