Skip to Content
SourcesShopifyOverview

Shopify

Connect Shopify storefront and Admin API data to Vendo, then route normalized commerce events and records to supported destinations.

Last reviewed September 15, 2026

Vendo combines Shopify storefront tracking with server-side commerce syncs. Use it to:

  • Capture behavior
  • Import durable order and customer records
  • Deliver normalized data to the destinations that you select

How it works

PathPurpose
Web PixelCaptures supported storefront and checkout events in Shopify’s pixel sandbox
Theme app embedLoads destination-specific browser features that require storefront context
Server-side sourceImports Shopify Admin API records such as orders, customers, products, refunds, and fulfillments
Webhooks and scheduled workKeep supported lifecycle data current between broader syncs

Supported destination workflows

DestinationShopify-specific guide
MixpanelShopify to Mixpanel
BigQueryShopify to BigQuery
SegmentShopify to Segment
OneSignalShopify to OneSignal
Customer.ioShopify to Customer.io
Google Tag ManagerShopify and GTM

The destination catalog in the app is the authority for your workspace. Managed destinations can require configuration with help from support.

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.
  • Before you enable browser-side marketing tools, confirm the consent requirements.

Setup

  1. Follow the Shopify setup guide.
  2. Confirm the Web Pixel and theme app embed states that your destinations require.
  3. Connect each destination with its own credentials.
  4. Select events, records, identity mapping, and optional backfill.
  5. Run a small test and review Latest run on the destination page.
  6. In each destination, validate one storefront event and one server-side order.

Data and identity

The Shopify data model is the canonical reference for events and objects. Identity can move from anonymous storefront context to a known Shopify customer during login or checkout. If the same conversion goes through the browser and server paths, keep stable event and order identifiers.

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. Before you run a range again, review Historical backfill. Partially delivered data can create duplicates in destinations that do not have compatible deduplication.

Verify

  1. Confirm that the Shopify and destination apps show a healthy connection.
  2. Trigger a storefront test event.
  3. Create or use a safe test order.
  4. Check the source and destination jobs.
  5. Compare event time, customer identity, order ID, amount, currency, and products with Shopify.

Troubleshooting

SymptomCheck
Storefront events missingWeb Pixel, theme embed, consent, and active theme
Orders missingShopify source scopes, selected streams, date range, and job errors
Customer history splitAnonymous-to-known identity mapping and destination merge behavior
Duplicate conversionsShared event ID and overlapping browser/server or backfill paths
Need help?

When you contact support, give your workspace, the source or destination name, the job ID and the first error message.

support@vendodata.com
Last updated on
OverviewSetup Guide