--- title: "Server side tracking" description: "How to setup server side tracking in Multifeeds" url: https://docs.woolytech.com/en/articles/238-server-side-tracking collection: "Tracking" updated: 2026-11-06 language: en --- # Server side tracking How to setup server side tracking in Multifeeds Server-side tracking sends your store's analytics and ad events through your own tagging server before they reach platforms like Google Analytics 4, Meta, and Google Ads. That improves data accuracy, privacy control, and resilience against ad blockers. **New to SST?** Read [The Power of Server-Side Tracking](https://docs.woolytech.com/en/articles/218-server-side-tracking-benefits.md) for why it matters. ### Before you begin Complete **client tracking setup** first. Server-side tracking builds on the same GTM web container and custom pixel. 1. In the app, go to **Pixel & Tags → Client tracking** (`/pixels/trackers/client`). 2. Finish both onboarding steps: - **Step 1 — Initialize tracking and generate pixel script** (creates your GTM web container and tracking loader). - **Step 2 — Create a Custom pixel from the above script** (install the script in **Shopify Admin → Settings → Customer events**). If either step is incomplete, the Server tracking screen shows **Client setup required** and blocks **Turn on Server side tracking**. For detailed client pixel instructions, see [How to set up Pixel and Tags](https://docs.woolytech.com/en/articles/202-how-to-set-up-pixel-and-tags-with-the-multifeed-google-shopping-feed-app-2.md). ### Billing Server-side tracking is a **subscription add-on**: - **5 monthly credits** on your Multifeeds plan (includes **500,000 server-side tracking requests** per billing period). - **Usage charges** beyond included volume: **$1 USD per 100,000 requests** (billed on your Shopify subscription). When you first turn on SST, Shopify may ask you to approve the add-on charge. After approval, return to the app — the configuration modal opens automatically. ## Where to configure SST 1. Open **Pixel & Tags → Server tracking** (`/pixels/trackers/server`). 2. Click **Turn on Server side tracking** (or **Configure** if already enabled). 3. Complete the **Server side tracking** modal and save. ## Configuration options ### Tracking domain (recommended: First party)

Option	When to use	DNS required?	Server region
First party domain (recommended)	Production stores; best for cookie longevity and trust	Yes — CNAME at your DNS provider	You choose (see regions below)
Use WoolyTech domain	Quick testing; managed hostname per store	No	Fixed to EU

