Full checkout visibility — the part most monitoring tools can't see

Why Shopify checkout is a monitoring blind spot

Shopify's checkout environment is intentionally isolated. When a customer clicks the checkout button on your store, they're redirected to a subdomain (typically checkout.shopify.com or your custom domain with the /checkouts/ path) where Shopify controls the page entirely. Your theme's CSS and JavaScript don't run here. Theme app embeds don't run here. Third-party analytics scripts don't run here.

This is a deliberate security decision by Shopify — keeping third-party code out of checkout protects payment data. But the consequence is that any monitoring tool that depends on your theme to inject its tracking code goes dark the moment checkout begins.

For most monitoring tools, your checkout funnel is completely invisible. You don't see which stage users drop off. You don't see errors. You don't see timing. You see an order either appears or doesn't.

The Web Pixel API: Shopify's official solution

Shopify provides a sanctioned mechanism for checkout instrumentation: the Web Pixel API. Web Pixels are sandboxed JavaScript workers that run within Shopify's controlled environment and receive standardised events from both the storefront and checkout. They communicate with the outside world through a message-passing interface and have access to a defined set of analytics events.

The Web Pixel is the only way to get real data from inside Shopify checkout. It's also how Shopify's own analytics work, how Google Analytics 4 integrates with Shopify checkout, and how Bloodhound monitors your checkout funnel.

Checkout events Bloodhound captures via Web Pixel

Once installed, Bloodhound's Web Pixel automatically receives and processes the following events from the Shopify checkout:

• page_viewed — any page view event, with full URL context
• product_viewed — product page views on the storefront
• collection_viewed — collection browse events
• cart_viewed — cart page view
• product_added_to_cart — add to cart events with variant and price data
• checkout_started — user initiates checkout
• checkout_address_info_submitted — shipping address entered
• checkout_shipping_info_submitted — shipping method selected
• checkout_contact_info_submitted — contact details confirmed
• payment_info_submitted — payment form submitted
• order_created — successful order placement
• thank_you_page_viewed — order confirmation viewed

Each event is timestamped and associated with an anonymous session ID, allowing Bloodhound to reconstruct the complete user journey and identify where sessions drop out.

What checkout monitoring data looks like in practice

With checkout monitoring active, Bloodhound gives you a funnel view: how many sessions reached each stage, and the drop-off rate between stages. A healthy Shopify checkout typically shows:

• Checkout started → shipping info submitted: 70-80% continuation
• Shipping info submitted → payment info submitted: 75-85% continuation
• Payment info submitted → order created: 85-95% continuation

When you see sharp drops between stages — particularly in the payment submission to order creation step — that's a signal to investigate for errors. Bloodhound surfaces error events that correlate with checkout drop-offs, so you can distinguish between behavioural abandonment (user changed their mind) and technical failure (something broke).

Timing data: the other half of checkout monitoring

Beyond funnel analytics, Bloodhound captures timing data for checkout operations: how long each stage takes to complete, how long payment processing takes, how long the order confirmation page takes to load. This data surfaces performance issues in the checkout flow — a payment widget that's taking 8 seconds to initialise is likely causing abandonment even when it doesn't throw a visible error.

Setting up Shopify checkout monitoring

When you install Bloodhound from the Shopify App Store, the Web Pixel is automatically created and activated. There are no additional steps — no code changes, no developer involvement, no theme edits. Shopify grants Bloodhound permission to register a Web Pixel as part of the app installation flow, and checkout events start flowing immediately.

The theme app embed (toggled in your theme editor) handles storefront monitoring — errors, Core Web Vitals, and script analytics on product pages, collections, and the cart. The Web Pixel handles checkout. Together, they give you complete coverage across your entire customer journey.

Limitations of checkout monitoring

The Web Pixel runs in a sandboxed environment with deliberate restrictions:

• No access to the checkout DOM or user inputs (by design — payment security)
• Event data is limited to the standardised Shopify event schema
• JavaScript errors within the checkout itself (from Shopify's own code or payment widgets) are not directly capturable via Web Pixel
• Timing precision is dependent on Shopify's event dispatch timing

These limitations are inherent to the Web Pixel architecture. They exist for good reason. What the Web Pixel provides — funnel visibility, event timing, session correlation — is significantly more than any tool relying on theme scripts can offer for checkout.