SHOPIFY CDP CONNECTOR

Get your Shopify data into Twilio Segment in 30 seconds.

Free for select Twilio Segment customers

Trusted by ecommerce teams at

Orgain NOBULL CrossFit Studio McGee Meermin Jenni Kayne Cymbiotika Dutch

The modern way to get Shopify data into Twilio Segment.

Most Shopify-to-Segment connectors were built before Shopify's Web Pixel API, Customer Privacy API, and headless architecture existed. The CDP Connector was built from scratch for today's Shopify.

Complete event coverage

Client-side storefront events via Shopify's native Web Pixel API plus server-side order webhooks. No gaps between browse and buy. No dependency on script injection that breaks on checkout updates.

Identity resolution that works

The CDP Connector stores the anonymous_id in Shopify cart attributes. When a customer checks out, the identity travels with the cart – even when cookies are blocked, even across domain changes. This is the only Shopify connector where anonymous browsing reliably stitches to purchase.

Built-in consent management

Native support for Shopify's Customer Privacy API with three modes: disabled, pass-through, and strict. Works with third-party consent platforms automatically. No custom development required.

Drop-in replacement for legacy connectors

If you're using an older Shopify-to-Segment connector that hasn't kept pace with Shopify's evolving checkout, the CDP Connector is a direct replacement. Shopify Web Pixel support, cart-based identity resolution, consent management, first-time purchase detection, custom event forwarding, and live event stream debugging – all included.

Four modules working together for complete data capture.

The CDP Connector uses four independent modules to capture data at every level of the Shopify stack. All four are active by default.

1
ScriptTag
Client-side, Device-mode

Installs the Twilio Segment snippet on your storefront and updates the cart to include anonymous_id. Loads your Device-mode Segment destinations (like Amplitude, Mixpanel, or Google Analytics) automatically.

2
Web Pixel
Client-side, Cloud-mode

Uses Shopify's native Web Pixel API to capture storefront events: product views, cart events, checkout steps, form submissions, and custom events. More reliable than script injection. Bypasses most ad blockers. Survives checkout updates.

3
Webhook
Server-side, fully reliable

Subscribes to Shopify webhooks for order events: payments, fulfillments, cancellations, edits, and refunds. Server-side means zero dependency on the browser. No ad blocker can touch it. Includes the Estimated First Order synthetic event for first-time vs repeat purchase detection.

4
UI Extension
Optional, identity sync

A lightweight Shopify theme extension that syncs anonymous_id to the cart when ScriptTag is disabled. Essential for headless stores or manual Segment installations. Ensures consistent visitor identity across the entire customer journey.

Every Shopify event mapped to the Twilio Segment V2 Ecommerce spec.

The CDP Connector translates Shopify events into spec-compliant Twilio Segment events automatically. No custom mapping required.

Captured by Shopify Web Pixel when visitors interact with your store. Client-side, real-time.

Shopify Event
Segment Event
Key Properties
page_viewed
Loaded a Page
url, referrer, search, title
product_viewed
Product Viewed
product_id, sku, name, brand, price, currency, url
product_added_to_cart
Product Added
product_id, sku, name, price, quantity
product_removed_from_cart
Product Removed
product_id, sku, name, price, quantity
cart_viewed
Cart Viewed
cart_id, currency, products[]
collection_viewed
Product List Viewed
list_id, category, products[]
search_submitted
Products Searched
query
checkout_started
Checkout Started
checkout_token, order_id, revenue, shipping, tax, products[]
payment_info_submitted
Payment Info Entered
checkout_token
checkout_completed
Checkout Step Completed
checkout_token, shopify_step
form_submitted
Shopify Form Submitted
form_id, form inputs

Captured by Shopify Webhooks. Server-side, reliable, immune to ad blockers.

Shopify Event
Segment Event
Key Properties
orders/paid
Order Paid + Order Completed
order_id, revenue, shipping, tax, discount, coupon, products[]
orders/fulfilled
Order Fulfilled
order_id, revenue, products[]
orders/cancelled
Order Cancelled
order_id
orders/create
Order Created
order_id, revenue, products[]
refunds/create
Order Refunded
order_id, negative revenue
orders/partially_fulfilled
Order Partially Completed
order_id
Full events spec documentation →

