Proxy management
Would you like to set up an alternative as a tracking solution for your events first party ?
You can also set up proxy mode on site as a feature to orchestrate communication between your website and the Commanders Act platform. A proxy is a kind of intermediary that routes information between two points, in this case your website and Commanders Act.
General principle
When a site uses a custom tracking domain (e.g. waf.mysite.com
) configured as a reverse proxy to Commanders Act, requests sent to this domain pass through the browser as if they were internal to the site. This allows:
The placement of a first-party cookie (linked to the site domain).
Retrieve this cookie in requests sent to Commanders Act via the proxy.

Steps for transmitting the cookie
1. Creation of the cookie on the browser side
The Commanders Act tag (via the container) places a cookie on the domain waf.mysite.com. This cookie generally contains a user or session ID.
2. Request sent via the proxy
The browser sends a request to waf.mysite.com
, which is actually a proxy to ca-trk-proxy.commander1.com
. The cookie is automatically included in the HTTP header of the request (Cookie:
).
3. Cloudflare or other proxy
The proxy must not modify the Host
header or delete cookies. It transmits the request as is to the Commanders Act infrastructure.
4. Reception on the Commanders Act side
The Commanders Act server reads the cookie in the HTTP header. It can then associate the collected data with the user identified by this cookie.
Requirements
For the transmission to work correctly:
The tracking domain must be 1st party (same domain or subdomain as the site).
The proxy must preserve the HTTP headers, in particular
Cookie
andHost
.The container must be configured to use this domain in Domain Management.
Discover the On-Premise Proxy solution
Discover the WAF Proxy solution
Last updated