The measurement address
What a measurement address is, the four steps it goes through before it works, and what to do when it gets stuck.
The measurement address is where your website sends its measurements. It is a
subdomain of your own domain — t.yourdomain.com — and the fact that it sits
under your own domain is the whole point of server-side tagging.
One measurement server can carry more than one measurement address. You need that as soon as you want several country sites under the same measurement.
The four steps
A new address goes through four steps. The address screen shows you under Progress where it is.
1. Address added
Known to Tagyard, not in use yet. This is where you get the CNAME record to
put at your DNS provider.
2. DNS points here
Tagyard checks every thirty seconds whether the record is right. As soon as the address points at us, this step flips. You do not have to refresh anything or submit it again.
3. Traffic is being routed
The route is set up without interruption: existing addresses on the same measurement server keep working while this one is added.
4. Security active
The certificate is only requested once your DNS actually points at Tagyard, and it is there after the first visit. That is deliberate: requesting a certificate for an address that points nowhere fails, and counts towards the issuer’s quota. See Getting started for the order from end to end.
When it stays on step 2
Two things go wrong here almost every time.
The proxy is on. At Cloudflare the record must be on DNS only, not on Proxied. With the proxy on, your traffic never reaches your measurement server and the certificate cannot be requested.
The record is on the apex domain. It belongs on the subdomain you chose, not
on @.
Beyond that, DNS always needs time to propagate. A record you have just set is not visible everywhere immediately.
Removing an address
You can do that from the address screen. Only remove an address that nothing sends to any more: once it is gone, traffic still arriving there gets no answer. Your traffic history stays — it hangs off the measurement server, not off the address.