Merge pull request #1398 from segmentio/littledata-docs-update

Add device-mode events

Author: markzegarelli

src/connections/sources/catalog/libraries/website/shopify-littledata/index.md

@@ -41,24 +41,19 @@ Below is a table of events that **Shopify by Littledata** sends to Segment throu
 
 | Event Name            | Description                                                           |
 | --------------------- | --------------------------------------------------------------------- |
-| Page Viewed           | The user has viewed a page                                            |
-| Product Clicked       | The user has clicked a product within a product list                  |
-| Product Image Clicked | The user has clicked a product image                                  |
-| Product List Viewed   | The user has viewed a product as they scroll down the collection page |
-| Product Shared        | User has shared a product through social links                        |
-| Product Viewed        | The user has viewed a product page                                    |
-| Thank you Page Viewed | User has viewed the thank you page after completing an order \*       |
-
-> note "" \* This is less reliable than the de-duplicated `Order Completed` event sent from the Littledata servers, but you can use it in device-mode destinations to trigger a conversion. The `payment_method` and `shipping_method` properties are not available with this event.
-
-In addition to the events tracked as standard, the following hits can be tracked based on page path:
-
-| Event Name             | Description                                 |
-| ---------------------- | ------------------------------------------- |
-| Blog Viewed            | A prospect has viewed the blog              |
-| Cart Viewed            | A prospect has viewed the cart              |
-| Registration Completed | A prospect has completed registration       |
-| Registration Viewed    | A prospect has viewed the registration page |
+| Cart Viewed           | A user has viewed the /cart page                                      |
+| Page Viewed           | A user has viewed any page                                            |
+| Product Clicked       | A user has clicked a product within a product list                    |
+| Product Image Clicked | A user has clicked a product image                                    |
+| Product List Viewed   | A user has viewed a product as they scroll down the collection page   |
+| Product Shared        | A user has shared a product through social links                      |
+| Product Viewed        | A user has viewed a product page                                      |
+| Products Searched     | A user has searched for products (with search `query`)                |
+| Registration Viewed   | A user has viewed the /account/register page                          |
+| Thank you Page Viewed | A user has viewed the thank you page after completing an order \*     |
+
+> note ""
+> \*  This is less reliable than the de-duplicated `Order Completed` event sent from the Littledata servers, but you can use it in device-mode destinations to trigger a conversion. The `payment_method` and `shipping_method` properties are not available with this event.
 
 ## Cloud-mode Events
 
@@ -127,7 +122,7 @@ Email marketing platforms such as [Klaviyo](/docs/connections/destinations/catal
 
 ## Alias Calls
 
-To support seamless customer tracking the [Mixpanel](/docs/connections/destinations/catalog/mixpanel/#alias), [Vero](/docs/connections/destinations/catalog/vero/#alias) and [KISSMetrics](docs/connections/destinations/catalog/kissmetrics/#alias) destinations, Littledata ensures the pre-checkout `anonymousId` is added as an alias of the `userId` (used from checkout step 2 onwards).
+To support seamless customer tracking the [Mixpanel](/docs/connections/destinations/catalog/mixpanel/#alias), [Vero](/docs/connections/destinations/catalog/vero/#alias) and [KISSMetrics](/docs/connections/destinations/catalog/kissmetrics/#alias) destinations, Littledata ensures the pre-checkout `anonymousId` is added as an alias of the `userId` (used from checkout step 2 onwards).
 
 ## Subscription e-commerce Events