Shopify
Connect Shopify storefront and Admin API data to Vendo, then route normalized commerce events and records to supported destinations.
Last reviewed July 13, 2026
Vendo combines Shopify storefront tracking with server-side commerce syncs. Use it to capture behavior, import durable order and customer records, and deliver normalized data to the destinations selected for the integration.
How it works
| Path | Purpose |
|---|---|
| Web Pixel | Captures supported storefront and checkout events in Shopify’s pixel sandbox |
| Theme app embed | Loads destination-specific browser features that require storefront context |
| Server-side source | Imports Shopify Admin API records such as orders, customers, products, refunds, and fulfillments |
| Webhooks and scheduled work | Keep supported lifecycle data current between broader syncs |
Supported destination workflows
| Destination | Shopify-specific guide |
|---|---|
| Mixpanel | Shopify to Mixpanel |
| BigQuery | Shopify to BigQuery |
| Segment | Shopify to Segment |
| OneSignal | Shopify to OneSignal |
| Customer.io | Shopify to Customer.io |
| Google Tag Manager | Shopify and GTM |
The destination catalog in the app is authoritative for your workspace. Managed destinations can require support-assisted configuration.
Before you start
- Use a Shopify account that can install and authorize the Vendo app.
- Choose the production or development store deliberately.
- Decide which destinations should receive browser events, server-side records, or both.
- Confirm consent requirements before enabling browser-side marketing tools.
Setup
- Follow the Shopify setup guide.
- Confirm the Web Pixel and theme app embed states required by your destinations.
- Connect each destination with its own credentials.
- Select events, records, identity mapping, and optional backfill.
- Run a small test and review Activity Logs.
- Validate one storefront event and one server-side order in each destination.
Data and identity
Shopify data model owns the canonical event and object reference. Identity can move from anonymous storefront context to a known Shopify customer during login or checkout. Keep stable event and order identifiers when the same conversion is sent through browser and server paths.
Backfill and freshness
Historical backfill applies to supported server-side records and the configured date range. It cannot recreate browser behavior that was never collected. Review Historical backfill before rerunning a range, because partially delivered data can create duplicates in destinations without compatible deduplication.
Verify
- Confirm Shopify and destination apps show a healthy connection.
- Trigger a storefront test event.
- Create or use a safe test order.
- Check the source and destination jobs.
- Compare event time, customer identity, order ID, amount, currency, and products with Shopify.
Troubleshooting
| Symptom | Check |
|---|---|
| Storefront events missing | Web Pixel, theme embed, consent, and active theme |
| Orders missing | Shopify source scopes, selected streams, date range, and job errors |
| Customer history split | Anonymous-to-known identity mapping and destination merge behavior |
| Duplicate conversions | Shared event ID and overlapping browser/server or backfill paths |