#### First party domain checklist **Why first-party?** See [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). - Use a **subdomain of your store domain** (example: `track.yourstore.com`). - Create a **CNAME** record: `your-subdomain.yourstore.com` → `sgtm-yourstore.woolytrack.org` (The app shows the exact hostname and target for your shop — use the **Copy** buttons.) - **Cloudflare users:** set the CNAME to **DNS only (gray cloud)**, not **Proxied (orange cloud)**. Orange-cloud proxying can block CNAME verification. #### WoolyTech managed domain - Uses a hostname like `sgtm-yourstore.woolytrack.org`. - No DNS setup; server is always provisioned in **EU**. - Useful for evaluation; first-party domain is recommended for live stores. ### Server location At launch, choose **EU** or **US-east** for new provisioning. The modal may show latency hints to help you pick a region close to most customers. ### GA4 Measurement ID (server-side) - Required format: `G-XXXXXXXXXX` (10 characters after `G-`). - You can pick an ID from existing **client-side GA4 trackers** in the dropdown, or type one manually. - If a **client-side GA4 tracker already uses the same Measurement ID**, pause or remove it to avoid **duplicate events**. The app warns you when this happens. Multifeeds creates a dedicated **Multifeeds | Server-side routing** GA4 configuration in your web GTM container that points `server_container_url` to your tagging server. ## Setup walkthrough ### Step 1 — Turn on and save configuration 1. Open **Server tracking** and click **Turn on Server side tracking**. 2. Approve billing if prompted. 3. In the modal: - Choose **First party domain** or **WoolyTech domain**. - Enter subdomain (if first-party). - Select **server region** (first-party only). - Enter **GA4 Measurement ID**. 4. Click **Save**. ### Step 2 — DNS (first-party domain only) After saving, a **Waiting for DNS** banner appears with your CNAME details. 1. Add the CNAME at your domain registrar or DNS host. 2. Wait for propagation (often minutes; can take up to 24–48 hours). 3. The app **checks DNS automatically** and shows a countdown until the next check — no manual refresh required. Until DNS verifies, the **tagging server is not provisioned** (by design). This avoids failed server deployments. ### Step 3 — Server provisioning Once DNS is verified (or immediately for WoolyTech managed domain), you'll see **Setting up your tracking server** / **Creating tagging server**. Provisioning usually takes **a few minutes**. During this time: - **Domain** widget: moves from _Waiting for DNS_ / _Verifying_ toward _Connected_. - **Server container** widget: _Provisioning_ → _Active_ when healthy. - **Traffic** widget: starts showing request counts when events flow. ### Step 4 — Update the custom pixel (first-party domain) After the tagging server is **Active** and Domain is **Connected**, the Shopify custom pixel still loads from the shared WoolyTech host until you update it. The first-party domain only applies to storefront events after this step. You'll see a yellow banner: **Update your Shopify custom pixel to keep tracking active**. 1. Click **Update pixel** (or open **Client tracking**). 2. Copy the new custom pixel script. The loader URL now uses your first-party domain (for example `https://track.yourstore.com/0/yourstore.js`) instead of `tl.woolytrack.org`. 3. In **Shopify Admin → Settings → Customer events**, open the existing Multifeeds custom pixel and replace its code with the new script. 4. Return to the app and **Verify** the pixel. Until the pixel is updated and verified, storefront events may not use the first-party loader even though the tagging server is online. Installing server trackers stays blocked while the pixel is out of date. **WoolyTech managed domain:** skip this step — the loader host does not change. See also [Why use a first-party domain](https://docs.woolytech.com/en/articles/239-what-is-first-party-domain-for-server-side-tracking.md) (first-party tracking loader). ### Step 5 — Install server-side trackers (optional but typical) After the server container is **Active** and the custom pixel is current, install trackers on **Server tracking → Installed trackers**: - Examples: GA4 (server), Meta CAPI, Google Ads conversions — each installs into your **server GTM container**. - Client trackers and server trackers are separate; server trackers require SST to be on and the server container ready. See the Trackers section of the knowledge base for platform-specific guides. ## Understanding the status widgets

Widget	What it means
Domain	DNS/CNAME health and whether your tracking hostname resolves correctly
Server container	Whether the tagging server pod is provisioned and responding
Traffic	Recent server-side request volume (updates every few seconds when live)

**Badge states you may see** - _Waiting for DNS_ — add or fix your CNAME. - _Provisioning_ / _Updating_ — infrastructure or GTM server container work in progress. - _Active_ — server is operational. - _Unreachable_ — hostname resolves but health check failed; recheck DNS (especially Cloudflare proxy) or contact support. ## Reconfigure or change settings Click **Configure** on the Server tracking card to change: - Custom domain or switch between first-party and Wooly managed domain - Server region (subject to launch availability) - GA4 Measurement ID Major domain or region changes may trigger **re-provisioning**; expect brief _Updating_ states. ## Turn off server-side tracking Click **Remove server side tracking** (destructive). This **permanently removes**: - Your tagging server infrastructure - Server GTM container configuration - Server-side trackers (including **Multifeeds | Server-side routing**) Client pixel and web GTM container remain unless you remove them separately. ## Troubleshooting

Symptom	What to try
Client setup required	Finish client steps 1–2 on `/pixels/trackers/client`
Client container not ready	Wait for GTM web container initialization to complete (step 1)
Waiting for DNS stuck	Confirm CNAME host/target match the app exactly; disable Cloudflare proxy on the CNAME
Server not available / unknown tagging server URL	Click Reconfigure and save again with the correct domain
Duplicate GA4 events	Pause client GA4 tracker using the same Measurement ID
Pixel script "Outdated" / yellow update banner after the server is Active	Expected for first-party domain. Complete Step 4 so the custom pixel loads from your domain. During DNS or provisioning the same badge can appear temporarily and clears when SST is fully active.
Billing / credits	Confirm SST add-on is active under your Multifeeds subscription

Still stuck? Contact Multifeeds support with your shop domain, tracking subdomain, and a screenshot of the Domain + Server container widgets. ## Related articles - [Server-Side Tracking benefits](https://docs.woolytech.com/en/articles/218-server-side-tracking-benefits.md) - [Pixel and Tags setup (client)](https://docs.woolytech.com/en/articles/202-how-to-set-up-pixel-and-tags-with-the-multifeed-google-shopping-feed-app-2.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)