Littledata's Shopify to Segment connection 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. You can send this data to a connected data warehouse like Snowflake; email and customer communications tools like Klaviyo, Iterable and Braze; analytics destinations such as Mixpanel and Kissmetrics; and many more destinations.
During the installation process:
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:
Using a headless Shopify setup? Follow the setup steps for headless Shopify tracking with Littledata.
These are the events that Littledata sends from Shopify to Segment. These events will show up as tables in your warehouse, and as regular events in your other Segment destinations.
Looking for complete property and event details? Don't miss the complete tracking schema in Google Sheets. Note: this can be uploaded directly into Segment Protocols.
Below is a table of events that Littledata sends to Segment through the analytics.js library. These events will show up as tables in your warehouse, and as regular events in your other device-mode Destinations.
|Cart Viewed||User has viewed the /cart page|
|Page Viewed||User has viewed a page|
|Product List Viewed||User has viewed a product as they scroll down the collection page|
|Product Clicked||User has clicked a product within a product list|
|Product Viewed||User has viewed a product page|
|Product Image Clicked||User has clicked a product image|
|Product Shared||User has shared a product via social links|
|Products Searched||User has searched for products (with search |
|Registration Viewed||User has viewed the /account/register page|
|Thankyou Page Viewed||User has viewed the thank you page after completing an order *|
* This is less reliable than the de-duplicated
Order Completed event sent from Littledata's servers, but you can use it in device-mode destinations to trigger a conversion.
shipping_method properties are not available with this event.
You can opt out of device-mode pageviews or events in the data pipeline settings.
Server-side events are tracked by Littledata servers from Shopify and passed onto any destination in cloud mode.
|Product Added||User has added a product to the cart, and left it in the cart for more than 10 seconds|
|Product Removed||User has removed a product from the cart|
|Checkout Started||User has started checkout|
|Checkout Step Viewed||User has viewed a step in the checkout|
|Checkout Step Completed||User has completed a step in the checkout|
|Customer Created||User added as a customer|
|Payment Info Entered||User has entered payment info|
|Coupon Applied||Sent with Checkout Step Completed or Order Completed when user has applied a coupon|
|Order Completed||Customer has completed an order **|
|Post Purchase Upsell||Customer accepts the upsell. Will contain only the newly added products.|
|Order Cancelled||Admin has cancelled an order (including the |
|POS Order Placed||User has placed an order via Shopify POS|
|Payment Failure||User completed checkout step 3 but the payment method failed (i.e. the card details were valid but the charge did not succeed)|
|Customer Enabled||User has confirmed their email address and created a Shopify customer account with |
|Fulfillment Created||Order fulfillment is created (including |
|Fulfillment Updated||Order fulfillment status has changed (including |
** Order Completed event may be delayed by up to 40 seconds to wait for tags applied after the order was created
In Littledata's app you can choose which of the following fields you want to send as the
userId for known customers:
createHashmethod) to match your other sources.
For Segment Unify we also send
shopify_customer_id as an externalID for advanced matching.
For every event where there is an identifiable Shopify customer (from both the client and the server) we also send an Identify call to build a customer profile in Unify and trigger updates in CRM systems connected to Segment. This identification happens when the customer logs into the storefront, on the last step of the checkout, with the order, and also after purchase with any customer update in Shopify admin.
Littledata includes the following traits with an Identify call:
|Property Name||Description||Property Type|
|userId||Chosen user identifier, defaulting to Shopify Customer ID||Double|
|createdAt||Date customer record was created||Date|
|customerLifetimeValue||Total spend of customer on the Shopify store||Double|
|default_address.street||The customer's default street address||String|
|default.address.postalCode||The customer's ZIP / post code||String|
|default_address.state||The customer's state address||String|
|default_address.country||The customer's country||String|
|Customer's email address||String|
|email_consent_state||If the user has consented to email marketing (mapping to EmailMarketingState)||String, Null|
|email_opt_in_level||Level of user's opt in email marketing (mapping to MarketingOptInLevel)||String, Null|
|firstName||Customer's first name||String|
|lastName||Customer's last name||String|
|phone||Customer's phone number||String|
|purchaseCount||Number of orders by this customer||Integer|
|sms_consent_state||If the user has consented to SMS marketing (mapping to SmsMarketingState)||String, Null|
|sms_opt_in_level||Level of user's opt in to SMS marketing (mapping to MarketingOptInLevel)||String, Null|
|state||Shopify customer state - enabled, disabled, invited to create an account or customer declined||String|
|tags||Custom tags applied to the customer||String|
|verified_email||Whether the customer has verified their email||Boolean|
Email marketing platforms such as Klaviyo, Iterable and Hubspot require an
traits() object (in device-mode) or from the Shopify customer record (in cloud-mode).
To support seamless customer tracking in analytics destinations such as Mixpanel, Vero and Kissmetrics, Littledata ensures the pre-checkout
anonymousId is added as an alias of the
userId (used from checkout step 2 onwards).
These are the properties which may be included in the events listed above. See the Track (eCommerce) tab of the event schema for exactly which properties are sent with which events.
|A comma-separated list of order tags. Untagged orders use ||String|
|The ID of the Shopify cart||String|
|The ID of the checkout session||String|
|The user's Google Analytics Client ID||String|
|The user's IP address||String|
|Comma-separated string of discount coupons used, if applicable||String|
|The currency of the order||String|
|The discounted amount||Float|
|Shopify email address (after checkout step 2), or email submitted on a storefront form||String|
|Lifetime revenue of the customer in Shopify||String|
|Location ID of the Point of Sale||Integer|
|The ID of the order is by default the Shopify order name||String|
|The payment gateway used by the customer||String|
|The payment method chosen for checkout||String|
|The user's local currency||String|
|The order total in local currency||String|
|A list of all the product at that step of the funnel||Array|
|Total purchase count for the customer||Integer|
|Product revenue (excluding discounts, shipping and tax) *||Float|
|Unique property to identify events sent by Littledata||String|
|Shipping method chosen for checkout||String|
|Shopify’s identifier for the customer||Integer|
|The source of the order (e.g. ||String|
|The revenue associated with a Subscription Event||Float|
|Total after discounts but before taxes and shipping||Float|
|The amount of tax on the order||Float|
|Total value of the order||Float|
|Chosen user identifier, defaulting to Shopify Customer ID||String|
revenue is available only with the Order Completed event, and only if the store opts in via the Littledata application. Revenue is a reserved property in many Segment destinations. Opting in will override the
total property sent to Google Analytics.
Each product in the
products array, or Product Viewed and Product Added events, will have the following properties:
|The brand of the product (Shopify vendor)||String|
|The category of the product (defaults to all)||String|
|The product price before any discount||String|
|Coupon code associated with the product||String|
|The URL of the first product image||String|
|The ID of the product collection (for List Views and Clicks)||String|
|The product position in the collection (for List Views and Clicks)||Integer|
|The product price||Float|
|Shopify product ID||String|
|The quantity of this product||Integer|
|Custom properties of purchased products||Array|
|Also Shopify product ID||String|
|The Shopify variant ID||String|
|The product SKU||String|
|The URL of the product page||String|
|The product variant name||String|
All recurring orders in the Shopify checkout, from any subscription app, are tracked as Order Completed events.
|Subscription Created||A customer has created a subscription (with |
|Subscription Updated||A customer has updated a subscription (with |
|Subscription Cancelled||A customer has cancelled a subscription (with |
|Order Processed||A recurring order in processed|
|Charge Failed||A recurring charge failed (with |
|Charge Max Tries Reached||Maximum tries to charge customer has been reached|
|Payment Method Updated||Customer has updated the payment method|
You can customize Littledata's Shopify source from the data pipeline settings in the Littledata admin. The general settings affect how we handle details such as orders, products and pageviews. The more advanced settings include:
Any cookie set on a landing page (e.g. a session identifier or marketing campaign name) can be sent on to Segment with an identify call.
If you have a proxy CDN setup to load Segment's AnalyticsJS library from your own domain you can specify it here.
View all available data pipeline settings >>>