Merge pull request segmentio#2354 from edwardupton/littledata-docs-update

Update Shopify connection overview

Author: forstisabella

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

@@ -6,13 +6,29 @@ redirect_from:
 
 <!-- LR Note: the working copy of the source catalog YML we built on showed this in the `website` source though as of Nov 18 it's labeled cloud-source -->
 
-Littledata is a smart analytics app that automates e-commerce tracking. Littledata's [Shopify-to-Segment connection](https://blog.littledata.io/help/posts/segment-overview/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} automatically tracks key e-commerce events on a Shopify or Shopify Plus store, so you can use Shopify as a source in your Segment workspace.
+Littledata's [Shopify to Segment connection](https://blog.littledata.io/help/posts/segment-overview/){:target="_blank"} uses a combination of client-side (browser) and server-side tracking to ensure 100% accurate data about your Shopify store in Segment. Littledata automatically integrates with Shopify and Shopify Plus sites to capture every customer touchpoint, including sales, marketing, customer and product performance data.
 
-Littledata is available as an independent [Shopify App](https://apps.shopify.com/segment-com-by-littledata){:target="_blank"}. When you install the Littledata app on your store, Littledata does two things:
+Littledata is available as an independent [Shopify App](https://apps.shopify.com/segment-com-by-littledata).
 
-1. It inserts a smart tracking script to your store's front end. You can use this script with any Shopify site, and uses Analytics.js under the hood to send data in a spec-compliant manner to Segment.
+#### Client-side (device mode) tracking
 
-2. The app also sets up server-side webhook forwarding to ensure 100% accuracy of important Customer and Order data.
+During the [installation process](https://blog.littledata.io/help/posts/segment-installation-guide/), Littledata adds a `LittledataLayer.liquid` snippet to all pages (included in `theme.liquid`) on your Shopify store. The benefits of this approach include:
+
+- Segment's analytics.js V1 library is loaded on all pages, except for the checkout
+- Includes a LittledataLayer data layer for all pages
+- Loads a minified tracking script, hosted on a content delivery network (CDN)
+- Enables sending of device-mode ecommerce events to all Segment destinations
+- Segment's anonymous ID and Google Analytics' client ID is passed to our servers to ensure consistent user journey tracking
+
+#### Server-side (cloud mode) tracking
+
+During the Segment connection setup, Littledata also adds a set of webhooks to your Shopify store. When a customer interacts with your store these changes are relayed server-side from Shopify to Littledata to Segment. The advantages to this approach are:
+
+- 100% event capture for adds to cart, checkout steps, sales and refunds/returns
+- Customer data (e.g. email) securely relayed server-side
+- No extra scripts on the sensitive and secure checkout pages
+- Accurate marketing attribution, even when customers use ad-blockers or cookie opt-outs
+- Supports cloud-mode destinations such as [Facebook Conversions API](/docs/connections/destinations/catalog/facebook-pixel-server-side/)
 
 Here's an architecture diagram that shows how the Littledata app mediates data flow between Shopify and Segment.
 
@@ -90,7 +106,7 @@ Below is a table of events that **Shopify by Littledata** sends to Segment from
 In the Littledata application you can choose which of the following fields you want to send as the `userId` for known customers:
 
 - **Shopify customer ID** (default) - Recommended if you have a simple Shopify setup with minimal integrations.
-- **Hashed email** - The MD5 email hash is useful if you have other marketing platforms sending traffic where you know the email of the visitor (e.g. email marketing like Bronto or Marketo), but not their Shopify customer ID.
+- **Hashed email** - The MD5 email hash is useful if you have other marketing platforms sending traffic where you know the email of the visitor (e.g. email marketing like Bronto or Marketo), but not their Shopify customer ID. We use an unsalted MD5 hash (\`createHash\` method) to match your other sources.
 - **Email** - The email identifier is recommended when other platforms use the email and can’t hash it, and you are comfortable with the privacy implications.
 - **None** (no identifier) - Choose “none” if user identity is already handled by your Segment implementation and you only need the extra events powered by Littledata's Shopify source.
 
@@ -218,9 +234,9 @@ Each item in the `products` array, or Product Viewed and Product Added events, w
 
 With an [annual Littledata Plus plan](https://www.littledata.io/app/enterprise){:target="_blank"} you can import all Shopify orders and refunds from before you started using Segment, to sync with destinations that support timestamped events (for example, a data warehouse). This enables you to build a complete customer history in your chosen destination.
 
-## Advanced Device-mode settings
+## Advanced settings
 
-You can edit the LittledataLayer object in your Shopify theme to manually change these advanced settings. For more information, see the [Shopify tracker GitHub repository](https://github.com/littledata/shopify-tracker#segment-configuration){:target="_blank"}.
+You can edit these data pipeline settings within Littledata's app.
 
 ### cookiesToTrack