Analytics and Tracking

First-Party Endpoint

Also called First-party tagging domain, custom tagging domain

A subdomain of your own site that receives tagging requests before passing the data on to the vendor.

Quick facts: First-Party Endpoint

Category
Analytics and Tracking
Also called
First-party tagging domain, custom tagging domain
Level
Advanced
Affects
Cookie lifetime, data loss to blockers, tracking accuracy
Where to see it
DNS records, server-side Google Tag Manager container settings, browser network tab
In this article4
  1. How a first-party endpoint works
  2. Why a first-party endpoint matters
  3. Common mistakes with first-party endpoints
  4. How to act on it

How a first-party endpoint works

When a tag on your site sends data to a vendor, the browser normally makes that request to the vendor’s own domain. A first-party endpoint changes the address on the envelope. You create a subdomain of your own site, point it through DNS at a tagging server, and the browser now talks to something that shares your website’s root domain rather than a stranger’s.

The data still reaches the vendor in the end. Nothing about the destination changes, only the first hop. In a server-side Google Tag Manager setup, the endpoint is the public address of the tagging server container, and browser requests land there before anything is forwarded onward.

Why a first-party endpoint matters

Browsers treat a request to your own domain differently from a request to a third party. Cookies written in a first-party context are given longer lives, blockers that work from lists of known vendor domains have nothing familiar to match, and network filtering in offices or on mobile networks is far less likely to interfere. The practical result is that more of your measurement arrives, and it keeps arriving for longer after a visitor’s first session.

It also puts you in charge of a piece of plumbing you were previously renting. You decide what is forwarded, to whom, and what is stripped out on the way. That is a much stronger position to write a privacy policy from than the tag sends whatever the tag sends.

Common mistakes with first-party endpoints

The worst one is treating it as a way around consent. Serving a tag from your own subdomain does not change what the data is or who ultimately receives it, so if permission was required before, it is still required. Regulators look at the purpose of the processing, not at the hostname on the request.

The second is the certificate. The subdomain needs a valid HTTPS certificate of its own, and when one lapses the browser drops every request silently — measurement stops with no visible error on the page. The third is choosing a hostname that does not actually share the site’s root domain. Point tags at an unrelated address and the browser goes straight back to treating it as a third party, which defeats the whole exercise.

How to act on it

If your measurement already feels thin — conversions counted in the ad platform that never appear in analytics, figures that collapse for Safari visitors — then a first-party endpoint is worth costing out. It needs a tagging server running somewhere, so there is a hosting bill and someone has to keep it patched. It is not a switch you flip in an interface.

Write down what you intend to send through it and why, before you build anything. Then set up the subdomain, get the certificate and DNS right, and compare a stretch of data before and after against something you can count independently, such as real enquiries in your inbox. If the gap between the two narrows, keep it. If it does not, the cause was elsewhere and browser tracking restrictions were never your problem.

Do and do not

Do

  • Use a subdomain of the same root domain as your site
  • Keep the HTTPS certificate renewing automatically
  • Decide what the server forwards before you build it

Do not

  • Treat it as a substitute for asking consent
  • Point tags at an unrelated hostname you happen to own
  • Launch it without someone owning uptime and updates

Questions people ask about this

Do I still need consent if tags run on my own subdomain?

Yes. Consent rules are about what data is collected, why, and who ends up with it — not about which hostname the browser contacts. Moving a tag onto your own subdomain changes the technical route and nothing else. Keep your consent banner and your privacy policy accurate, and describe the tagging server as a processor you control.

Does a first-party endpoint need its own server?

It needs something running behind the subdomain to receive the requests, usually a tagging server hosted in the cloud. That brings a monthly hosting cost and someone responsible for updates and uptime. If nobody in the business will own that, a first-party endpoint becomes a silent point of failure rather than an improvement.

Will it recover all my missing conversions?

No. It reduces losses caused by browser restrictions and blockers, so more data survives, but it cannot recover a conversion that was never sent, a form that failed, or a visitor who refused consent. Treat it as one repair among several and measure the change against a source you can verify by hand.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.