Setting up Tracking First in A-Record
Commanders Act recommends using a WAF proxy. A-Record's tracking first is only an alternative if a WAF proxy cannot be configured.
Last updated
Commanders Act recommends using a WAF proxy. A-Record's tracking first is only an alternative if a WAF proxy cannot be configured.
Last updated
When setting up tracking first by A-Record, it is essential that you 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 A-Record
Unless otherwise specified, let Let's Encrypt manage the certificate for your domain.
Retrieve your DNS configuration and send this information, together with the name of your chosen sub-domain, to your IT department so that they can configure your A-Record.
Once configured, return to the Commanders Act 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"!
