Description
...
A tracking domain needs to be configured in DMP if you want to keep using our pixels. If you don't do this properly the cookies will be marked as third-party and be blocked by browsers.
If for example you have the website "example.com" and you want to implement our pixel there, then you need to create tracking domain "px.example.com" for example.
This can be done by creating a CNAME record on your DNS server to "go-direct.flx1.com". After configuring the CNAME you can configure the tracking domain in DMP.
If you don't configure tracking domains the tracking domain "go.flx1.com. When a custom " will be used. After configuring the tracking domain is configured, you can select through which domain the pixel data will be handled.it when creating or updating a tracking pixel.
Please note that cookies are separated by tracking domain. So if you change the tracking domain for existing users or create a new one they won't share the cookies.
This will result in all users getting new DMP UUID's.
https://blog.chromium.org/2020/01/building-more-private-web-path-towards.html
https://blog.mozilla.org/security/2021/02/23/total-cookie-protection/
Creating a tracking domain
...
When you have at least one custom tracking domain available, you will be able to select the tracking domain when creating new or updating tracking pixels.
The default tracking domain is always selected and will be used when no other tracking domain is available.
HTTPS
When the DNS-record is configured properly we will also be able to generate a SSL-certificate for the subdomain. This allows us to drop secure first-party cookies.
The certificates are requested from CA Let's Encrypt for the subdomain.
After creating the tracking domain in DMP the certificate will be generated and properly served by our servers, the process of generating and serving the new pixels can take a day.