Purchase Events & Properties

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 1: Event properties to add to Backend Purchase from eCommerce Purchase

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	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	Cart Data
products.custom_attributes.comboChild	Cart Data
products.custom_attributes.isDonation	Cart Data
products.custom_attributes.isExtra	Cart Data
products.custom_attributes.Item Level	Cart Data
products.custom_attributes.L1	Cart Data
products.custom_attributes.L2	Cart Data
products.custom_attributes.L3	Cart Data
products.custom_attributes.L4	Cart Data
products.custom_attributes.L5	Cart Data
products.custom_attributes.rewardItem	Cart Data
products.custom_attributes.sublevelItems	Cart Data
products.id	Cart Data
products.isDonation	Cart Data
products.isExtra	Cart Data
products.Item Level	Cart Data
products.L1	Cart Data
products.L2	Cart Data
products.L3	Cart Data
products.L4	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	Cart Data

Table 2: Event properties to deprecate for Backend Purchase

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.

Ecommerce Event Property	Conclusion	Comment

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

Ecommerce Event Property	Conclusion	Comment
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)	WON'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	WON'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	WON'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)	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. As it is a BE event, it won’t record information from the FE (Device)
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.
Payment Status (pending\|done)	UNCLEAR 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	VALIDATE Already exists in the Backend Purchase event, validate the implementation is correctly done

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

Purchase Events & Properties

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)

0 Comments