Domains
Each ConsentForge property is associated with one or more domains. The domain determines where the embed script is authorised to run.
Viewing domains
Account → Domains shows all domains across all your properties.
Domain verification
ConsentForge verifies domain ownership before the banner can go live. Verification is automatic when:
- You add the embed script to your site
- ConsentForge detects a request from that domain using your embed token
If you haven't deployed the script yet, you can skip verification and come back later — the banner will simply not render until a request is received from the domain.
Adding additional domains to a property
A single property can serve multiple domains (e.g. www.example.com and example.com, or a staging environment):
Property → Settings → Domains → Add Domain
Wildcard domains
For multi-tenant SaaS or subdomain-per-client setups, you can authorise a wildcard:
*.example.com
This allows any subdomain of example.com to use the property's embed token.
Domain mismatch errors
If the embed script is called from a domain not listed on the property, the banner will not render and a warning is logged in Property → Activity Log.
Common causes:
- Staging/preview environments not added as authorised domains
- A CDN or proxy changing the origin domain
- Typo in the domain list
Removing a domain
Property → Settings → Domains → [Domain] → Remove
Removing a domain immediately prevents the banner from rendering on that domain.