The only Shopify connector where identity resolution actually works.

Connecting an anonymous visitor's browsing session to their purchase is the hardest problem in Shopify analytics. The CDP Connector solves it by storing the anonymous_id in the Shopify cart.

How it works
1
Visitor arrives
anonymous_id is generated and stored in the browser. ScriptTag writes it to the Shopify cart attributes.
2
Visitor browses
Web Pixel captures product views, cart events, and checkout steps. All events carry the same anonymous_id.
3
Visitor checks out
The anonymous_id travels with the cart to checkout. Even if cookies are blocked, the cart attribute persists.
4
Order webhook fires
Webhook receives the order with anonymous_id from cart attributes and Shopify Customer ID as user_id. identify() fires to stitch anonymous sessions to the known buyer.
What gets resolved

Every webhook event triggers an identify() call that enriches the customer profile with traits from Shopify:

shopify_customer_id
email
first_name
last_name
created_at
orders_count
total_spent
shopify_rfm_group
shopify_predicted_spend_tier
address (country, state, city, postal_code)

You can add additional custom traits via the CDP Connector settings. The user_id source is configurable: Shopify Customer ID (default), email, or none.

Built for every Shopify configuration.

100% accurate data collection regardless of how your Shopify store is set up.

New Checkout

Full support for Shopify's latest checkout architecture. All checkout step events captured automatically.

Headless

Webhook events work out of the box. Install Segment manually in your headless frontend and use UI Extension for anonymous_id sync.

Subscriptions

Tracks new and recurring subscription orders. Distinguishes first-time purchases from renewals.

Consent Mode

Native Shopify Customer Privacy API support. Three modes: disabled, pass-through, and strict. Works with third-party consent platforms.

Shopify Markets

Full support for international selling. Currency, locale, and market data included in events.

Upsells

Captures upsell and cross-sell events within the checkout flow. Revenue attribution for post-purchase offers.

Everything LittleData does. Plus everything it doesn't.

LittleData was the default Shopify-to-Segment connector for years. Attribution's CDP Connector is the modern replacement.

CDP Connector
LittleData
Native Shopify app pixel
Yes
No (custom pixel, manual setup)
Server-side order webhooks
Yes
Yes
Cart-based anonymous_id sync
Yes
No (uses PersistentID)
Shopify Customer Privacy API
Yes (3 modes: disabled, pass-through, strict)
Yes (pass-through only, blocking requires custom code)
Estimated First Order detection
Yes
No
Twilio Segment as primary destination
Yes
Limited (one of many destinations)
Segment V2 Ecommerce spec
Yes
Partial
Headless store support
Yes (webhooks + UI Extension)
Yes (custom pixel + server-side)
Shopify Markets support
Yes
Yes
Custom event forwarding
Yes
No
Live event stream debugging
Yes
No
30-second install
Yes
No (requires manual pixel setup)

What customers say

Jay Meyering

"Attribution's CDP Connector has been great for us! Connecting it to Segment was extremely easy, and it covers all the events we need for our store analytics – incredibly useful. The support team has been very responsive to any questions we've had. Really great experience all around."

Jay Meyering
Sr. Manager, Software Development, CrossFit
CrossFit

Frequently asked questions

Attribution’s Shopify CDP Connector is a Shopify App Store app that sends your Shopify storefront and order data directly to a Twilio Segment source. It installs in 30 seconds with no coding required and automatically captures pageviews, product interactions, checkout events, and order events using both client-side and server-side tracking. The CDP Connector follows the Twilio Segment V2 Ecommerce spec and handles identity resolution from anonymous first visit through to purchase. It is a standalone pass-through app that does not store any customer data.

The fastest way to connect Shopify to Twilio Segment is Attribution’s CDP Connector, available in the Shopify App Store. It installs in 30 seconds with no coding required. The CDP Connector automatically installs the Twilio Segment snippet on your storefront, captures all standard ecommerce events via Shopify’s Web Pixel API, subscribes to server-side order webhooks for payments, fulfillments, cancellations, and refunds, and resolves customer identity from anonymous browsing through to purchase. The alternative is a manual Segment installation, which requires developer time, breaks when Shopify updates the checkout, and does not handle identity resolution across the storefront and checkout domains.

