Authorized domains allow clients to explicitly define the only domains allowed to send traffic to their content. When set, traffic will only be accepted from these domains—everything else will be blocked.
We only recommend using this feature if your are going to use Unique article id. Or you experience a lot of spam sites using your content and code.
Using in combination with CMS ID
We strongly recommend enabling Authorized Domains if you are using the cms_id feature.
The cms_id enables content ownership identification across domains. Without restricted domains in place, unauthorized sites could reuse your cms_id, potentially inflating analytics or misusing your content attribution. By restricting traffic to known domains, you ensure that only approved sources can represent your content and identity.
How It Works
- If no restricted domains are set, then traffic is accepted from everywhere (default behavior).
- If one or more restricted domains are set, then only traffic from those domains will be accepted. All others will be blocked.
Where to Set It
You can configure the restricted domains via the Tracking Rules panel in CompassApp.
Changes take effect slightly immediately and apply to all incoming traffic.
What Happens to Blocked Traffic?
When a domain is not in the restricted list:
- Its traffic is ignored and lost forever.
- It does not count toward analytics, recommendations, or reports.
Who Can Configure This?
Only users with Admin or Tracking rules permissions can modify the restricted domains list.
Things to Keep in Mind
- No entries = traffic from all domains is allowed.
- At least one entry = only those listed domains are allowed.
- Top domain feature included. For example:
example.comincludessub.example.com