Properly setting up tracking pixels and trackers is essential for online stores. Accurate tracking optimizes ad performance and drives online sales growth.
In this guide, we walk through client-side tracking in Multifeeds: the Shopify custom pixel, the web tracking container, and client trackers. Server-side tracking (SST) is optional and builds on this same pixel — it does not replace it.
New to SST? See The Power of Server-Side Tracking and How to set up Server-Side Tracking.
Client-side setup is the source of every tracking event. The Shopify custom pixel listens to storefront and checkout events, pushes them into the data layer, and loads tracking. Client trackers and server trackers both depend on that stream.
Layer | What it does |
Custom pixel (Shopify Customer events) | Captures storefront events ( |
Web container (client trackers) | Fires browser trackers (GA4, Meta Pixel, Google Ads, and others) from those events. |
Server tracking (SST, optional) | Forwards the same events to platforms after they leave the storefront, which improves accuracy and reduces browser load. |
Until client steps 1–2 are complete, Turn on Server side tracking stays blocked.
Before diving into the setup process, it is important to understand why tracking is essential:
Tracking conversions: See how many users purchase after clicking your Shopping ads.
Optimizing campaigns: Improve ad targeting with better data insights.
Retargeting users: Show ads to people who interacted with your products.
The app uses Shopify's custom pixel, which is available on all Shopify plans.
To create the pixel, copy the custom pixel script from Multifeeds and paste it in Shopify Admin → Settings → Customer events. That script is the pipeline for all events — including events that later go to a server container.
If the app shows Update your custom pixel (or an Outdated badge), copy the new script, replace the code in Customer events, then Verify in the app. A stale pixel can affect tracking accuracy and blocks installing new trackers.
In Multifeeds, go to Pixel & Tags → Client side tracking (/pixels/trackers/client).
Complete Initialize tracking and generate pixel script.
This creates your web tracking container and the tracking loader used by the custom pixel.
Go to Shopify Settings → Customer events.
Click Add custom pixel → give it a name (for example, Multifeeds) → Add pixel.
In Customer privacy:
Under Permission, select Not required (recommended).
Under Data sale, select Data collected does not qualify as data sale (recommended).
Clear the entire Code section → paste the script from the app → Save → Connect.
Return to Multifeeds and click Verify.
On Client side tracking → Installed trackers, add trackers for the platforms you use (Google Ads, GA4, Meta Pixel, and others). Each client tracker installs into your web tracking container.
Adding a new tracker
Create a new tracker from Install tracker.
Once added, you can check the tracker status in your Google Ads account.
It may take a few days for the status to change from Inactive to Active.
To verify if the tracker is working correctly:
Hover over the status to check for any errors.
If an issue exists, a Need Attention status will appear. Navigate to Diagnostics and follow the provided instructions to fix it.
Once everything is set up correctly, your tracker should appear as Active.
When SST is on, many trackers should run on the server (for example, GA4 server and Google Ads conversions). That offloads work from the storefront and improves delivery.
Keep the client tracker when the platform expects browser and server events together. Multifeeds sends the same event_id on both paths so the platform can reconcile hits instead of counting them twice.
Platform | Typical setup |
GA4 | Prefer the server GA4 tracker after SST is active. Pause a client GA4 tracker that uses the same Measurement ID to avoid duplicate events. |
Meta | Run Meta Pixel (client) and Meta Conversions API (server) together. Events share |
TikTok (and similar) | Same dual-path idea: browser pixel + Events API, reconciled by event ID. Multifeeds does not currently ship a native TikTok tracker; configure that pattern if you add TikTok outside the app. |
Server trackers require SST to be on, the tracking server Active, and a current custom pixel.
The custom pixel script includes the tracking loader URL. Several server-side changes regenerate that script. Until you paste the new code in Shopify and Verify, storefront events may still use the old loader.
Change | What to do |
Turn on or remove server-side tracking | Copy the new script → replace the custom pixel in Customer events → Verify. |
Change tracking domain (first-party ↔ WoolyTech managed, or a new subdomain) | Same as above. First-party SST serves the loader from your domain (for example |
Tracking version / metafields / script settings | Copy the updated script and verify. The app shows a yellow Update your custom pixel banner when the installed hash does not match. |
Until the pixel is current, installing client or server trackers stays blocked.
For deeper insights, you can enable Enhanced Conversion Tracking (ECT) in Google Analytics 4 (GA4).
What is Enhanced Conversion Tracking?
Enhanced conversion tracking is an advanced tracking method that improves the accuracy of conversion data by securely sending first-party customer information (for example email addresses, phone numbers, or hashed user data) from websites to ad platforms like Google Ads. This data is then matched with existing user profiles to track conversions more precisely.
How to Enable Enhanced Conversion Tracking
Open your Google Ads account.
Navigate to Goals → Summary.
Enable Enhanced Conversions and follow the setup instructions.
After setting up Pixel and trackers, test whether they are functioning correctly.
Ways to test your setup:
Test Add to Cart and Begin Checkout trackers → Chrome extension: Datalayer Checker Plus.
Test Enhanced Conversion Tracking (ECT) → Chrome extension: EC Assist.
Test with Developer Tools → inspect events in the browser.
Setting up Pixel and trackers in Multifeeds helps you optimize ads, track sales, and improve ROI. Keep the custom pixel current whenever you change SST or the tracking domain so every event still originates from the storefront.
If you encounter any issues, double-check your IDs and trackers, or contact Multifeeds support.
