Accurate tracking lets your ad platforms see which clicks turn into sales, so they can optimize your campaigns. This guide walks through tracking setup in Multifeeds: the Shopify custom pixel, the setup wizard, and installing trackers.
Multifeeds supports two kinds of trackers:
Browser trackers run in the shopper's browser (GA4, Meta Pixel, Google Ads, Pinterest, Awin).
Server trackers run on your own tracking server (GA4, Google Ads, Meta Conversions API). They need server side tracking. See How to set up Server-Side Tracking.
The Shopify custom pixel is the source of every tracking event. Browser and server trackers both depend on it.
Layer | What it does |
Custom pixel (Shopify Customer events) | Captures storefront events ( |
Web container | A Google Tag Manager container Multifeeds creates for you. Browser trackers run from it. |
Tracking server (optional) | Receives the same events from your own domain and forwards them to platforms. Server trackers run from it. |
In Multifeeds, open Tracking. A new store sees the setup wizard, with a progress bar at the top. You can leave the page at any time; setup continues in the background and the wizard resumes where you left off.
Click Copy script & open Customer events. The script is copied and Shopify Settings → Customer events opens in a new tab.
Click Add custom pixel, name it (for example, Multifeeds), then Add pixel.
In Customer privacy:
Permission: select Not required (recommended).
Data sale: select Data collected does not qualify as data sale (recommended).
Clear the Code box, paste the script, click Save, then Connect.
Come back to Multifeeds. The app checks your storefront automatically and moves on once it finds the new script. You can also click Verify pixel.
Shopify may warn that the pixel is not subscribed to any events. You can safely ignore this: Multifeeds subscribes to events from its tracking script.
If your storefront is password protected, the app asks for the storefront password to check it. If the check still cannot reach your store, use Verify in a new tab.
Server side (recommended): browser tracking plus your own tracking server. Continue with the Server step, see How to set up Server-Side Tracking.
Browser only: trackers run in the shopper's browser. You can turn on server side later from the dashboard.
Multifeeds creates your web container in the background (usually 2–5 minutes). The checklist on the right shows each part as it finishes. With server side, the Launch step also connects your domain, starts the tracking server, and asks you to update the pixel once (see the server side guide).
If setup gets stuck, Start over removes what was created so far and returns to the first step. Your Shopify custom pixel stays.
Install at least one tracker (for example GA4 or Meta), then click Finish. From then on, Tracking opens the dashboard.
The dashboard is on the Settings tab of the Tracking page. It has two sections in one card.
Infrastructure
Pixel: Verified, Outdated (the storefront runs an older script), Not verified, or Verifying. When the pixel is outdated or not verified, the app re-checks your storefront automatically while the page is open. Re-verify checks again on demand.
Tracking script: the script version, marked Latest when it is current.
Server (with server side): your tracking domain, server location, response time, requests in the last 24 hours, and a link to Reports.
Configure: tracking script settings, server settings (or Turn on server side tracking), and container previews.
Remove (trash icon): remove server side tracking only, or remove all tracking.
Trackers
Browser and Server tabs list your installed trackers. Use the filter next to Vendor ID to show one tracker type.
Install tracker lists server trackers and browser trackers in separate sections, with the credits each one uses. Without a tracking server, the server section offers Activate server side instead.
While you have free tracker credits left, a banner below the card shows how many.
Reports (the tab next to Settings) shows your tracking server's traffic: requests, status codes, events, countries, and devices.
On the dashboard, click Install tracker and pick a tracker.
Fill in the tracker's IDs (for example a GA4 Measurement ID or a Google Ads Conversion ID and label) and choose its events.
Click Save. Multifeeds installs it into your web container (browser) or server container (server) and publishes the change.
Google Ads: after you add a conversion tracker, it can take a few days for its status in Google Ads to change from Inactive to Active. If Google Ads shows Needs attention, open Diagnostics there and follow the instructions.
When server side is on, prefer server trackers where the platform supports them. Some platforms expect browser and server events together; Multifeeds sends the same event_id on both paths so the platform can match them instead of counting twice.
Platform | Typical setup |
GA4 | Use the server GA4 tracker once server side is live. Pause a browser GA4 tracker with the same Measurement ID to avoid duplicate events. |
Meta | Run Meta Pixel (browser) and Meta Conversions API (server) together. Events share |
Google Ads | Use the server conversion tracker once server side is live. |
The custom pixel script includes the address your tracking loads from. These changes generate a new script:
Change | What to do |
Turn server side on or off, or change the tracking domain | Copy the new script, replace the code in your Multifeeds custom pixel in Customer events, and save. |
Tracking script settings (metafields, consent) or a new script version | Same as above. |
The dashboard marks the pixel Outdated until the storefront runs the new script, and checks again automatically. Installing new trackers stays blocked while the pixel is outdated.
Enhanced conversions send hashed first-party customer data (such as email) with conversions, which improves match rates.
Open your Google Ads account.
Go to Goals → Summary.
Turn on Enhanced conversions and follow the setup instructions.
GA4: open Reports → Realtime in GA4 while you browse your store.
Google Ads and GA4 tags: Google Tag Assistant, or Configure → Preview web container on the Tracking dashboard.
Data layer events: the Chrome extension Datalayer Checker Plus.
Enhanced conversions: the Chrome extension EC Assist.
If something does not work, check your IDs and the tracker's events, or contact Multifeeds support.