Domain & Path Configuration
When you create a deployment, you record where it is used — the domain and path — and which environment it belongs to.
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 with the same domain, path, and environment, 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
What domain and path mean
A deployment is addressed by its ID alone: your backend renders and accepts against that ID, and Click never looks a deployment up from a domain or path. The domain and path you set are recorded on the deployment as metadata, for reporting and for telling deployments apart.
Two deployments of the same template cannot share the same domain, environment, path, and variant, so use the path to label where each one is used:
| Agreement | Domain | Path | Why |
|---|---|---|---|
| Terms of Service | app.co | /signup | Shown on the first step of sign-up |
| Privacy Policy | app.co | / | Applies across the whole app |
Multiple subdomains each need their own deployment, because the domain is part of the combination that must be unique:
| Subdomain | Path | Agreement |
|---|---|---|
app.yourcompany.com | / | Main app Terms |
admin.yourcompany.com | / | Admin portal Terms |
See the Terms of Service and Privacy Policy guides for full setup walkthroughs.
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.
Troubleshooting
Render or accept answers 404 CLICK_DEPLOYMENT_INACTIVE.
The deployment is not active, has ended, or has not started yet. Activate it in the Deployments list, or check its schedule.
Render or accept answers 404 CLICK_DEPLOYMENT_NOT_FOUND.
There is no deployment with that ID in your organization. Check that your backend uses the ID of the deployment in the environment it is running against.
Next: A/B Testing → or Scheduled Deployments →