Skip to content

Commit 291aee6

Browse files
author
markzegarelli
authored
Merge pull request #1502 from segmentio/littledata-docs-update
Littledata docs update
2 parents 90c1cd1 + ecd261e commit 291aee6

File tree

1 file changed

+13
-8
lines changed
  • src/connections/sources/catalog/libraries/website/shopify-littledata

1 file changed

+13
-8
lines changed

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

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,8 @@ Below is a table of events that **Shopify by Littledata** sends to Segment throu
5252
| Registration Viewed | A user has viewed the /account/register page |
5353
| Thank you Page Viewed | A user has viewed the thank you page after completing an order \* |
5454

55-
> 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.
55+
> info ""
56+
> \* 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.
5657
5758
## Cloud-mode Events
5859

@@ -78,14 +79,14 @@ Below is a table of events that **Shopify by Littledata** sends to Segment from
7879

7980
## User identity
8081

81-
In the Littledata application, you can choose which of the following fields you want to send as the `userId` for known customers:
82+
In the Littledata application you can choose which of the following fields you want to send as the `userId` for known customers:
8283

83-
- Shopify Customer ID (default)
84-
- Email
85-
- MD5 email hash
86-
- None
84+
- **Shopify customer ID** (default) - Recommended if you have a simple Shopify setup with minimal integrations.
85+
- **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.
86+
- **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.
87+
- **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.
8788

88-
For example, using 'email' allows you to match users across platforms that do not have access to the Shopify Customer ID. For [Segment Personas](/docs/personas/) we also send `shopify_customer_id` as an [externalID](/docs/personas/identity-resolution/externalids/) for advanced matching.
89+
For [Segment Personas](/docs/personas/) we also send `shopify_customer_id` as an [externalID](/docs/personas/identity-resolution/externalids/) for advanced matching.
8990

9091
## Identify Calls
9192

@@ -145,7 +146,7 @@ The list below outlines the properties included in the events listed above.
145146
| `affiliation` | The affiliation of the order | String |
146147
| `cart_id` | The ID of the Shopify cart | String |
147148
| `checkoutId` | The ID of the checkout session | String |
148-
| `context.uip` | The user's IP address | String |
149+
| `context.ip` | The user's IP address | String |
149150
| `context['Google Analytics'].clientId` | The user's Google Analytics Client ID | String |
150151
| `context['Google Analytics'].geoid` | The user's location | String |
151152
| `coupon` | Comma-separated string of discount coupons used, if applicable | String |
@@ -191,6 +192,10 @@ Each item in the `products` array, or Product Viewed and Product Added events, w
191192
| `url` | The URL of the product page | String |
192193
| `variant` | The product variant name | String |
193194

195+
## Import all orders
196+
197+
With a [Littledata Plus plan](https://www.littledata.io/app/enterprise) 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.
198+
194199
## Advanced device-mode settings
195200

196201
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).

0 commit comments

Comments
 (0)