1. Why ecommerce stores lose so much analytics data
Ecommerce stores feel the ad blocker gap harder than most sites do. Checkout flows lean on GA4 ecommerce events, Meta Pixel purchase events feed ad optimization, and a GTM container usually stitches the two together. All three depend on a script loading from google-analytics.com, googletagmanager.com, or connect.facebook.net, and those domains sit on nearly every filter list in circulation.
29.5% of internet users worldwide used an ad blocker in Q2 2025, according to the adoption survey cited in our statistics guide. That figure is not the percentage of store sessions or purchases lost. Test your storefront and checkout events to measure the effect on your own setup.
Why this matters more for stores than blogs
A missed pageview on a content site barely registers. A missed purchase event on a store under-reports revenue directly, throws off ROAS math, and leaves your ad platforms bidding without the conversion signal they need.
Introtrace runs alongside your existing tags, serving supported blocked scripts and relaying blocked event requests. Recovery uses cdn.introtrace.com by default; paid plans support a custom subdomain through CNAME configuration. Test the pages and events you rely on, including their consent behavior.
2. Shopify setup
For theme-rendered storefront pages, add Introtrace directly to theme.liquid. This does not install it in Shopify checkout or the customer-events sandbox.
Get your script tag
Create a free Introtrace account and copy the organization script from Settings. It looks like a single <script> tag with your organization ID.
Open theme.liquid
From your Shopify admin, go to Online Store → Themes → Edit code, then open layout/theme.liquid.
Place before analytics scripts
Add the Introtrace script near the start of <head>, before your analytics and consent scripts.
Save and preview
Save the file and load your storefront with an ad blocker enabled to confirm the script loads (check the Network tab for cdn.introtrace.com or your configured paid-plan subdomain).
Shopify’s custom pixels run in a sandbox. A script running there cannot be assumed to intercept requests made by other tags or the storefront. Contact us before choosing this route for Introtrace.
3. Shopify checkout & thank-you page
The storefront is only half the picture — your checkout and order confirmation pages are where purchase and add_payment_info events fire, and theme.liquid doesn't apply to checkout pages.
Do not use the old checkout.liquid or Additional scripts instructions. Shopify has retired those integration paths; see Shopify’s checkout documentation.
Review the pixel or app that currently sends your checkout events. Verify whether Introtrace can run in that environment and recover its requests; a successful storefront test does not establish purchase-event coverage.
4. WooCommerce setup
WooCommerce runs on WordPress, so you have more flexibility — and more options for adding a script sitewide without editing theme files directly.
Option A: header/footer plugin
Plugins like "Insert Headers and Footers" or "WPCode" let you paste the Introtrace script tag into the site-wide <head> section without touching theme code. This is the safest option if you don't want to risk theme updates overwriting your changes.
Option B: edit header.php
If you edit theme files, add the script near the start of <head> in header.php, before analytics and consent scripts. Use a child theme so the change survives theme updates.
Avoid loading recovery through GTM
Add Introtrace independently of GTM, using a header plugin or your child theme. If GTM is blocked, an Introtrace tag inside that container cannot load to recover it.
WooCommerce's checkout and order-received pages are regular WordPress pages, so a sitewide header script can cover them, but verify the rendered checkout and order-received pages — unlike Shopify, there's no separate checkout templating system to work around.
5. Verifying it's working
Use the GA4 recovery testing checklist to compare the same event with blocking off, blocking on, and recovery enabled. Repeat it for your checkout events as well as storefront page views.
Once the script is live, confirm recovery is working before assuming everything's connected:
- Open your storefront in a browser with uBlock Origin or Brave Shields enabled
- Open DevTools → Network tab and filter for cdn.introtrace.com or your configured recovery subdomain
- Confirm requests to google-analytics.com / googletagmanager.com / facebook.com that would normally be blocked are now being proxied successfully
- Check Introtrace for recovery activity; verify event names and values in your analytics platform
- Compare GA4 real-time reports before and after — verify the specific pageview and conversion you triggered, allowing for reporting delays
Hold off on conclusions from GA4 or Meta Ads Manager for a few days; both have reporting delays. Compare equivalent periods and account for traffic changes, consent settings, and event deduplication.
Summary
On WooCommerce, install through the sitewide header and verify checkout separately. On Shopify, theme installation covers theme-rendered storefront pages; checkout and sandboxed pixels require their own compatibility checks. In both cases, confirm recovered events reach GA4 or Meta before relying on the reports.
Global ad blocker adoption does not tell you how many store purchases are missing. Measure your recovered events and compare attribution only after verifying delivery and deduplication.
Recover your store's blocked conversions
Install on your storefront and verify supported GA4, GTM, and Meta Pixel requests. Check checkout compatibility separately. Free to start, with 20,000 signals per 30 days included.
Frequently asked questions
Does Introtrace require a Shopify app?
For theme-rendered storefront pages, add the script directly to theme.liquid. Shopify checkout and customer-event pixels run in a different environment; do not assume a theme script covers them. Contact us to verify your checkout setup before relying on recovery there.
Will this slow down my Shopify or WooCommerce store?
The script downloads asynchronously, but still adds browser-side work. Measure page performance before and after installation with the same tags and recovered events. The default host is the shared CDN; a custom subdomain requires a paid plan.
Does this replace GA4, GTM, or Meta Pixel on my store?
Nothing to replace. Your GA4, GTM, and Meta Pixel setup keeps running exactly as it is; Introtrace just catches the requests an ad blocker would have dropped and forwards them through cdn.introtrace.com by default, or your own subdomain if you've set up a CNAME on a paid plan. Either path, the same destinations keep getting the data.
Do I need to modify my checkout or thank-you page separately?
Shopify’s checkout, Thank you, and Order status pages do not use theme.liquid. The old checkout.liquid and Additional scripts paths have been retired. Current pixel integrations run in a sandbox, so verify Introtrace compatibility with your specific setup before expecting checkout recovery.
