Commerce

Shopify integration for digital marketing agencies

Shopify is the most common e-commerce platform digital marketing agencies' clients run on, and Shopify's tracking surface is a moving target — the pixel infrastructure changed three times in two years (Online Store 2.0, Customer Events API, Shopify Plus checkout). Tracking which Shopify version a client is on, which checkout extension they use, and which apps are installed is essential for setting up Meta CAPI, TikTok Events API, and Google Ads conversions correctly.

How Phloz models Shopify

Every Shopify concept that matters for digital marketing agency operations is a typed object in the tracking map. Health state per node, audit cadence, and graph relationships to every other tracking-system node it touches — so a broken tag or misconfigured property is findable in seconds across your full book of clients.

  • Shopify store as a typed node with myshopify domain, primary domain, plan tier (Basic / Plus), checkout type
  • Customer Events API config tracked separately — pre-checkout-extension stores need different setup than Shopify Plus
  • Installed Shopify apps with tracking implications (Klaviyo, TikTok, Meta, Google, Pinterest) linked to the store node
  • Storefront pixel status + theme version — finding broken pixels after a theme update takes one query

Common Shopify configuration gotchas

The configuration mistakes agencies most often make with Shopify, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.

  • Shopify Plus checkout pixel placement: Plus stores use a separate checkout domain, and pixels must be re-installed there explicitly. Most non-Plus migration agencies miss this and lose all checkout conversions.
  • Customer Events API timing: events fire client-side AFTER navigation completes, but server-side AFTER the order webhook. Agencies treat these as the same event and double-count conversions.
  • App-installed pixels: the Klaviyo Shopify app installs its own pixel that conflicts with manually-installed Klaviyo tags. Pick one source of truth per platform.

At launch (V1)

Shopify store + pixel + Shopify Analytics integration modelled as tracking-map nodes.

Coming (V2)

Shopify Admin API sync: active apps, storefront pixel status, customer-event firing.

Why we built the integration this way

Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With every Shopifyobject as a typed tracking node, the agency can answer questions like "which clients have a misconfigured Shopifysetup?" or "which Shopifyconfigurations changed last quarter?" from a single graph query.

The V1 surface is intentionally manual — agencies enter the configuration at onboarding rather than auto-importing. This forces explicit verification at the exact moment the agency takes over the client's tracking, catching most of the commonGotchas listed above before they become production issues. V2 will add API-based sync where the underlying platform supports it; we won't add sync where the underlying API doesn't expose the right data.

When to use this in your client onboarding flow

The standard pattern for digital marketing agencies running Phloz: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's Shopifyconfiguration as Phloz nodes — pixel IDs, tracking-code installations, conversion-action setup, the relationships to other systems. Verify each one fires by triggering a test event. Set the "verified at" timestamp on each node. Schedule a quarterly verification task on the agency engineer who owns tracking.

The 30 minutes at onboarding catches 90 percent of the tracking issues that would otherwise surface during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.

Frequently asked questions

The three questions agencies ask most often about Phloz's Shopify integration. Honest answers — same data we'd give a friend evaluating the integration.

How does Phloz handle Shopify Plus stores differently from Basic?
Plus stores have additional node metadata: checkout extensibility, organisation-level controls, B2B account groups. The same Shopify integration handles both — Phloz just models the Plus-specific fields when applicable. For agencies running mixed Plus + Basic client portfolios, this is the cleanest way to track the differences.
Does Phloz manage Shopify themes or storefronts?
No — Phloz tracks the storefront's tracking infrastructure (pixels, scripts, app installations) but doesn't manage theme code. For agencies running web-design + tracking together, the Shopify integration documents what's installed; the actual code lives in Shopify's theme editor.
What about Shopify Markets / multi-currency tracking?
Markets are tracked as child nodes under the parent Shopify store, each with its own currency and (potentially) its own pixel configuration. Agencies running Shopify Markets across multiple geographies use this to verify each Market's tracking is actually firing.

Other commerce and adjacent tools Phloz integrates with.

Start your free trial

14 days free · No credit card · Starter tier free forever