Hello everyone,
Additional tracking pixels (Meta, TikTok, Google, Klaviyo) and third-party apps frequently begin to affect checkout and site loading times as retailers expand.
I was curious about your current approach to maintaining a quick storefront without missing out on important marketing information. Do you limit the number of active scripts, employ custom pixel apps, or use Google Tag Manager server-side tracking?
I’d love to know what’s currently working well for your stores.
Hey @angelina-new-user ,
For me, the first step is keeping track of which scripts and apps are actually being used. It’s pretty easy for a store to end up with several apps loading scripts that aren’t really needed anymore.
I usually try to remove anything unnecessary and then test the store speed again, especially on mobile. I also think it’s better to look at the actual impact of each script rather than just setting a random limit on how many scripts can run.
The goal is to keep the tracking that’s actually useful while avoiding scripts that add extra load without giving much value.
Thank You!
Hello @angelina-new-user Thanks for reaching out to Shopify community with your concern. I recently fixed a client’s store who had multiple tracking scripts which resulted in low loading speed of the page. Hence the checkout experience gets slow too.
First of all you need to identify which tracking pixel is actually useful/needed in order to make your store or customer journey easy to checkout. Once that is identified, make sure every script is not loading on every page or an event is firing just on the page it needs to be. Sometimes some events can be triggered after few seconds of the page load.
Also, I personally prefer Google Tag manager server side tracking to manage everything at one place. Again, thats just a personal choice. You can choose the best approach by identifying and testing which approach works best for your store.
I’ve found that the easiest way to keep this under control is to be pretty ruthless about what actually needs to load on the storefront. A lot of apps add scripts that are technically useful but don’t necessarily need to run on every page, so I’d rather remove or limit those before trying to optimize around them.
For tracking, I’d keep the core pixels that actually influence marketing decisions and avoid installing multiple apps that are all sending essentially the same events. I’ve also found that checking the actual network requests is more useful than just looking at a speed score. Sometimes a script looks scary in the report but has very little impact, while another small script can cause a noticeable delay.
I use SiteGuru for the broader technical side of the store, and I think the same principle applies here. Keep the storefront as simple as possible, then add tracking when there’s a clear reason for it. Server-side tracking can help with certain setups, but I wouldn’t add that complexity unless the extra data or attribution is actually worth maintaining.
The biggest question for me is always whether the tracking data is being used. If nobody is making decisions from a particular pixel or event, I’d seriously question whether it needs to be slowing down the store.
Currently, the best strategy is to use Server-Side Tracking rather than loading complex client-side scripts in theme.liquid:
Shopify Web Pixels API: Run marketing pixels in a sandboxed environment without preventing page renders by utilizing Shopify’s built-in Customer Events.
Server-Side GTM (sGTM): Transmit a single data payload from your website to a tagging server (like Stape.io), which uses an API to transmit data to Meta CAPI, TikTok, Google, and Klaviyo.
Script Audit: Use GTM or Web Pixels to handle all tracking and avoid using raw JavaScript in theme files.
In summary, server-side tracking (sGTM + Meta CAPI) preserves 100% data correctness without compromising checkout or store speed!
Hello @angelina-new-user, Kim267 and alinacarrie above have this right, Web Pixels via Customer events is the way to go since those run sandboxed and can’t block checkout rendering the way theme-injected scripts do. One thing worth checking on top of that: audit for duplicate events, it’s common to end up with the same pixel firing twice once you stack a native app integration and a manually added GTM tag for the same platform, which inflates your numbers without adding any real speed cost you can trim. Thanks
What’s worked best for us is treating tracking like an app audit, not setting a fixed script limit.
I’d audit quarterly and after every app install. Also verify consent behavior and event totals before and after each change.
One distinction that gets missed is that “server-side” does not automatically mean faster or 100% accurate. I’d baseline each script by route and event: storefront/checkout-entry load, long tasks, transfer size, consent state, event delivery and duplicate rate. Keep a safe comparison window, then check PDP → add to cart → checkout entry → purchase by device. Shopify Web Pixels can reduce theme coupling, but a slow app block or duplicate request can remain. My decision rule is simple: retain a pixel only when its data changes a marketing decision; otherwise remove it or move it off the critical path. Check field performance on mobile, not just a Lighthouse score.
@angelina-new-user the checkout half of your question has a shorter answer than the storefront half: on the upgraded checkout nothing from the theme runs, not theme.liquid and not an app embed. What Shopify does allow on checkout pages is checkout UI extensions and web pixels, and a pixel runs in its own sandbox, with no access to the page and nothing on the page waiting for it. Trimming pixels in the theme changes how fast your product pages feel and changes nothing about checkout.
On pixel apps, we built WeltPixel Conversion Tracking ourselves, so it is the app I can speak for, and the plan covering all four platforms you listed costs 39 a month. What any of them adds to the storefront depends on whether it also loads the platform scripts in the theme for the browser side, ours included, so ask each of them that before installing.
For the speed question, I’d first keep tracking out of theme/checkout markup and audit it under Settings → Customer events. Use the official Facebook & Instagram by Meta, Google & YouTube, and TikTok customer-event apps first where each covers your needs; remove duplicate pixels, subscribe only to the events you need, then test checkout speed and purchase counts. That avoids piling several legacy scripts onto the critical path.
If you still need custom multi-network files after the Additional Scripts cutoff, I make and sell a $24 Custom Pixel Multi-Ad Kit for Meta + Google + TikTok: Shopify Custom Pixel Multi-Ad Kit (Meta + Google + TikTok) — Post–Additional Scripts. It’s paste-ready browser-side Custom Pixel files, not CAPI or server-side GTM.
Hello @angelina-new-user, @thriftoindia and @koncz.szabi are both right that consolidating into Customer events beats stacking legacy scripts. One more reason to make that move if you’re on the newer checkout: Additional Scripts is being phased out and simply doesn’t fire on many checkouts anymore, so a pixel still living there isn’t just slow, it may already be silently not running at all. Customer events (Settings > Customer events > Add custom pixel) is the only place guaranteed to still fire post-migration.
If this helped, please mark it a solution
Hi there @koncz.szabi
Keeping the storefront minimal-bin is usually the best way to go. I’d regularly audit pixels and scripts, disable or remove anything that’s no longer needed, and only load nonessential tracking where it really adds value. Shopify’s customer events and pixels also allow you to centralze tracking as opposed to the need to add multiple scripts directly to the theme. I’d watch checkout, page performance, after every change, especially on high traffic days. In general, clean data and improved performance is what you get with a smaller number of well architected tracking events rather than including every single script available to you.