Yes. Attribution’s Shopify CDP Connector is a direct replacement for LittleData (now Littledata by Ordergroove). The CDP Connector provides the same core capability, sending Shopify events to Twilio Segment, but with several improvements. It uses Shopify’s native Web Pixel API for client-side events, which is more reliable than script injection and survives checkout updates. It resolves identity by syncing anonymous_id through the Shopify cart, ensuring visitors are connected to their purchases even when cookies are blocked. It supports Shopify’s Customer Privacy API for consent management. And it includes an Estimated First Order synthetic event that lets Attribution distinguish first-time purchases from repeat ones.

Identity resolution on Shopify is hard because the checkout is on a separate domain and ad blockers interfere with client-side tracking. The CDP Connector solves this by storing the anonymous_id in the Shopify cart attributes. When a customer checks out, the anonymous_id travels with the cart to the checkout and appears on the order webhook. This means the CDP Connector can stitch together anonymous browsing sessions with purchase events even when cookies are blocked or the checkout domain changes. The identify() call fires on login, during checkout, and from webhook events, using the Shopify Customer ID as the user_id by default. Attribution’s CDP Connector is the only Shopify-to-Segment connector where this identity resolution reliably works.

The CDP Connector sends all standard Shopify ecommerce events mapped to the Twilio Segment V2 Ecommerce spec. Client-side events include Page Viewed, Product Viewed, Product Added, Product Removed, Cart Viewed, Product List Viewed, Products Searched, Checkout Started, Payment Info Entered, and Checkout Step Completed. Server-side webhook events include Order Paid, Order Completed, Order Fulfilled, Order Cancelled, Order Created, Order Refunded, and Order Partially Completed. The CDP Connector also captures Shopify Form Submitted events and custom events sent via Shopify.analytics.publish().

Twilio Segment does not offer a native Shopify source with full ecommerce event coverage. Segment has native sources for Stripe, Zendesk, and dozens of other platforms, but not Shopify. The CDP Connector fills this gap by acting as a complete Shopify-to-Segment bridge. It captures both client-side storefront events and server-side order webhooks, resolves identity across anonymous browsing and purchase, handles consent management, and follows the Twilio Segment V2 Ecommerce spec. The result is a complete, spec-compliant Shopify source in your Twilio Segment workspace with no custom development required.

Yes, with one limitation. For headless stores, the Webhook module captures all server-side order events normally. However, the ScriptTag and Web Pixel modules only work on the Shopify storefront, so you will need to install the Twilio Segment snippet manually in your headless frontend. The CDP Connector’s UI Extension can still sync anonymous_id via cart attributes if your headless frontend writes to the Shopify cart. Use the source_name property on Order events to identify whether orders originated from the Shopify storefront or your headless frontend.

The CDP Connector has native support for Shopify’s Customer Privacy API with three modes. Disabled mode sends all events regardless of consent preferences. Pass-through mode attaches consent context to every event but still sends them, letting you decide in Twilio Segment how to handle consent. Strict mode fully honors Shopify Customer Privacy settings, blocking and queuing events until customer consent is obtained. If you use a third-party consent management platform, configure it to set data processing in Shopify’s Customer Privacy API and the CDP Connector will respect those settings automatically.

The CDP Connector is free for select Twilio Segment customers. Contact Attribution for eligibility details. The CDP Connector is a standalone product that works independently of Attribution’s multi-touch attribution platform. Shopify stores that use the CDP Connector can also add Attribution’s multi-touch attribution, first-time purchaser reports, cohort payback analysis, and Offline Conversion Events for a complete ecommerce measurement stack.

Attribution’s CDP Connector is the most complete Shopify-to-Segment connector available. It is the only connector that uses Shopify’s native Web Pixel API for client-side events, syncs anonymous_id through Shopify cart attributes for reliable identity resolution, supports Shopify’s Customer Privacy API for consent management, and follows the Twilio Segment V2 Ecommerce spec for all events. It works with standard Shopify storefronts, headless architectures, Shopify Markets, subscriptions, upsells, and the new Shopify checkout. Other options include legacy connectors like LittleData (now Littledata by Ordergroove), which lack Web Pixel API support and cart-based identity resolution, and manual Segment installations, which require developer time and break on checkout updates.