Google AdsNewStep 1 of 5 on the chain

Google tag gateway for advertisers

Serving Google's tag scripts and measurement requests through your own domain and first-party infrastructure, configured through a CDN, load balancer, web server or server-side tagging setup, rather than loading them from Google's domains.

Why it matters

Measurement written from your own domain survives conditions that third-party requests do not, which matters more every year as browsers tighten.

What goes wrong

It improves durability broadly rather than fixing one specific failure, which makes it the wrong thing to do first. Basic click identifier capture, CRM mapping and enhanced conversions are all cheaper, more targeted and more likely to be the actual problem. This is worth doing once those are solid.

How to check it on your own account

View the page source, or the network tab in the browser's developer tools, and read the hostname the Google tag loads from. Through the gateway it is a path on your own domain; without it, it is one of Google's.

Next to this

Where this comes up

How it applies in your trade

The same method, worked through for each kind of business: what a lead is worth, what is known on arrival and what to prepare.

The rest of this step

Measure this on your own data

The diagnostic reads a CRM export in your browser and reports your volume, your match rate and the spread between your leads against the thresholds in this glossary. Nothing is uploaded and no account is needed.

See what your own leads are worth

Read your closed deals and find out whether your lead values actually vary, and by how much. Nothing is stored, and your file is read in your browser.

Try it on a sample dataset