Converlay Now Finds the Script That's Quietly Breaking Your Tracking — and Tells You How to Fix It

Almost no Shopify store runs Converlay in isolation. By the time a merchant installs it, the theme usually already has a Google tag dropped in by a past developer, a sales channel app is firing its own pixel, a cookie banner is supposed to be gating all of it, and maybe a second analytics tool is running "just to compare." Most of that coexists fine. Some of it quietly doesn't—and until now, there was no way for a merchant to tell the difference without opening browser dev tools and reading network requests by hand.

Converlay v2.40.0 changes that. The dashboard now scans a store's live storefront for third-party scripts that conflict with its own tracking, surfaces exactly what it found, and—new in this release—hands every finding to North with a concrete, sourced fix: what to click, in which admin, and how to confirm it worked.

The Problem: Nobody Audits Their Own Theme

Conflicting scripts aren't a Converlay problem specifically—they're a Shopify-store problem that predates Converlay on most installs. A theme built two redesigns ago still has a raw gtag() snippet in theme.liquid. A sales channel app installs its own pixel through the Web Pixels Manager. A consent management app is supposed to talk to Shopify's Customer Privacy API, but a misconfigured integration means visitor choices never actually reach it. None of these throw an error. They just quietly cost the merchant clean data: the same purchase reported twice to the same ad platform under two different tracking setups, or events flowing to a destination that a shopper explicitly opted out of.

Converlay's own pixel and server-side delivery were never the fragile part—Shopify's sandboxing and Converlay's backend already isolate that. The fragile part was always everything else running alongside it, invisible to a merchant who has no reason to know what scripts their store is even loading.

What the Scan Actually Checks

The new compatibility scan runs against a catalog of 70+ known scripts and tools—tag managers, GA4, ad pixels, sales-channel trackers, other tracking apps, product analytics, email/SMS platforms, session replay tools, and roughly 35 consent-management platforms with their own Shopify sync behavior. For each one it finds running on the storefront, it checks two things that actually matter to a merchant's numbers:

• Double reporting. Is the same platform being fed the same event twice through two different paths—for example, a theme's own GA4 tag running next to Converlay's GA4 destination, both firing on every purchase? Every non-Converlay GA4 or Google tag next to Converlay's destination for the same property doubles page views, product views, and cart events—there should be exactly one sender per event.
• Consent sync. If a consent banner is installed, does its visitor choice actually reach Shopify's Customer Privacy API, or does it just hide a cookie banner while every tag keeps firing underneath it? The scan reports each consent tool as synced, partially synced, unverified, or not synced at all—a distinction most merchants have no way to check themselves.

Results show up as a new Compatibility card on the dashboard's Health page, run automatically at install and re-checked on demand, with a 30-day freshness window so a merchant always knows how current a result is before acting on it.

From "Here's a Problem" to "Here's the Fix"

A list of conflicting scripts is only useful if a merchant knows what to do about it, and that's the part v2.40.0 actually adds. Every finding on the Compatibility card now carries merchant-facing remediation steps—the click path in Shopify admin or the offending app's own settings, what will keep working after the change, and how to verify the fix landed—sourced from that vendor's or Shopify's own documentation and marked as verified, likely, or inferred depending on how firmly that path was confirmed.

Next to each finding sits an "Ask North how to fix this" button. Click it, and North walks through the fix conversationally—one finding at a time, most severe first, with a verification step at the end and an offer to re-scan once the change is live. Ask it directly and it can also explain what the scan can't see: a scan reads what's running in the browser right now, not every script that could ever load, so North is upfront about that boundary instead of implying a clean scan means a guaranteed-clean store.

Also in v2.40.0: Playing Nicer With What's Already There

Alongside the scan, this release tightens how Converlay itself behaves next to the scripts it's now reporting on. With analytics consent granted but ad consent denied, the pixel used to correctly withhold dedicated ad click-ID fields—but the page URL and referrer it recorded could still carry an fbclid or gclid query parameter through to the server and into an ad platform's event log. Both the pixel and SDK now strip click-ID parameters from those URLs whenever ad consent isn't granted, while leaving UTM parameters and everything else intact.

A same-property guard that used to block enabling a second GA4 or server-side GTM destination has also been narrowed: it now only stops a destination from being newly turned on against a property another destination already owns, instead of accidentally demoting one that's already running—so tightening the guard rail doesn't itself become a new outage.

Why This Matters More Than a Bigger Catalog Number

Converlay exists to close the gap between what actually happens on a Shopify storefront and what ad platforms and analytics tools report back. A merchant with a duplicate GA4 tag isn't getting bad data from Converlay—they're getting good data from Converlay mixed with duplicated data from something else, and until now there was no way to see that mixture, let alone untangle it. The compatibility scan doesn't just flag noise; it's a direct line from "something feels off" to a specific, sourced fix, without needing a developer to read through theme source code first.

Converlay connects your Shopify store to 26 destinations—including Meta, Google Analytics 4, TikTok, Pinterest, Klaviyo, and more—via server-side event delivery, and now scans for the third-party scripts most likely to be quietly working against it.

Install Converlay from the Shopify App Store and check the Health page—the Compatibility card runs automatically, and North is one click away from every finding it reports.