PostHog on Shopify: App, Manual Install or Server-Side Sync?

Manual installation pairs PostHog’s theme snippet with a Customer events pixel for checkout. The storefront SDK supports autocapture, replay, heatmaps, feature flags and experiments; the snippet alone cannot track checkout. We wrote a detailed step-by-step guide to installing PostHog on Shopify and tracking checkout events.

A manual installation lets you choose what gets tracked and how it appears in PostHog, but accuracy still depends on how you build it. Budget for a developer to maintain the code, connect visitor IDs and handle consent. Write your event plan before starting. For a headless store, install PostHog in the storefront application; the theme snippet applies to Shopify-hosted themes.

PixieHog is a Shopify app built specifically to connect Shopify with PostHog. As of October 2026, it is free, with a 5.0 rating from three reviews. (+) CeladonWorks develops and supports the app, which launched in December 2024 and works with checkout.

PixieHog’s published default Web Pixel selections enable page_viewed, product_added_to_cart, cart_viewed, product_removed_from_cart, checkout_started, checkout_contact_info_submitted and checkout_completed. (+) You can change the selected events and choose Shopify event names or mapped ecommerce names; for example, checkout_completed becomes Order Completed in the mapped format. (+) Product and collection views are off by default; turn them on if your analysis needs them.

Replay and storefront experiments need PixieHog’s optional on-site PostHog snippet. (+) Enable it separately from Web Pixel Events through PostHog JS Web Config.

Check the data collection strategy before enabling it. “Identified by Consent” is meant to attach customer data only when Shopify’s Customer Privacy API reports consent; “Identified” attaches it regardless of consent. (+) In PixieHog’s published pixel code, that check runs when the pixel loads. (+) Test what happens when a visitor grants and withdraws consent without reloading. Withdrawal does not automatically delete customer data already collected.

Ask CeladonWorks to fix app integration problems: PostHog does not provide support for third-party integrations such as PixieHog. (+)

Trackify sends Shopify store events to Mixpanel, PostHog and Segment from one app. It lets you select which event types to track without writing custom tracking code.

As of October 2026, Trackify costs US$8.99 a month or US$89 a year, with a seven-day free trial and no reviews. (+) Elevate Tech develops and supports it; the app launched in May 2025.

Trackify lists checkout compatibility without naming the checkout events it sends. During the trial, place an order and check that the purchase arrives under the same visitor as the storefront activity. Ask Elevate Tech whether it loads PostHog’s storefront SDK too; replay and storefront experiments need it.

Trackify is worth considering if you need to send the same store events to several tools. If you only use PostHog, that extra capability may not help you.

Shopify webhooks deliver order, customer and refund updates from Shopify’s servers after those actions happen. (+) A server-side sync forwards those records to PostHog without installing it on your storefront.

Zapier has a ready-made Shopify–PostHog connection: New Order, New Paid Order, New Customer or New Refund can trigger PostHog’s Capture Event action. You supply the event name, PostHog distinct ID and properties. If your conversion is a payment, trigger on New Paid Order and don’t also count New Order as a purchase.

RudderStack supports server-side Shopify webhooks as well as browser pixels, and has a PostHog destination. (+ / +) On a Shopify-hosted theme, its identity stitching needs the RudderStack App Embed Script; headless stores can use its custom-pixel identity stitching or the documented storefront mapping. (+) Choosing RudderStack alone does not establish a shared PostHog identity.

You can still use synced events for trends, funnels and retention. Server order and refund records don’t depend on a browser page loading. Shopify’s checkout_completed fires on the thank-you page or the first upsell page, and is missed if that page fails to load. (+) Webhooks can arrive twice or not at all, so decide who drops duplicate deliveries and reconciles missed orders with Shopify. (+)

A backend sync can send orders, but it cannot show what the visitor clicked before buying. Session recordings, heatmaps, autocapture and storefront experiments won’t work with a server-only sync because PostHog isn’t actually installed on your site.

Your theme snippet and Customer events pixel are separate event streams. Shopify runs custom pixels in a sandboxed iframe without direct access to the top frame, so the pixel cannot simply read the storefront’s PostHog cookie through document.cookie. (+) Pasting the snippet into both places does not establish a shared visitor identity.

For the manual route, pass the storefront’s PostHog distinct ID through Shopify’s browser.cookie API using a consent-controlled bridge. (+) Follow the checkout-event implementation in our install guide, then verify that the storefront and purchase events resolve to the same person.

PixieHog’s pixel reads the distinct ID from PostHog’s local-storage entry. (+) Check that your storage settings let it find that ID, then follow a test visit through checkout to see whether the events stay with the same person.

To join server purchases to browser activity or experiment exposure, a server sync needs the browser’s PostHog distinct ID or an explicit mapping to it; the order’s customer ID or email alone does not identify the browser that saw an experiment. (+) PostHog events require a distinct ID, so decide how that ID reaches the order pipeline before choosing the sync. (+) Once purchases connect to the participant who saw the variant, follow our PostHog A/B testing guide for Shopify.

You can use browser tracking for the shopping journey and a server sync for order records, provided each event has one sender and the IDs connect.

1. Check installation ownership. Initialize PostHog once on the storefront and give each event one sender. An app can own checkout events while your theme code owns the storefront, as long as they don’t overlap. When moving from an app to manual code, remove the app’s pixel and disable its storefront snippet first.
2. Run a test order. Follow each planned product, cart, checkout and purchase action in PostHog Activity. Check the order ID, value and currency.
3. Check identity. Confirm that storefront activity, experiment exposure if used, and the purchase resolve to the same person. Test both cart checkout and Buy Now, where your store offers it.
4. Check attribution. If you report purchases by campaign, start a test order from a UTM-tagged link and check that your purchase report attributes the order to that campaign.
5. Check browser features and consent. If you use replay, open a recording. If you run experiments, check that flags load and the storefront shows the right variant. Test consent denied, granted and withdrawn.
6. Reconcile purchases with Shopify. Compare order IDs, values and refunds for the same reporting period. Investigate missing and repeated purchases, allowing for your consent and test-order exclusions.
7. Verify each destination separately. Confirm the event names and properties actually received in PostHog and every other connected tool.

Before using purchases to measure conversion, check that each purchase belongs to the visitor who made it. The PostHog audit also covers consent, duplicate events and comparison with your order records.