Custom Pixel Event stopped working

Technical Q&A
,
1

Hello,

We’re facing a complete breakdown of our pixel injection system across the site.

The entire content_for_header mechanism is no longer injecting properly and behaves erratically. Both standard and custom pixels are affected.

Most critically, Custom Pixels in Checkout are now completely non-functional.
No injection, no fallback, no workaround : we’re blind.

Stape is affected. Other apps relying on this are impacted too.
Several independent developers have tried to resolve it, none succeeded.
This is now severely affecting our tracking and infrastructure.

Does anyone had similar situation ? How can we save this ?

Best,

PM

2

Hey @pierremer,

You’re not alone — this issue has been happening since recent changes in Shopify’s checkout extensibility and stricter rules around content_for_header. Shopify is phasing out the old injection method in favor of new, sandboxed checkout UI extensions and web pixels. Here’s what you can do:

1. Switch to Shopify’s native Customer Events (Web Pixels)

Custom pixel events now need to be configured through Shopify’s customer events API or directly within the Customer Events section in your admin.
The content_for_header method is deprecated in many checkout environments, especially for Plus stores using checkout extensibility.

2. Use Shopify’s Web Pixel Extension API

If you’re using custom scripts or server-side tracking via apps like Stape, you’ll need to rebuild your pixel tracking logic using Shopify’s Web Pixel Extension API.

This will allow you to:

  • Listen to events like checkout_started, checkout_completed, etc.
  • Send data server-side (via your own backend or a platform like Stape)

3. Fallback (Temporary)

If you’re not ready to fully migrate:

  • Inject the tracking in theme.liquid for pre-checkout behavior
  • Use post-purchase extensions (Shopify CLI / app blocks) for order confirmation events
    But understand: this won’t fix checkout page tracking. That requires full migration.

4. If You’re on Shopify Plus

You may be able to use Checkout.liquid still — but only until it’s fully sunset. That gives a short-term solution if you have the technical setup for it.

I can help refactor your current tracking setup and rebuild your custom pixels the right way — either using Shopify’s pixel extensions or with a hybrid server-side method.
Let me know if you’re open to a quick fix or a long-term solution.

4

Honestly baffled by the Shopify situation over the past few months.

They claim to empower small and mid-size businesses, yet expect us to operate with in-house dev teams the size of Microsoft’s just to keep basic level tracking functional.

Now we’re left reverse-engineering platform shifts, chasing broken documentation, and patching together half-migrated tracking layers across client and server — just to get visibility on checkout events. It’s not just inefficient… it’s frankly disrespectful to the users Shopify claims to serve. Not mentioning the hours we waste every week.

I’ll start applying the recommendations, but honestly, this entire situation is surreal. Even customer care is completely clueless. :face_with_bags_under_eyes:

6

Hi Cherry1,

Unfortunately, not yet.

We ended up building a five-page custom pixel just to try and restore basic tracking, it’s a total patchwork, and despite the effort, we’re still not getting reliable events, especially on checkout.

I genuinely hope the internal teams at Shopify will take this seriously.

The situation is blocking. :smiling_face_with_tear:

Thanks again for following up !
Pierre