Skip to main content

Integration reference

Tracking domains

How a network puts its tracking links on a hostname of its own: choosing the name, proving it controls it, pointing traffic at the edge, the certificate, making it primary, what a lost visitor sees, and retiring one. Every step is taken in the panel, under Settings, Tracking domains.

Choose the hostname

Use a subdomain of a domain the network already controls, on a name that hosts nothing else, such as go.your-network.example. A bare domain works and is a poor choice: it cannot carry a CNAME, and it ties click traffic to the zone that carries the network’s mail and website. A hostname is refused when it is one of these.

Hostnames that are refused
Refused because
It is empty.
It is longer than 253 characters.
It has only one label, with no dot in it.
One of its labels is longer than 63 characters.
It contains an underscore, which a hostname cannot carry a certificate for.
A label starts or ends with a hyphen.
It contains characters a hostname cannot have.
It is an IP address, not a name.
Its last label is all digits.
It is a public suffix, a name anyone can register under, rather than a name one network controls.
It is under this platform’s own domains.

Prove the network controls it

The wizard shows a token. Publish it as a TXT record at _wowoffer.<hostname> in the zone’s DNS, then run the check. Proving control is what entitles the network to a publicly trusted certificate for the name, and it is the step that commits: nothing later takes it back except removing the domain.

The record, with the token the wizard shows
_wowoffer.go.your-network.example.  TXT  "<token>"

Two networks may both add the same name, because an unproved domain does nothing: it is not served, authorises no certificate and builds no link. The name is claimed by the first network to prove it. A domain that has proved ownership never loses it to one failed check.

Point traffic at the edge

Add an A record for the hostname pointing at this platform’s edge. The address is named by the check in the wizard, which reads it from what the edge really resolves to. Use an A record and not a CNAME: a CNAME to a tracking host is what browser blocklists resolve and match on. Keep the record DNS only, with no CDN proxy such as Cloudflare’s in front of it, because the edge must see the address that really sent the request. Until the name resolves to the edge, a click on it never arrives.

The certificate

The edge obtains a certificate for a proved hostname on demand, the first time it is asked for the name over HTTPS, and renews it the same way. The certificate check in the wizard makes that request, so it is a real measurement: it can take a minute the first time, and a check that keeps finding no certificate while the records are right is the platform’s problem to fix, not the network’s.

Make it primary

A network has one primary tracking domain, and every new partner link and integration snippet uses it. Links partners already hold keep working on whichever hostname they were built with. A domain whose certificate has never been proved cannot be made primary.

What a lost visitor sees

  • The network’s default page for lost visitors, set on the tracking domains list, is where a browser goes when a tracking link on its domains is broken or expired, unless the offer has its own fallback URL. With none set, a plain neutral page shows.
  • Each domain also chooses what its bare address shows: the neutral page, a redirect to an https:// address, or the network default.

Retiring a domain

  • Removing a proved domain retires it: it serves nothing and renews nothing, and links built with it stop working.
  • Removing a retired domain, or one that never proved ownership, deletes it, which frees the name for the network to add again.
  • The primary domain cannot be removed. Make another domain primary first.