The Black Friday Theme That Silently Turned Off Conversion Tracking

The tracking broke, and the broke was the date, and the date was the theme, and the theme was the publish, and the publish was the holiday redesign, and the redesign was the new theme, and the new theme was the embed, and the embed was the per theme, and the per theme was the off, and the off was the silent, and the silent was the purchases still arriving, and the still arriving was the weaker matching, and the weaker matching was the ad account's slow bleed.

This is the anatomy of the per-theme app embed, and it is worth reading this week specifically, because the October script-tag deadline pushed a lot of stores onto theme app extensions, and the holiday theme publish is the step that quietly undoes that migration.

If your store or your clients publish a seasonal theme in the next six weeks, this is the failure to check for on the day you publish, not the day the ad data looks strange.

What actually changed, and what did not

On 1 October 2026 Shopify blocked storefront script tag writes. scriptTagCreate and scriptTagUpdate return a permission error on every API version, the REST ScriptTag resource rejects POST and PUT, and pinning an older API version does not defer it. Existing script tags keep running until 1 March 2027, and the read and delete operations still work, so the migration is urgent for new installs and merely scheduled for everyone else.

The replacement for anything that only collects data is a web pixel, which the developer ships and the merchant never touches. The replacement for anything that shows something on the page, or that bridges browser data to server-side events, is an app embed block inside a theme app extension. That second path is where the trap lives.

Shopify does not enable app embeds on install, and the toggle is per theme rather than per store. The path is Online Store, then Themes, then Customize, then the App embeds panel, then the toggle, then save.

Why the theme publish is the trigger

A new theme is a new set of embed toggles, all starting off. Publishing the Black Friday theme therefore deactivates the tracking embed that was working on the old theme, and nothing in the publish flow warns you, because from Shopify's perspective nothing broke. A new theme was published and its embeds are in their default state, which is off.

The failure is quiet in a specific and expensive way. Browser events still fire, so the pixel looks alive in the platform's debugger. What stops is the browser-captured attribution data, the click IDs and cookies in the _fbp, gclid and rdt_cid family, which never make it onto the order for server-side use. Purchases still track. Match quality drops and deduplication mismatches rise, which shows up weeks later as a soft divergence between your Shopify order count and the conversions your ad platforms report, with no deploy, no app update and no error on the inflection date.

Tracking agencies report this as the single most common cause of tracking that died on a specific date, and the date is almost always a theme change.

This is the same shape as the theme update that reverted the checkout edits, where a routine theme operation silently removed customisations that lived in the theme rather than above it. The embed toggle is the same kind of state: attached to the theme, invisible in the app, and reset by an action that has nothing to do with tracking.

The second silent failure sitting underneath

While you are in there, check the pixel's data-sharing mode. Since 13 January 2026 Shopify has defaulted marketing app pixels to Optimized mode, which lets the platform wind down or pause a pixel's data sharing when it judges the signal to be low value. There is no merchant-facing alert. Since 29 June 2026 the pause is at least recorded as a dated entry in the app pixel activity log on the pixel's detail page, but only if you go and look.

The fix is one setting per pixel: Settings, then Customer events, then the App pixels tab, then the pixel's setting in the Data column, then set Mode to Always on. Custom pixels you added yourself are not affected.

Two independent silent failures, both defaulting to the unsafe direction, both surviving install-day QA because both work correctly on day one and decay later. That combination is why a tracking stack that passed its setup checklist in September can be quietly degraded by November.

What to do this week

Audit before the theme publish, not after. In the admin, Settings then Customer events lists your web pixels. Anything your tracking depends on that is not in that list is probably still a script tag, and script tags stop being injected on 1 March 2027.

Re-enable the embed on the new theme before you publish it. Do it on the unpublished theme in the customiser so the switch is already on when it goes live, rather than discovering the gap from the ad account.

Check the pixel mode on every app pixel. Set each to Always on. This takes under a minute per pixel and it removes one of the two silent failure modes entirely.

Add three standing triggers to the calendar. Any theme change, any checkout or consent-tool change, and any platform deadline. Re-run the verification after each, because all three reset state that the tracking depends on.

Overlay orders against platform purchases as a time series. The divergence is the detector, and the detector is the only thing that catches a gradual throttle, because there is no error to alert on.

The rule

Shopify app embeds are enabled per theme and default to off, so publishing a new theme silently disables browser-to-server attribution while the pixel keeps appearing to fire. Re-enable the embed on every new theme before publishing, set every app pixel to Always on, and monitor the gap between order count and platform conversions as the detector.

The pixel was never broken and the theme publish never failed, which is exactly why this costs so much. The embed toggle is per theme rather than per store, so a holiday redesign that has nothing to do with tracking turns tracking off, and the symptom is not an error but a slowly widening gap between what Shopify counted and what Meta reported, arriving in November with no obvious cause and six weeks of ad spend behind it.