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
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/libraries/website/shopify-littledata/index.md
+27-28Lines changed: 27 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ redirect_from:
6
6
7
7
<!-- 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 -->
8
8
9
-
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.
9
+
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.
10
10
11
11
Littledata is available as an independent [Shopify App](https://apps.shopify.com/segment-com-by-littledata).
12
12
@@ -40,20 +40,20 @@ Here's an architecture diagram that shows how the Littledata app mediates data f
40
40
## Getting Started
41
41
42
42
1.**Login** to your Shopify Store account.
43
-
2. Go the [Shopify app store listing](https://apps.shopify.com/segment-com-by-littledata){:target="_blank"} for **_Segment.com by Littledata_**.
43
+
2. Go the [Shopify app store listing](https://apps.shopify.com/segment-com-by-littledata){:target="_blank"} for \*\*\_Segment.com by Littledata_\*\*.
44
44
45
45
3. Click **Add app** to begin the installation process.
46
46
4.**Sign up** for a Littledata account using an email address, Google login or Facebook login. _More team members can be added to the subscription after completing the installation process._
47
47
5. Add the [**Segment write key**](/docs/connections/find-writekey/) for the source that is going to send data in the **input field**.
48
48
49
-
6. Choose either an **Automatic** or a **Manual** install. _Automatic installs work in most instances, but if you choose to do a manual install, just follow [this guide](https://blog.littledata.io/help/posts/segment-installation-guide/){:target="_blank"}._
49
+
6. Choose either an **Automatic** or a **Manual** install. _Automatic installs work in most instances, but if you choose to do a manual install, just follow [this guide](https://blog.littledata.io/help/posts/segment-installation-guide/){:target="\_blank"}._
50
50
51
51
7. Segment's **analytics.js** library, Littledata **tracking script** and **webhooks** will be automatically applied to the store and the installation process will then be complete.
52
52
53
53
54
54
## Event schema
55
55
56
-
This source has a full [tracking plan and event schema](https://docs.google.com/spreadsheets/d/1aljowRhMU9_7uGXmcipbP1Y14S4cOSdXGQA2Vx7BHko/copy){:target="_blank"} in Google Sheets, which is ready to [upload into Protocols](/docs/protocols/apis-and-extensions/#google-sheets-tracking-plan-uploader).
56
+
This source has a full [tracking plan and event schema](https://docs.google.com/spreadsheets/d/1aljowRhMU9_7uGXmcipbP1Y14S4cOSdXGQA2Vx7BHko/copy){:target="\_blank"} in Google Sheets, which is ready to [upload into Protocols](/docs/protocols/apis-and-extensions/#google-sheets-tracking-plan-uploader).
57
57
58
58
## Device-mode events
59
59
@@ -83,23 +83,23 @@ The source also respects [GDPR-compliant cookie](https://blog.littledata.io/2021
83
83
84
84
Below is a table of events that **Shopify by Littledata** sends to Segment from Littledata's servers. These events appear as tables in your warehouse, and as regular events in your other Destinations that support cloud-mode. They include the `anonymousId` that links them to the device-mode events where the event was part of a previous user session, or associated with a `userId` that was previously linked with an `anonymousId`. See Littledata's [troubleshooting guide on attribution](https://blog.littledata.io/help/posts/troubleshooting-marketing-attribution-for-shopify/) for more details.
| Checkout Started | A user has started checkout |
89
-
| Checkout Step Completed | A user has completed a step in the checkout |
90
-
| Coupon Applied | Sent with Checkout Step Completed or Order Completed when user has applied a coupon |
91
-
| Customer Created | User added as a customer |
92
-
| Customer Enabled (v2) | A user has confirmed their email address and created a Shopify customer account with verified_email set as true |
93
-
| Fulfillment Created (v2) | An order fulfillment status has changed (including status, tracking_numbers and tracking_urls where the shipping integration allows) |
94
-
| Fulfillment Updated (v2) | An order fulfillment status has changed (including status, tracking_numbers and tracking_urls where the shipping integration allows) |
95
-
| Order Cancelled (v2) | An admin has cancelled an order (including the cancel_reason) |
96
-
| Order Completed | A prospect has completed an order |
97
-
| Order Refunded | An order has been refunded |
98
-
| POS Order Placed (v2) | A user has placed an order through Shopify POS |
99
-
| Payment Failure (v2) | A user completed checkout step 3 but the payment method failed (for example, the card details were valid but the [charge did not succeed(https://stripe.com/docs/testing#cards-responses)]) |
100
-
| Payment Info Entered | A user has entered payment info |
101
-
| Product Added | A user has added a product to the cart, and left it in the cart for more than 10 seconds |
102
-
| Product Removed | A user has removed a product from the cart |
| Checkout Started | A user has started checkout |
89
+
| Checkout Step Completed | A user has completed a step in the checkout |
90
+
| Coupon Applied | Sent with Checkout Step Completed or Order Completed when user has applied a coupon |
91
+
| Customer Created | User added as a customer |
92
+
| Customer Enabled (v2) | A user has confirmed their email address and created a Shopify customer account with verified_email set as true |
93
+
| Fulfillment Created (v2) | An order fulfillment status has changed (including status, tracking_numbers and tracking_urls where the shipping integration allows) |
94
+
| Fulfillment Updated (v2) | An order fulfillment status has changed (including status, tracking_numbers and tracking_urls where the shipping integration allows) |
95
+
| Order Cancelled (v2) | An admin has cancelled an order (including the cancel_reason) |
96
+
| Order Completed | A prospect has completed an order |
97
+
| Order Refunded | An order has been refunded |
98
+
| POS Order Placed (v2) | A user has placed an order through Shopify POS |
99
+
| Payment Failure (v2) | A user completed checkout step 3 but the payment method failed (for example, the card details were valid but the [charge did not succeed](https://stripe.com/docs/testing#cards-responses)|
100
+
| Payment Info Entered | A user has entered payment info |
101
+
| Product Added | A user has added a product to the cart, and left it in the cart for more than 10 seconds |
102
+
| Product Removed | A user has removed a product from the cart |
103
103
104
104
## User identity
105
105
@@ -154,9 +154,9 @@ To support seamless customer tracking the [Mixpanel](/docs/connections/destinati
154
154
155
155
## Subscription events
156
156
157
-
All [recurring orders in the Shopify checkout](https://blog.littledata.io/help/posts/tracking-subscription-orders-in-the-shopify-checkout/){:target="_blank"}, from any subscription app, are tracked as Order Completed events.
157
+
All [recurring orders in the Shopify checkout](https://blog.littledata.io/help/posts/tracking-subscription-orders-in-the-shopify-checkout/){:target="\_blank"}, from any subscription app, are tracked as Order Completed events.
158
158
159
-
Additional subscription lifecycle events via Littledata's [ReCharge connection](https://www.littledata.io/connections/recharge){:target="_blank"} are available in cloud-mode destinations. See the [Track (custom)](https://docs.google.com/spreadsheets/d/1aljowRhMU9_7uGXmcipbP1Y14S4cOSdXGQA2Vx7BHko/edit#gid=1155311093){:target="_blank"} tab of the event schema.
159
+
Additional subscription lifecycle events via Littledata's [ReCharge connection](https://www.littledata.io/connections/recharge){:target="\_blank"} are available in cloud-mode destinations. See the [Track (custom)](https://docs.google.com/spreadsheets/d/1aljowRhMU9_7uGXmcipbP1Y14S4cOSdXGQA2Vx7BHko/edit#gid=1155311093){:target="\_blank"} tab of the event schema.
The list below outlines the properties included in most events. See the 'Track (eCommerce)' tab of the [event schema](https://docs.google.com/spreadsheets/d/1aljowRhMU9_7uGXmcipbP1Y14S4cOSdXGQA2Vx7BHko/copy){:target="_blank"} for exactly which properties are sent with which events.
173
+
The list below outlines the properties included in most events. See the 'Track (eCommerce)' tab of the [event schema](https://docs.google.com/spreadsheets/d/1aljowRhMU9_7uGXmcipbP1Y14S4cOSdXGQA2Vx7BHko/copy){:target="\_blank"} for exactly which properties are sent with which events.
@@ -201,8 +201,7 @@ The list below outlines the properties included in most events. See the 'Track (
201
201
|`total`| The total value of the order | Float |
202
202
|`userId`| Chosen user identifier, defaulting to Shopify Customer ID | String |
203
203
204
-
> note ""
205
-
> \*`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.
204
+
> note "" \*`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.
206
205
207
206
## Product properties
208
207
@@ -232,15 +231,15 @@ Each item in the `products` array, or Product Viewed and Product Added events, w
232
231
233
232
## Import all orders
234
233
235
-
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.
234
+
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.
236
235
237
236
## Advanced settings
238
237
239
238
You can edit these data pipeline settings within Littledata's app.
240
239
241
240
### cookiesToTrack
242
241
243
-
You can send any cookie set on a landing page (for example, a session identifier or marketing campaign name) to Segment with an Identify call. A common use is to set the array as `['iterableEmailCampaignId', 'iterableTemplateId']` to pass Iterable `campaignId` and `templateId` through to the [Order Completed event](https://support.iterable.com/hc/en-us/articles/204795719-Sending-Data-from-Segment-to-Iterable-#order-completed){:target="_blank"}.
242
+
You can send any cookie set on a landing page (for example, a session identifier or marketing campaign name) to Segment with an Identify call. A common use is to set the array as `['iterableEmailCampaignId', 'iterableTemplateId']` to pass Iterable `campaignId` and `templateId` through to the [Order Completed event](https://support.iterable.com/hc/en-us/articles/204795719-Sending-Data-from-Segment-to-Iterable-#order-completed){:target="\_blank"}.
0 commit comments