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
+44-42Lines changed: 44 additions & 42 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,6 @@ Here's an architecture diagram that shows how the Littledata app mediates data f
37
37
38
38
Below is a table of events that **Shopify by Littledata** sends to Segment through the analytics.js libary. These events will show up as tables in your warehouse, and as regular events in your other Destinations supporting device-mode.
@@ -46,7 +45,6 @@ Below is a table of events that **Shopify by Littledata** sends to Segment throu
46
45
| Product Viewed | The user has viewed a product page |
47
46
| Product Image Clicked | The user has clicked a product image |
48
47
49
-
50
48
In addition to the events tracked as standard, the following hits can be tracked based on page path:
51
49
52
50
| Event Name | Description |
@@ -56,7 +54,6 @@ In addition to the events tracked as standard, the following hits can be tracked
56
54
| Blog Viewed | A prospect has viewed the blog |
57
55
| Registration Completed | A prospect has completed registration |
58
56
59
-
60
57
## Cloud-mode events
61
58
62
59
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.
@@ -76,7 +73,6 @@ Below is a table of events that **Shopify by Littledata** sends to Segment from
76
73
| Customer Enabled (v2) | A user has confirmed their email address and created a Shopify customer account with verified_email set as true |
77
74
| Fulfilment Update (v2) | An order fulfilment status has changed (including status, tracking_numbers and tracking_urls where the shipping integration allows) |
78
75
79
-
80
76
## Identify calls
81
77
82
78
For every event where there is an identifiable Shopify customer (from both the device-mode and cloud-mode) Littledata also sends an Identify call. This 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.
@@ -100,7 +96,6 @@ The following traits are included with an Identify call:
100
96
|`state`| Whether the customer account is enabled or disabled | String |
101
97
|`verified_email` (v2) | Whether the customer has verified their email | Boolean |
102
98
103
-
104
99
## Alias calls
105
100
106
101
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).
@@ -120,43 +115,50 @@ Additional events available through Littledata's [ReCharge connection](https://w
120
115
| Payment Method Updated | A customer has updated the payment method |
121
116
| Customer Update | A customer information updated |
122
117
123
-
## Event Properties
118
+
## Event properties
124
119
125
120
The list below outlines the properties included in the events listed above.
0 commit comments