You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`userId`| If registered user place order then the value of userId will be the Customer ID otherwise it will be order ID. You can change this as per your requirement. |
72
-
|`event`|Event name e.g. `Checkout Started`, `Order Completed` etc. |
73
-
|`properties`| This will hold information about the order |
74
-
|`properties.order_id`| Elastic Path Order ID |
75
-
|`properties.value`|Revenue ($) with discounts and coupons added in. For better flexibility and total control over tracking, we let you decide how to calculate how coupons and discounts are applied. Usually this is required for `Checkout Started` event |
76
-
|`properties.total`|Revenue ($) with discounts and coupons added in. For better flexibility and total control over tracking, we let you decide how to calculate how coupons and discounts are applied. Usually this is required for all the events apart from `Checkout Started` event |
77
-
|`properties.revenue`|Revenue ($) associated with the transaction (excluding shipping and tax). Usually this is required for all the events apart from `Checkout Started` event |
78
-
|`properties.tax`|Total tax associated with the transaction |
79
-
|`properties.discount`|Total discount associated with the transaction |
80
-
|`properties.shipping`|Shipping cost associated with the transaction |
81
-
|`properties.currency`|Currency code associated with the transaction e.g. GBP, USD etc. |
82
-
|`properties.products`|List of products in the order |
83
-
|`properties.products.$.product_id`|Product ID|
84
-
|`properties.products.$.name`|Product Name|
85
-
|`properties.products.$.sku`|Product SKU |
86
-
|`properties.products.$.price`|Product Unit Price|
87
-
|`properties.products.$.quantity`|Quantity of a product |
71
+
|`userId`| If the registered user places an order, then the value of the userId is the Customer ID. Otherwise, it will be the order ID. You can change this as per your requirement. |
72
+
|`event`|The event name, for example, `Checkout Started`, `Order Completed`. |
73
+
|`properties`| This holds information about the order.|
74
+
|`properties.order_id`|The Elastic Path Order ID.|
75
+
|`properties.value`|The revenue ($) with discounts and coupons added in. For better flexibility and total control over tracking, Elastic Path lets you decide how to calculate how coupons and discounts are applied. This is usually required for the `Checkout Started` event.|
76
+
|`properties.total`|The revenue ($) with discounts and coupons added in. For better flexibility and total control over tracking, Elastic Path lets you decide how to calculate how coupons and discounts are applied. This is usually required for all the events apart from the `Checkout Started` event.|
77
+
|`properties.revenue`|The revenue ($) associated with the transaction (excluding shipping and tax). This is usually required for all the events apart from the `Checkout Started` event.|
78
+
|`properties.tax`|The total tax associated with the transaction.|
79
+
|`properties.discount`|The total discount associated with the transaction.|
80
+
|`properties.shipping`|The shipping cost associated with the transaction.|
81
+
|`properties.currency`|The currency code associated with the transaction. For example, GBP, USD. |
82
+
|`properties.products`|The list of products in order.|
|`properties.products.$.price`|The product unit price.|
87
+
|`properties.products.$.quantity`|The quantity of a product.|
88
88
89
89
Note: We are using properties of these events from [eCommerce Spec](https://segment-docs.netlify.app/docs/connections/spec/ecommerce/v2){:target="_blank"} defined by Segment doc. Add more properties as per this documentation based on your business requirement.
0 commit comments