Extensibility Compatibility w/ Third Party Libraries

Topic summary

A team transitioning from checkout.liquid to Shopify’s checkout Extensibility is encountering compatibility issues with third-party analytics tools like Amplitude JS.

Core Problem:

  • Third-party browser-based libraries expect access to the DOM and standard browser APIs
  • Checkout extensions run in a restricted sandbox environment without access to window and document objects
  • This architectural limitation breaks many existing analytics integrations

Confirmation & Workaround:

  • Liam confirmed that checkout extensions indeed lack DOM/browser API access due to the sandboxed environment
  • ecbLR identified Shopify’s ‘Customer Events’ panel as a potential solution—a less restrictive sandbox provided as an “escape hatch” for legacy pixels
  • Code injected via Customer Events runs in an iframe, allowing most pixels to work with minor refactoring
  • However, not all third-party tools are guaranteed to be compatible even with this approach

Outstanding Need:
The team seeks alternatives to share checkout events with third-party analytics products to maintain visibility across the complete funnel.

Summarized with AI on November 9. AI used: claude-sonnet-4-5-20250929.

Hi,

“third-party browser-based tooling ( such as Amplitude JS ) may no longer be compatible with Extensibility, given that these tools expect access to the DOM and the usual suite of browser APIs, which Shopify no longer exposes through the sandbox environment.”

^This is correct - checkout extensions do not have access to window and document objects since they are loaded in a restricted environment.

1 Like