Manage your Gateway
Configure your Gateway from the Administration interface
You create, configure and monitor your first-party Gateways in Administration > Gateway, with no code. The only technical step is connecting your CDN (see Route traffic).
Get started
If the site has no Gateway yet, you see an introduction screen. Choose one of two options:
Configure my first Gateway — launches the 5-step setup wizard below.
Load a gateway from another site — reuses an existing Gateway from your account as a starting point.
💡 Tip: Click Save and exit at any time. Your progress is saved, and the Gateway stays inactive until setup is complete.
Set up a Gateway in 5 steps
Step 1 · Scope
Select what to route through your domain. You can add use cases later without recreating the Gateway.
Google Tag Gateway (default)
Loads Google Tag and sends Google measurements from a first-party path.
Commanders Act container (default)
Loads your Commanders Act web container from your own domain.
Server-side tracking
Sends your events to your server-side destinations via your domain.
Commanders Act collections
Routes CMP hits and other Commanders Act collections through your domain.
Third-party libraries
Hosts partner libraries on your domain with obfuscated file names.
Then choose who handles the CDN: I have the access, or I will hand this off to my technical team (default), which prepares ready-to-share instructions for IT.
Step 2 · Domain and path
Fill in the information needed to reserve your first-party path:
Field
Notes
Internal Gateway name
For your own reference.
First-party path
Auto-generated, can be regenerated. The unique URL on your domain that carries Gateway traffic.
Domain
The website the Gateway runs on.
Google tag ID
Only if you selected Google Tag Gateway.
CDN provider / load balancer
Cloudflare Free, Cloudflare Enterprise, Akamai (beta), Fastly (beta), other CDN, or "I don't know".
Cookies to exclude (optional)
Pre-filled with the 2 cookies excluded by the standard Worker code.
⚠️ Avoid tracking, analytics, metrics, tag, google or ads in the path — blockers detect them more easily. Your technical team must also confirm the path isn't already used on your site.
Step 3 · CDN connection
The platform generates the exact configuration (domain, route, infrastructure) and a step-by-step guide for your CDN. Follow it yourself, or copy the shareable link for your IT team. CDN-specific details: Route traffic.
Step 4 · Verification
Two checks run automatically: path validation and geolocation forwarding. Both must return "ok" before you can continue. If one fails, fix your CDN configuration and click Re-run verification.
Step 5 · Activation
Your first-party entry point is live. Complete the action card for each use case (see below), then click Finish. The right-hand panel recaps your configuration and links to the help center.
Finish activating each use case
Use case
What to do
Google Tag Gateway
Replace your Google tag URLs (gtag.js, GTM) with your first-party path, in every container that loads them.
Commanders Act container
Replace the container loading URL with the new first-party URL.
Server-side tracking / Commanders Act collections
No tag changes. Regenerate and deploy your container(s).
Third-party libraries
Declare each JS file (e.g. Meta Pixel) in First-Party Tag Hosting, then use the generated obfuscated file name in the tag.
You can add or change use cases later from the Gateway's configuration.
Manage your Gateways
Finish activating each use case
Use case
What to do
Google Tag Gateway
Replace your Google tag URLs (gtag.js, GTM) with your first-party path, in every container that loads them.
Commanders Act container
Replace the container loading URL with the new first-party URL.
Server-side tracking / Commanders Act collections
No tag changes. Regenerate and deploy your container(s).
Third-party libraries
Declare each JS file (e.g. Meta Pixel) in First-Party Tag Hosting, then use the generated obfuscated file name in the tag.
You can add or change use cases later from the Gateway's configuration.
Manage your Gateways
Once a Gateway exists, Administration > Gateway becomes your dashboard. From there you can:
Search by name or filter by status (Active, Suspended…).
Add a gateway or Load a gateway from another site.
Review the Gateway table: name, domain, first-party path, Google ID, status and number of declared libraries. Use the row icons to edit or delete (deletion asks for confirmation).
Unload configurations listed under Loaded from other sites when you no longer need them.
Open Manage libraries (below the table) to go to First-Party Tag Hosting.
First-Party Tag Hosting
In Administration > First-Party Tag Hosting, declare the third-party JS libraries to serve through your Gateway(s).
Click Add JS URL and enter the library's original third-party URL.
Find the generated hosted links in the table — one first-party URL per Gateway where the library is active. The table also shows status and last deployment date; use the row icons to edit or delete.
Use the first-party URL in your tag instead of the original one.
Last updated
Was this helpful?