---
title: "What is first party domain (for server side tracking)"
url: https://docs.woolytech.com/en/articles/239-what-is-first-party-domain-for-server-side-tracking
collection: "Tracking"
updated: 2026-08-13
language: en
---

# What is first party domain (for server side tracking)

When you enable server-side tracking in Multifeeds, you can send analytics and ad events through a **tagging server** on your own hostname instead of a shared WoolyTech domain.

  

Using a **first-party subdomain you control** — for example `track.yourstore.com`  — is the recommended option for production stores. This article explains why.

  

**Already know you want first-party?** See [How to set up Server-Side Tracking in Multifeeds](https://docs.woolytech.com/article/238-server-side-tracking) for DNS, region, and GA4 configuration steps.

  

* * *

  

## What is a first-party tracking domain?

A first-party tracking domain is a **subdomain of your store's own domain** that points (via DNS) to your Multifeeds tagging server.

  

<table style="min-width: 25px;"><colgroup><col style="min-width: 25px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p>ApproachExample hostnameWho owns the domain?</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>First-party (recommended)</strong></p></td><td colspan="1" rowspan="1"><p><code>track.yourstore.com</code></p></td><td colspan="1" rowspan="1"><p>You — subdomain of your store</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>WoolyTech managed</strong></p></td><td colspan="1" rowspan="1"><p><code>sgtm-yourstore.woolytrack.org</code></p></td><td colspan="1" rowspan="1"><p>WoolyTech — quick for testing</p></td></tr></tbody></table>

With first-party setup, browsers and ad platforms see tracking requests going to **your** brand domain, not a third-party vendor hostname.

  

* * *

  

## Key benefits

### 1\. Longer-lived, more reliable cookies

Safari Intelligent Tracking Prevention (ITP), Firefox, and other browsers heavily restrict **third-party** cookies and cross-site storage.

  

When your tagging endpoints use **your own subdomain**, cookies and identifiers are treated as **first-party** to your site. That typically means:

  

-   Better persistence for analytics and attribution windows
    
-   Fewer dropped sessions between page views and checkout
    
-   More stable identity for returning customers
    

  

This is one of the main reasons Google Tag Manager server-side tagging documentation recommends a custom subdomain on your root domain.

  

### 2\. Better data capture (fewer blocked requests)

Ad blockers and privacy tools often target known third-party analytics and tag-manager domains. A hostname like `sgtm-*.woolytrack.org`  may be categorized differently than `track.yourstore.com` .

  

Routing events through your first-party domain can recover conversions and funnel steps that would otherwise never reach GA4, Meta, or Google Ads — especially on mobile and privacy-focused browsers.

  

### 3\. Stronger trust and brand consistency

Customers and auditors see requests to **your** domain, not an unfamiliar third-party host. That supports:

  

-   A more professional, cohesive technical footprint
    
-   Clearer data-governance story for GDPR/CCPA reviews
    
-   Alignment with how enterprise teams expect marketing data to flow
    

  

### 4\. First-party tracking loader (when SST is fully active)

After your custom domain is verified and the tagging server is live, Multifeeds can serve your **pixel loader script** from your own domain (for example `https://track.yourstore.com/0/yourstore.js` ) instead of only from shared loader hosts.

  

That keeps the full tracking path — loader, GTM, and server container — on first-party infrastructure, which reinforces cookie and request reliability.

  

### 5\. You choose server region

First-party domains support selecting a **server region** close to your customers (for example EU or US-east at launch). WoolyTech managed domains are provisioned in **EU only** and are best suited for evaluation.

  

* * *

  

## First-party vs WoolyTech managed — when to use which

<table style="min-width: 25px;"><colgroup><col style="min-width: 25px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><br>First-party domainWoolyTech managed domain</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Best for</strong></p></td><td colspan="1" rowspan="1"><p>Live stores, paid ads, production analytics</p></td><td colspan="1" rowspan="1"><p>Quick tests, internal demos</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>DNS setup</strong></p></td><td colspan="1" rowspan="1"><p>Required (CNAME)</p></td><td colspan="1" rowspan="1"><p>None</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Cookie / blocker resilience</strong></p></td><td colspan="1" rowspan="1"><p>Highest</p></td><td colspan="1" rowspan="1"><p>Lower</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Server region</strong></p></td><td colspan="1" rowspan="1"><p>Your choice (where available)</p></td><td colspan="1" rowspan="1"><p>EU only</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Brand appearance</strong></p></td><td colspan="1" rowspan="1"><p>Your subdomain</p></td><td colspan="1" rowspan="1"><p><code>*.woolytrack.org</code></p></td></tr></tbody></table>

**Recommendation:** Use WoolyTech managed to explore server-side tracking, then move to a first-party subdomain before relying on SST for bidding, reporting, or compliance-sensitive workflows.

  

* * *

  

## What first-party does not replace

A first-party domain improves **how** events are delivered; it does not remove the need for:

  

-   Completing [client pixel setup](https://docs.woolytech.com/article/238-server-side-tracking) (steps 1–2)
    
-   Consent / privacy configuration for your markets
    
-   Correct GA4 Measurement ID and server-side tracker setup
    

  

It also does not eliminate DNS work — you still add a CNAME at your DNS provider. That is covered in the setup guide, not here.

  

* * *

  

## Related articles

-   [How to set up Server-Side Tracking in Multifeeds](https://docs.woolytech.com/article/238-server-side-tracking) — DNS checklist, provisioning, widgets
    
-   [The Power of Server-Side Tracking](https://docs.woolytech.com/article/218-server-side-tracking-benefits) — why SST matters overall