Table 1: Event properties to deprecate for Ecommerce Purchase
...
Ecommerce Event Property
...
Conclusion
...
Comment
...
deliverySurchargeFeeAmount
...
| Status | ||||
|---|---|---|---|---|
|
...
mparticle_amplitude_should_split
...
| Status | ||||
|---|---|---|---|---|
|
...
products.added_to_cart_time_ms
...
| Status | ||||
|---|---|---|---|---|
|
...
Transaction POS
...
| Status | ||||
|---|---|---|---|---|
|
Info already logged in Restaurant POS property
...
Value Threshold 10 Met
...
| Status | ||||
|---|---|---|---|---|
|
...
Value Threshold 5 Met
...
| Status | ||||
|---|---|---|---|---|
|
...
hasSavedDeliveryAddress
...
| Status | ||||
|---|---|---|---|---|
|
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 | ||||
|---|---|---|---|---|
|
It’s important information to know the # of users making order with a recent delivery address to gather insights on store locator features
...
...
| Status | ||||
|---|---|---|---|---|
|
...
products.position
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Drive Thru Lane Type
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Front Counter Closed
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Breakfast
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Burgers For Breakfast
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Catering
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Curbside
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Dine In
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Drive Thru
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Front Counter Closed
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Home Delivery
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Mobile Ordering
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Parking
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Playground
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Table Service
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Take Out
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Has Wifi
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Latitude
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Longitude
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant Number Drive Thru Windows
...
| Status | ||||
|---|---|---|---|---|
|
...
Restaurant POS
...
| Status | ||||
|---|---|---|---|---|
|
...
Timed Fire Minutes
| Status | ||||
|---|---|---|---|---|
|
...
| 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 | ||
|---|---|---|
|
Table 1: Event Properties to add to Backend Purchase
Event Property | Comment |
|---|---|
Promotional Code | If applied to order |
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 from 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.
|
Event Property | 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 ID | Use Restaurant Number instead |
Restaurant Latitude | |
Restaurant Longitude |
Table 3: Event properties to potentially add to Backend Purchase later
Property | Comment |
|---|---|
Address Type | This information is not stored on backend, requires further analysis |
deliveryServiceFeeAmount | Requires analysis to check feasibility of adding |
deliverySmallCartFeeAmount | Requires analysis to check feasibility of adding |
Mobile number (if not matching stored mobile number) | Requires analysis to check feasibility of adding |
hasSelectedRecentAddress | This information is not stored on backend, requires further analysis |
hasSavedDeliveryAddress | This information is not stored on backend, requires further analysis |
Rewards | Requires analysis to check feasibility of adding 'Add Reward Applied' and 'Reward ID' |
Upsell Total | Requires analysis to check feasibility of adding |
| Info |
|---|
Need to check why existing property ‘Tax Amount’ only returns 0.0 value! |