Extensibility Compatibility w/ Third Party Libraries

[ecbLR]

High-level question:
Our team is transitioning from `checkout.liquid` to checkout Extensibility, and we need to replicate our existing third-party analytics customizations with extensions using the new web pixel API. 

Our research suggests that some 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. 

We want to understand if our general interpretation is accurate without going too deep into specifics. 

[Liam · Accepted solution]

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. 

[ecbLR]

Thanks for confirming this for us, @Liam. Appreciate it. 

[dewain]

Hi Liam, 

Is there an alternative which can be leveraged to share checkout events with 3rd party analytics products. It would be extremely helpful for us to understand the complete funnel.

Thanks,

Dewain

[ecbLR]

@dewain We've been using Shopify's 'Customer Events' pannel, which is a lax sandbox Shopify has provided as an escape hatch for legacy pixels. All the code gets injected into an iframe. While not everything is guaranteed to be compatible, with a little refactoring seems to be okay for most pixels.