Setting up Tracking First in CNAME
CommandersAct recommends using a WAF proxy. CNAME tracking first is only an alternative if a WAF proxy cannot be configured.
Last updated
CommandersAct recommends using a WAF proxy. CNAME tracking first is only an alternative if a WAF proxy cannot be configured.
Last updated
When setting up tracking first by CNAME, it is essential to create the CAID cookie yourself (On-Premise CAID).
Please declare the chosen subdomain on your CAX platform: Administration > Domain Management > Add subdomain
Enter your full domain: XYZ.myshop.com
Select CNAME
Unless otherwise specified, let Let's Encrypt manage the certificate for your domain.
Retrieve your DNS configuration and send this information, along with the name of your chosen subdomain, to your IT department so that they can configure your CNAME.
Once configured, return to the CommandersAct CAX platform Administration > Domain Management Validate the chosen domain configuration and generate a certificate (blue buttons).
Activate "Container integration" for the newly created sub-domain.
Regenerate and deploy all your containers.
Tracking may need to be upgraded if it is managed outside the container (e.g. tracking views, clicks, data activation, OneTag outside commandersAct containers, etc.). If in doubt, contact support (support@commandersact.com).
Bravo, you're now trading in "First"!
