---
title: "How to set up Pixel and trackers with Multifeeds"
description: "Tracking setup wizard, dashboard, and browser and server trackers"
url: https://docs.woolytech.com/en/articles/202-how-to-set-up-pixel-and-trackers-with-multifeeds
collection: "Tracking tags"
updated: 2026-11-17
language: en
---

# How to set up Pixel and trackers with Multifeeds

Tracking setup wizard, dashboard, and browser and server trackers

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](https://docs.woolytech.com/en/articles/238-server-side-tracking.md).
    

## How tracking fits together

The Shopify custom pixel is the **source of every tracking event**. Browser and server trackers both depend on it.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #f6f6f7; vertical-align: top; border: 1px solid #ddd;"><p><strong>Layer</strong></p></td><td colspan="1" rowspan="1" style="font-weight: bold; background: #f6f6f7; vertical-align: top; border: 1px solid #ddd;"><p><strong>What it does</strong></p></td></tr><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #fafafa; vertical-align: top; border: 1px solid #ddd;"><p><strong>Custom pixel (Shopify Customer events)</strong></p></td><td colspan="1" rowspan="1" style="vertical-align: top; border: 1px solid #ddd;"><p>Captures storefront events (<code>page_view</code>, <code>add_to_cart</code>, <code>purchase</code>, and so on) and attaches a shared <code>event_id</code>.</p></td></tr><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #fafafa; vertical-align: top; border: 1px solid #ddd;"><p><strong>Web container</strong></p></td><td colspan="1" rowspan="1" style="vertical-align: top; border: 1px solid #ddd;"><p>A Google Tag Manager container Multifeeds creates for you. Browser trackers run from it.</p></td></tr><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #fafafa; vertical-align: top; border: 1px solid #ddd;"><p><strong>Tracking server (optional)</strong></p></td><td colspan="1" rowspan="1" style="vertical-align: top; border: 1px solid #ddd;"><p>Receives the same events from your own domain and forwards them to platforms. Server trackers run from it.</p></td></tr></tbody></table>

## Set up tracking with the wizard

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.

### Step 1: Pixel

1.  Click **Copy script & open Customer events**. The script is copied and Shopify **Settings → Customer events** opens in a new tab.
    
2.  Click **Add custom pixel**, name it (for example, Multifeeds), then **Add pixel**.
    
3.  In **Customer privacy**:
    
    -   **Permission**: select **Not required** (recommended).
        
    -   **Data sale**: select **Data collected does not qualify as data sale** (recommended).
        
4.  Clear the **Code** box, paste the script, click **Save**, then **Connect**.
    
5.  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**.

### Step 2: Tracking mode

-   **Server side** (recommended): browser tracking plus your own tracking server. Continue with the Server step, see [How to set up Server-Side Tracking](https://docs.woolytech.com/en/articles/238-server-side-tracking.md).
    
-   **Browser only**: trackers run in the shopper's browser. You can turn on server side later from the dashboard.
    

### Step 3: Launch

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.

### Step 4: First tracker

Install at least one tracker (for example GA4 or Meta), then click **Finish**. From then on, **Tracking** opens the dashboard.

## The Tracking 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.

## Install trackers

1.  On the dashboard, click **Install tracker** and pick a tracker.
    
2.  Fill in the tracker's IDs (for example a GA4 Measurement ID or a Google Ads Conversion ID and label) and choose its events.
    
3.  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.

## Browser and server trackers together

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.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #f6f6f7; vertical-align: top; border: 1px solid #ddd;"><p><strong>Platform</strong></p></td><td colspan="1" rowspan="1" style="font-weight: bold; background: #f6f6f7; vertical-align: top; border: 1px solid #ddd;"><p><strong>Typical setup</strong></p></td></tr><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #fafafa; vertical-align: top; border: 1px solid #ddd;"><p><strong>GA4</strong></p></td><td colspan="1" rowspan="1" style="vertical-align: top; border: 1px solid #ddd;"><p>Use the <strong>server</strong> GA4 tracker once server side is live. Pause a browser GA4 tracker with the same Measurement ID to avoid duplicate events.</p></td></tr><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #fafafa; vertical-align: top; border: 1px solid #ddd;"><p><strong>Meta</strong></p></td><td colspan="1" rowspan="1" style="vertical-align: top; border: 1px solid #ddd;"><p>Run <strong>Meta Pixel</strong> (browser) and <strong>Meta Conversions API</strong> (server) together. Events share <code>event_id</code> so Events Manager can match them.</p></td></tr><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #fafafa; vertical-align: top; border: 1px solid #ddd;"><p><strong>Google Ads</strong></p></td><td colspan="1" rowspan="1" style="vertical-align: top; border: 1px solid #ddd;"><p>Use the server conversion tracker once server side is live.</p></td></tr></tbody></table>

## When you must update the pixel

The custom pixel script includes the address your tracking loads from. These changes generate a new script:

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #f6f6f7; vertical-align: top; border: 1px solid #ddd;"><p><strong>Change</strong></p></td><td colspan="1" rowspan="1" style="font-weight: bold; background: #f6f6f7; vertical-align: top; border: 1px solid #ddd;"><p><strong>What to do</strong></p></td></tr><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #fafafa; vertical-align: top; border: 1px solid #ddd;"><p><strong>Turn server side on or off, or change the tracking domain</strong></p></td><td colspan="1" rowspan="1" style="vertical-align: top; border: 1px solid #ddd;"><p>Copy the new script, replace the code in your Multifeeds custom pixel in Customer events, and save.</p></td></tr><tr><td colspan="1" rowspan="1" style="font-weight: bold; background: #fafafa; vertical-align: top; border: 1px solid #ddd;"><p><strong>Tracking script settings (metafields, consent) or a new script version</strong></p></td><td colspan="1" rowspan="1" style="vertical-align: top; border: 1px solid #ddd;"><p>Same as above.</p></td></tr></tbody></table>

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 for Google Ads

Enhanced conversions send hashed first-party customer data (such as email) with conversions, which improves match rates.

1.  Open your **Google Ads** account.
    
2.  Go to **Goals → Summary**.
    
3.  Turn on **Enhanced conversions** and follow the setup instructions.
    

## Testing your setup

-   **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.

## Related articles

-   [How to set up Server-Side Tracking in Multifeeds](https://docs.woolytech.com/en/articles/238-server-side-tracking.md)
    
-   [What is first party domain (for server side tracking)](https://docs.woolytech.com/en/articles/239-what-is-first-party-domain-for-server-side-tracking.md)
    
-   [The Power of Server-Side Tracking](https://docs.woolytech.com/en/articles/218-server-side-tracking-benefits.md)
