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 | |
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 | rbi Comment |
|---|---|---|
Restaurant Drive Thru Lane Type | ||
Restaurant Has Breakfast | ||
Restaurant Has Burgers For Breakfast | ||
Restaurant Has Catering | ||
Restaurant Has Curbside | ||
Restaurant Has Dine In | ||
Restaurant Has Drive Thru | ||
Restaurant Has Home Delivery | ||
Restaurant Has Mobile Ordering | ||
Restaurant Has Parking | ||
Restaurant Has Playground | ||
Restaurant Has Table Service | ||
Restaurant Has Take Out | ||
Restaurant Has Wifi | ||
Restaurant Latitude | ||
Restaurant Longitude | ||
Restaurant ID | Use Restaurant Number |
Table 3: Event properties to add to Backend Purchase (rbiberia requests)
Ecommerce Event Property | Conclusion | rbi 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 | 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. |
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. |
Tax Amount | LATER | This is always ‘0.0’ on FE & BE Purchase Events What is the expected calculation? |
deliveryFeeAmount | EXISTING | Existing as deliveryFeeAmount |
deliveryDiscountAmount | WON'T ADD | This is always ‘0' or 'none’ on FE purchase events What is the expected calculation? |
deliveryGeographicalFeeAmount | WON'T ADD | This is always ‘0' or 'none’ on FE purchase events What is the expected calculation? |
Device Time | WON'T ADD | For BE events, Device Time is not available but each individual event has a timestamp Use the calendar and enable Time Range to filter events between times |
Is Kiosk | WON'T ADD | This is always ‘none’ or ‘false’ on FE purchase events Use ‘posSystem' property in 'In-Store Loyalty Transaction Claimed’ events |
Payment Status | WON'T ADD | The oder status will always be the same ('INSERT_SUCCESSFUL') when the BE purchase event is fired so is not useful |
posSystem | WON'T ADD | use posSystem property In-Store Loyalty Transaction Claimed events for kiosk purchases Can we add Offer ID and Offer Applied to In-Store Loyalty Transaction Claimed events? |
posType | WON'T ADD | use ‘posType’ property in ‘In-Store Loyalty Transaction Claimed’ events |
Rewards | LATER | pls use Loyalty events for now, we need to check feasibility of adding 'Add Reward Applied' and 'Reward ID' in the future |
deliveryServiceFeeAmount | LATER | ServiceFeeAmount is available but always ‘0' or 'none’ on BE purchase events Also, deliveryServiceFeeAmount is always ‘0' or 'none’ on FE purchase events What is the expected calculation? Expected to be applicable to BK ES |
deliverySmallCartFeeAmount | LATER | SmallCartFee is available but always ‘0' or 'none’ on BE purchase events What is the expected calculation? Expected to be applicable to BK ES |
Source Page | WON'T ADD | FE events have to be used for user interaction |
Transaction Id | WON'T ADD | Use Transaction RBI Cloud Order ID, this is the same as Transaction ID |
Upsell Simplified Enabled | WON'T ADD | Is upselling currently available? This property is unavailable for BE events |
Upsell Total | LATER | if feasible, to be added |
Address Type | WON'T ADD | Only available for FE events |
hasSavedDeliveryAddress | WON'T ADD | Only available for FE events |
Mobile number used for orders which is not same as default number in profile? | LATER | Luke to check |
Any requirement for additional BE Purchase related events to be assessed at a later date
0 Comments