Domain & Path Configuration
When you create a deployment, you tell Click exactly where on your website to show the agreement — which domain it belongs to, and which page (or pages) it should appear on.
Only published templates can be deployed. Drafts are not eligible.
Creating a deployment
- Go to Click → Deployments → + New Deployment.
- Fill in the required fields:
| Field | What to enter |
|---|---|
| Template | The published template you want to deploy |
| Domain | Your website address, without https:// — e.g. app.yourcompany.com |
| Path | The page path — e.g. /signup. Use / to cover your entire site. |
| Environment | Development, Staging, or Production |
- Click Create Deployment. The deployment is saved but not yet live.
Screenshot: click-create-deployment-form, screenshot of the New Deployment modal with Template, Domain, Path, and Environment fields labelled
Activating a deployment
After creating, you activate the deployment to make it live:
- From the Deployments list, toggle the Active switch on the deployment row.
- Or open the deployment and toggle it from the detail view.
If another deployment is already active on the same page, Click automatically deactivates it when you activate the new one — no manual cleanup needed.
Screenshot: click-deployment-active-toggle, screenshot of the Deployments list with the Active toggle highlighted in on/off states for two deployments
How path matching works
The path you set is matched exactly — it does not cover sub-pages unless you use /.
| Domain | Path set | Pages covered | Pages not covered |
|---|---|---|---|
app.co | / | Every page on app.co | Subdomains like sub.app.co |
app.co | /signup | app.co/signup only | app.co/signup/confirm |
app.co | /checkout | app.co/checkout only | app.co/checkout/complete |
If your Terms of Service or Privacy Policy applies everywhere, set the path to /. For step-specific agreements — like a checkout confirmation — use the exact page path.
Common routing scenarios
Multi-step sign-up flow — Terms on step one, Privacy Policy site-wide (see the Terms of Service and Privacy Policy guides for full setup walkthroughs):
| Agreement | Domain | Path | Why |
|---|---|---|---|
| Terms of Service | app.co | /signup | Only the first step requires acceptance |
| Privacy Policy | app.co | / | Applies across the whole app |
Multiple subdomains — each needs its own deployment:
| Subdomain | Path | Agreement |
|---|---|---|
app.yourcompany.com | / | Main app Terms |
admin.yourcompany.com | / | Admin portal Terms |
docs.yourcompany.com | / | Docs acknowledgment |
Cookie consent banner — deploy to / so it appears on every page. Users who have already accepted are automatically skipped and not shown the banner again. See the Cookie Consent guide for the full setup walkthrough.
Tracking views and acceptances
Each deployment automatically tracks views, acceptances, and declines — no setup required.
Screenshot: click-deployment-stats-row, screenshot of a deployment row in the list showing the Views, Acceptances, and Declines counters populated with real numbers
For a breakdown of what each metric means and how to export data, see Metrics and Reporting.
Restricting which domains can show a template
You can limit which domains are allowed to render a template by setting Allowed Domains in Click Settings. Requests from any other domain will be blocked, even if a deployment is active.
Screenshot: click-allowed-domains-settings, screenshot of the Security section in Click Settings showing the Allowed Domains field with example domains listed
Troubleshooting
The wrong agreement is showing on my page.
If multiple deployments target overlapping paths (e.g., one for / and one for /signup), the one with the higher Priority value wins. Go to Click → Deployments, compare the priority values for overlapping deployments, and adjust as needed.
The deployment is active but no sessions are being created.
Check three things: (1) the domain must match exactly — www.yourcompany.com and yourcompany.com are treated as different; (2) if Allowed Domains is configured in Settings, verify your domain is listed; (3) the path must match exactly — a deployment on /signup won't show on /signup/step-2.
Next: A/B Testing → or Scheduled Deployments →