From 4e00101aa74ee042f2a14a8434240ad972dd5a05 Mon Sep 17 00:00:00 2001 From: rchinn1 Date: Wed, 3 Sep 2025 15:28:10 -0700 Subject: [PATCH 1/3] updates to ecommerce-v2 --- src/connections/spec/ecommerce/v2.md | 154 +++++++++++++-------------- 1 file changed, 77 insertions(+), 77 deletions(-) diff --git a/src/connections/spec/ecommerce/v2.md b/src/connections/spec/ecommerce/v2.md index 202380da79..63316daaf8 100644 --- a/src/connections/spec/ecommerce/v2.md +++ b/src/connections/spec/ecommerce/v2.md @@ -4,7 +4,7 @@ title: 'Spec: V2 Ecommerce Events' Segment's e-commerce spec helps define the journey for a customer as they browse your store, click on promotions, view products, add those products to a cart, and complete a purchase. -> info "Note" +> info "" > Not all destinations support every event listed here and accept arrays as properties. Refer to individual destination documentation for more information on supported events and properties. ## Event lifecycles @@ -14,7 +14,7 @@ Here is a list of supported events for our various categories within the custome ### Browsing overview -| **Action** | **Description** | +| Action | Description | | --- | --- | | Products Searched | User searched for products | | Product List Viewed | User viewed a product list or category | @@ -23,7 +23,7 @@ Here is a list of supported events for our various categories within the custome ### Promotions overview -| **Action** | **Description** | +| Action | Description | | --- | --- | | Promotion Viewed | User viewed promotion | | Promotion Clicked | User clicked on promotion | @@ -32,10 +32,10 @@ Here is a list of supported events for our various categories within the custome ### Core ordering overview -| **Action** | **Description** | +| Action | Description | | --- | --- | | Product Clicked | User clicked on a product | -| Product Viewed | User viewed a product details | +| Product Viewed | User viewed product details | | Product Added | User added a product to their shopping cart | | Product Removed | User removed a product from their shopping cart | | Cart Viewed | User viewed their shopping cart | @@ -50,7 +50,7 @@ Here is a list of supported events for our various categories within the custome ### Coupons overview -| **Action** | **Description** | +| Action | Description | | -------------- | ------------------------------------------------------ | | Coupon Entered | User entered a coupon on a shopping cart or order | | Coupon Applied | Coupon was applied on a user's shopping cart or order | @@ -60,7 +60,7 @@ Here is a list of supported events for our various categories within the custome ### Wishlisting overview -| **Action** | **Description** | +| Action | Description | | ------------------------------ | ----------------------------------------- | | Product Added to Wishlist | User added a product to the wish list | | Product Removed from Wishlist | User removed a product from the wish list | @@ -68,7 +68,7 @@ Here is a list of supported events for our various categories within the custome ### Sharing overview -| **Action** | **Description** | +| Action | Description | | -------------- | ----------------------------------------- | | Product Shared | Shared a product with one or more friends | | Cart Shared | Shared the cart with one or more friends | @@ -76,7 +76,7 @@ Here is a list of supported events for our various categories within the custome ### Reviewing overview -| **Action** | **Description** | +| Action | Description | | ---------------- | ----------------------- | | Product Reviewed | User reviewed a product | @@ -93,7 +93,7 @@ Fire this event when a visitor searches for products. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|-----------------|------------------------------| | query | String \| Object | Query the user searched with | @@ -109,12 +109,12 @@ analytics.track('Products Searched', { Fire this event when a visitor views a product list or category. -> info "Note" +> info "" > Not all destinations accept arrays as properties. Refer to individual destination documentation for more information on supported events and properties. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------------|----------|---------------------------------------------------------| | list_id | String | Product list being viewed | | category | String | Product category being viewed | @@ -163,7 +163,7 @@ analytics.track('Product List Viewed', { ``` -> info "Note" +> info "" > The `Product List Viewed` event is aliased to the `Viewed Product Category` event (from e-commerce v1 spec). @@ -171,12 +171,12 @@ analytics.track('Product List Viewed', { Send this event when a visitor filters a product list or category. -> info "Note" +> info "" > Not all destinations accept arrays as properties. Refer to individual destination docs for more information on supported events and properties. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------------|----------|----------------------------------------------------------------------------| | list_id | String | Product list being viewed | | category | String | Product category being viewed | @@ -256,7 +256,7 @@ Fire this event when a user views a promotion. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | **Example** | +| Property | Type | Description | Example | |--------------|----------|----------------------|--------------------------| | promotion_id | String | Promotion's ID | promo_1 | | creative | String | Promotion's creative | top_banner_2 | @@ -284,7 +284,7 @@ Fire this event when a visitor clicks an internal offer promotion. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | **Example** | +| Property | Type | Description | Example | |--------------|----------|----------------------|--------------------------| | promotion_id | String | Promotion's ID | promo_1 | | creative | String | Promotion's creative | top_banner_2 | @@ -303,7 +303,7 @@ analytics.track('Promotion Clicked', { }); ``` -> info "Note" +> info "" > The `Promotion Clicked` event is aliased to the [`Clicked Promotion` event](/docs/connections/destinations/catalog/google-analytics/#measuring-promotions). ## Core Ordering @@ -316,7 +316,7 @@ Fire this event when a visitor clicks a product. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|---------------------------------------------------------| | product_id | String | Database id of the product being viewed | | sku | String | Sku of the product being viewed | @@ -351,7 +351,7 @@ analytics.track('Product Clicked', { }); ``` -> info "Note" +> info "" > - The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. > - The `Product Clicked` event is aliased to the `Clicked Product` event from [e-commerce v1 spec](/docs/connections/spec/ecommerce/). @@ -361,7 +361,7 @@ Fire this event when a visitor views a product. That view might happen on a page This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|---------------------------------------------------------| | product_id | String | Database id of the product being viewed | | sku | String | Sku of the product being viewed | @@ -400,7 +400,7 @@ analytics.track('Product Viewed', { }); ``` -> info "Note" +> info "" > - The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. > - The `Product Viewed` event is aliased to the `Viewed Product` event from [e-commerce v1 spec](/docs/connections/spec/ecommerce/). @@ -410,7 +410,7 @@ Fire this event when a visitor adds a product to their shopping cart. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|---------------------------------------------------------| | cart_id | String | Cart ID to which the product was added to | | product_id | String | Database id of the product being viewed | @@ -447,7 +447,7 @@ analytics.track('Product Added', { }); ``` -> info "Note" +> info "" > - The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. > - The `Product Added` event is aliased to the `Added Product` event from [e-commerce v1 spec](/docs/connections/spec/ecommerce/). @@ -457,10 +457,10 @@ Fire this event when a visitor removes a product from their shopping cart. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|---------------------------------------------------------| | cart_id | String | Cart ID to which the product was removed from | -| product_id | String | Database id of the product being viewed | +| product_id | String | Database ID of the product being viewed | | sku | String | Sku of the product being viewed | | category | String | Product category being viewed | | name | String | Name of the product being viewed | @@ -493,7 +493,7 @@ analytics.track('Product Removed', { }); ``` -> info "Note" +> info "" > - The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. > - The `Product Removed` event is aliased to the `Removed Product` event from [e-commerce v1 spec](/docs/connections/spec/ecommerce/#added---removed-product). @@ -501,12 +501,12 @@ analytics.track('Product Removed', { Fire this event when a visitor views a shopping cart. -> info "Note" +> info "" > Not all destinations accept arrays as properties. Refer to individual destination documentation for more information on supported events and properties. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------------|----------|---------------------------------------------------------| | cart_id | String | Shopping cart ID | | products | Array | Products displayed in the product list | @@ -555,14 +555,14 @@ analytics.track('Cart Viewed', { Fire this event whenever an order/transaction was started. Fire on the page that the customer lands on after they press the checkout button. -> info "Note" +> info "" > Not all destinations accept arrays as properties. Refer to individual destination documentation for more information on supported events and properties. Be sure to **include all items in the cart as event properties**, with the same properties from the previous calls, like so: This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | order_id | String | Order/transaction ID | | affiliation | String | Store or affiliation from which this transaction occurred (for example, Google Store) | @@ -574,7 +574,7 @@ This event supports the following semantic properties: | coupon | String | Transaction coupon redeemed with the transaction | | currency | String | [Currency code](https://support.google.com/analytics/answer/6205902#supported-currencies){:target="_blank"} associated with the transaction | | products | Array | Products in the order | -| products.$.product_id | String | Database id of the product being viewed | +| products.$.product_id | String | Database ID of the product being viewed | | products.$.sku | String | Sku of the product being viewed | | products.$.category | String | Product category being viewed | | products.$.name | String | Name of the product being viewed | @@ -624,7 +624,7 @@ analytics.track('Checkout Started', { }); ``` -> info "Note" +> info "" > - The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. > - The `Checkout Started` event is aliased to the `Started Order` event from [Segment's GA Enhanced E-Commerce destinations](/docs/connections/destinations/catalog/google-analytics/#measuring-checkout-steps). @@ -634,7 +634,7 @@ Fire this event whenever a checkout step is viewed. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------|----------|----------------------------------------------------| | checkout_id | String | Checkout transaction ID | | step | Number | Number representing a step in the checkout process | @@ -652,12 +652,12 @@ analytics.track('Checkout Step Viewed', { }); ``` -> info "Note" +> info "" > `shipping_method` and `payment_method` are semantic properties. If you want to send that information, do so in this exact spelling. You can have as many or as few steps in the checkout funnel as you'd like. Note that you'll still need to track the `Order Completed` event per Segment's standard [e-commerce tracking API](/docs/connections/spec/ecommerce/v2/#order-completed) after you've tracked the checkout steps. -> info "Note" +> info "" > The `Checkout Step Viewed` event is aliased to the `Viewed Checkout Step` event from [Segment's GA Enhanced E-Commerce destinations](/docs/connections/destinations/catalog/google-analytics/#measuring-checkout-steps). ### Checkout Step Completed @@ -666,7 +666,7 @@ Fire this event whenever a checkout step is completed. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------|----------|----------------------------------------------------| | checkout_id | String | Checkout transaction ID | | step | Number | Number representing a step in the checkout process | @@ -685,12 +685,12 @@ analytics.track('Checkout Step Completed', { }); ``` -> info "Note" +> info "" > `shipping_method` and `payment_method` are semantic properties. If you want to send that information, do so in this exact spelling. You can have as many or as few steps in the checkout funnel as you'd like. Note that you'll still need to track the `Order Completed` event per Segment's standard [e-commerce tracking API](/docs/connections/spec/ecommerce/v2/#order-completed) after you've tracked the checkout steps. -> info "Note" +> info "" > The `Checkout Step Completed` event is aliased to the `Completed Checkout Step` event from [Segment's GA Enhanced E-Commerce destinations](/docs/connections/destinations/catalog/google-analytics/#measuring-checkout-steps). @@ -700,7 +700,7 @@ Fire this event whenever payment information has been successfully entered. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------|----------|----------------------------------------------------| | checkout_id | String | Checkout transaction ID | | order_id | String | Order ID (optional) | @@ -717,7 +717,7 @@ analytics.track('Payment Info Entered', { }); ``` -> info "Note" +> info "" > `shipping_method` and `payment_method` are semantic properties. If you want to send that information, do so in this exact spelling. You can have as many or as few steps in the checkout funnel as you'd like. Note that you'll still need to track the `Order Completed` event per Segment's standard [e-commerce tracking API](/docs/connections/spec/ecommerce/v2/#order-completed) after you've tracked the checkout steps. @@ -726,14 +726,14 @@ You can have as many or as few steps in the checkout funnel as you'd like. Note Fire this event whenever an order/transaction was updated. -> info "Note" +> info "" > Not all destinations accept arrays as properties. Refer to individual destination documentation for more information on supported events and properties. Be sure to **include all items in the cart as event properties**, with the same properties from the previous calls, like so: This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | order_id | String | Order/transaction ID | | affiliation | String | Store or affiliation from which this transaction occurred (for example, Google Store) | @@ -743,9 +743,9 @@ This event supports the following semantic properties: | tax | Number | Total tax associated with the transaction | | discount | Number | Total discount associated with the transaction | | coupon | String | Transaction coupon redeemed with the transaction | -| currency | String | [Currency code](https://support.google.com/analytics/answer/6205902#supported-currencies) associated with the transaction | +| currency | String | [Currency code](https://support.google.com/analytics/answer/6205902#supported-currencies){:target="_blank"} associated with the transaction | | products | Array | Products in the order | -| products.$.product_id | String | Database id of the product being viewed | +| products.$.product_id | String | Database ID of the product being viewed | | products.$.sku | String | Sku of the product being viewed | | products.$.category | String | Product category being viewed | | products.$.name | String | Name of the product being viewed | @@ -794,7 +794,7 @@ analytics.track('Order Updated', { }); ``` -> info "Note" +> info "" > - The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. > - The `Order Updated` event is aliased to the `Updated Order` event from [Segment's GA Enhanced E-Commerce destinations](/docs/connections/destinations/catalog/google-analytics/#measuring-checkout-steps). @@ -803,14 +803,14 @@ analytics.track('Order Updated', { Fire this event whenever an order/transaction was successfully completed by the customer. -> info "Note" +> info "" > Not all destinations accept arrays as properties. Refer to individual destination documentation for more information on supported events and properties. Be sure to **include all items in the cart as event properties**, with the same properties from the previous calls, like so: This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | checkout_id | String | Checkout ID | | order_id | String | Order/transaction ID | @@ -822,9 +822,9 @@ This event supports the following semantic properties: | tax | Number | Total tax associated with the transaction | | discount | Number | Total discount associated with the transaction | | coupon | String | Transaction coupon redeemed with the transaction | -| currency | String | [Currency code](https://support.google.com/analytics/answer/6205902#supported-currencies) associated with the transaction | +| currency | String | [Currency code](https://support.google.com/analytics/answer/6205902#supported-currencies){:target="_blank"} associated with the transaction | | products | Array | Products in the order | -| products.$.product_id | String | Database id of the product being viewed | +| products.$.product_id | String | Database ID of the product being viewed | | products.$.sku | String | Sku of the product being viewed | | products.$.category | String | Product category being viewed | | products.$.name | String | Name of the product being viewed | @@ -888,7 +888,7 @@ Be sure to **include all items in the cart as event properties**, with the same This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|----------------------| | order_id | String | Order/transaction ID | @@ -931,14 +931,14 @@ analytics.track('Order Refunded', { Fire this event whenever an order/transaction was cancelled. -> info "Note" +> info "" > Not all destinations accept arrays as properties. Refer to individual destination documentation for more information on supported events and properties. Be sure to **include all items in the cart as event properties**, with the same properties from the previous calls. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------------|----------|---------------------------------------------------------------------------------------------------------------------------| | order_id | String | Order/transaction ID | | affiliation | String | Store or affiliation from which this transaction occurred (for example, Google Store) | @@ -948,9 +948,9 @@ This event supports the following semantic properties: | tax | Number | Total tax associated with the transaction | | discount | Number | Total discount associated with the transaction | | coupon | String | Transaction coupon redeemed with the transaction | -| currency | String | [Currency code](https://support.google.com/analytics/answer/6205902#supported-currencies) associated with the transaction | +| currency | String | [Currency code](https://support.google.com/analytics/answer/6205902#supported-currencies){:target="_blank"} associated with the transaction | | products | Array | Products in the order | -| products.$.product_id | String | Database id of the product being viewed | +| products.$.product_id | String | Database ID of the product being viewed | | products.$.sku | String | Sku of the product being viewed | | products.$.category | String | Product category being viewed | | products.$.name | String | Name of the product being viewed | @@ -1000,7 +1000,7 @@ analytics.track('Order Cancelled', { }); ``` -> info "Note" +> info "" > The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. ## Coupons @@ -1013,7 +1013,7 @@ Fire this event whenever a coupon is entered either on a cart or on an order/tra This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|-------------------------------------| | order_id | String | Order/transaction ID, if applicable | | cart_id | String | Cart ID, if applicable | @@ -1030,7 +1030,7 @@ analytics.track('Coupon Entered', { }); ``` -> info "Note" +> info "" > This has no effect in GA enhanced e-commerce, as that destination pulls from the `coupon` field on the order events. Refer to Segment's [Google Analytic documentation](/docs/connections/destinations/catalog/google-analytics/) for more information. ### Coupon Applied @@ -1039,7 +1039,7 @@ Fire this event whenever a coupon is successfully applied to either a cart or an This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|----------------------------------------------| | order_id | String | Order/transaction ID, if applicable | | cart_id | String | Cart ID, if applicable | @@ -1059,7 +1059,7 @@ analytics.track('Coupon Applied', { }); ``` -> info "Note" +> info "" > This has no effect in GA enhanced e-commerce, as that destination pulls from the `coupon` field on the order events. Refer to Segment's [Google Analytic documentation](/docs/connections/destinations/catalog/google-analytics/) for more information. ### Coupon Denied @@ -1068,7 +1068,7 @@ Fire this event whenever a coupon is denied from either a cart or an order/trans This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|-------------------------------------| | order_id | String | Order/transaction ID, if applicable | | cart_id | String | Cart ID, if applicable | @@ -1088,7 +1088,7 @@ analytics.track('Coupon Denied', { }); ``` -> info "Note" +> info "" > This has no effect in GA enhanced e-commerce, as that destination pulls from the `coupon` field on the order events. Refer to Segment's [Google Analytic documentation](/docs/connections/destinations/catalog/google-analytics/) for more information. ### Coupon Removed @@ -1097,7 +1097,7 @@ Fire this event whenever a coupon is removed from either a cart or an order/tran This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|----------------------------------------------| | order_id | String | Order/transaction ID, if applicable | | cart_id | String | Cart ID, if applicable | @@ -1117,7 +1117,7 @@ analytics.track('Coupon Removed', { }); ``` -> info "Note" +> info "" > This has no effect in GA enhanced e-commerce, as that destination pulls from the `coupon` field on the order events. Refer to Segment's [Google Analytic documentation](/docs/connections/destinations/catalog/google-analytics/) for more information. ## Wishlisting @@ -1130,11 +1130,11 @@ Fire this event when a customer adds a product to their wish list. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |---------------|----------|---------------------------------------------------------| | wishlist_id | String | Wishlist ID to which the product was added to | | wishlist_name | String | Wishlist name to which the product was added to | -| product_id | String | Database id of the product being viewed | +| product_id | String | Database ID of the product being viewed | | sku | String | Sku of the product being viewed | | category | String | Product category being viewed | | name | String | Name of the product being viewed | @@ -1169,7 +1169,7 @@ analytics.track('Product Added to Wishlist', { }); ``` -> info "Note" +> info "" > The `sku` and `product_id` do not have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. ### Product Removed from Wishlist @@ -1178,11 +1178,11 @@ Fire this event when a customer removes a product from their wish list. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |---------------|----------|---------------------------------------------------------| | wishlist_id | String | Wishlist ID to which the product was added to | | wishlist_name | String | Wishlist name to which the product was added to | -| product_id | String | Database id of the product being viewed | +| product_id | String | Database ID of the product being viewed | | sku | String | Sku of the product being viewed | | category | String | Product category being viewed | | name | String | Name of the product being viewed | @@ -1216,7 +1216,7 @@ analytics.track('Product Removed from Wishlist', { }); ``` -> info "Note" +> info "" > The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. ### Wishlist Product Added to Cart @@ -1225,7 +1225,7 @@ Fire this event when a customer moves a product from their wish list to their ca This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |---------------|----------|---------------------------------------------------------| | wishlist_id | String | Wishlist ID to which the product was added to | | wishlist_name | String | Wishlist name to which the product was added to | @@ -1266,7 +1266,7 @@ analytics.track('Wishlist Product Added to Cart', { }); ``` -> info "Note" +> info "" > The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. ## Sharing @@ -1279,7 +1279,7 @@ Fire this event when a customer shares a product. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |---------------|----------|-----------------------------------------| | share_via | String | Method of sharing | | share_message | String | Message that the sender sent | @@ -1314,19 +1314,19 @@ analytics.track('Product Shared', { }); ``` -> info "Note" +> info "" > The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. ### Cart Shared Fire this event when a customer shares a shopping cart. -> info "Note" +> info "" > Not all destinations accept arrays as properties. Refer to individual destination docs for more information on supported events and properties. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |-----------------------|----------|----------------------------------------| | share_via | String | Method of sharing | | share_message | String | Message that the sender sent | @@ -1360,7 +1360,7 @@ Fire this event when a customer reviews a product. This event supports the following semantic properties: -| **Property** | **Type** | **Description** | +| Property | Type | Description | |--------------|----------|-----------------| | product_id | String | Product's ID | | review_id | String | Review ID | From 6269aa652842ea3e75f2c696d4da5d070dde382b Mon Sep 17 00:00:00 2001 From: rchinn1 Date: Wed, 3 Sep 2025 15:32:22 -0700 Subject: [PATCH 2/3] Build preview [netlify-build] --- src/connections/spec/ecommerce/v2.md | 1 - 1 file changed, 1 deletion(-) diff --git a/src/connections/spec/ecommerce/v2.md b/src/connections/spec/ecommerce/v2.md index 63316daaf8..5cfb0ce7e4 100644 --- a/src/connections/spec/ecommerce/v2.md +++ b/src/connections/spec/ecommerce/v2.md @@ -20,7 +20,6 @@ Here is a list of supported events for our various categories within the custome | Product List Viewed | User viewed a product list or category | | Product List Filtered | User filtered a product list or category | - ### Promotions overview | Action | Description | From c7e388dfba8a01712f641b6401ff5e568df65277 Mon Sep 17 00:00:00 2001 From: rchinn1 Date: Wed, 3 Sep 2025 15:43:08 -0700 Subject: [PATCH 3/3] quick fixes --- src/connections/spec/ecommerce/v2.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/connections/spec/ecommerce/v2.md b/src/connections/spec/ecommerce/v2.md index 5cfb0ce7e4..21ce943b00 100644 --- a/src/connections/spec/ecommerce/v2.md +++ b/src/connections/spec/ecommerce/v2.md @@ -20,6 +20,7 @@ Here is a list of supported events for our various categories within the custome | Product List Viewed | User viewed a product list or category | | Product List Filtered | User filtered a product list or category | + ### Promotions overview | Action | Description | @@ -273,7 +274,7 @@ analytics.track('Promotion Viewed', { }); ``` -> info "Note" +> info "" > The `Promotion Viewed` event is aliased to the [`Viewed Promotion` event](/docs/connections/destinations/catalog/google-analytics/#measuring-promotions). @@ -875,7 +876,7 @@ analytics.track('Order Completed', { }); ``` -> info "Note" +> info "" > - The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`. > - The `Order Completed` event is aliased to the `Completed Order` event from [E-Commerce spec v1 - 5/11/16](/docs/connections/spec/ecommerce/). @@ -922,7 +923,7 @@ analytics.track('Order Refunded', { ``` -> info "Note" +> info "" > The `sku` and `product_id` don't have to be different. If they are different, typically the `product_id` is a database identifier, like `9714107479` and the `sku` is a public-facing identifier like `SEG-02`.