> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/organization-and-account-settings/domains/domain-usage.md).

# Domain usage

{% hint style="success" %}
**Access Type:** Domains - Editor
{% endhint %}

For every custom domain  added to the Didomi platform, your organization must specify how the domain will be used. In this article we will provide an overview of the the usage that can be assigned to the custom domain.

* [Serve a hosted page](#serve-a-hosted-page)
* [Serve the Didomi SDK](#serve-the-didomi-sdk)

<figure><img src="/files/G4gDoSyGg8I9PLybgKwa" alt="" width="563"><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Serve a hosted page" %}
For custom domains whose usage is to serve a hosted, the custom domain will be used to load a webpage (e.g. preference center). Some characteristics of the serve a hosted page usage designation is:

* Can only be linked to one widget
* Custom domain must be detached from its widget before it can be deleted
* Can only be used by one widget at a time
* The custom domain's URL is used by the end-user to access the widget
  {% endtab %}

{% tab title="Serve the Didomi SDK" %}
For custom domains whose usage is to serve the Didomi SDK, the custom domain will be used to load the Didomi SDK. Some characteristics of the serve Didomi SDK usage designation is:

* Not linked to any widget or notice
* Can be used for consent notices, preferences widgets, and privacy request widgets
* A custom domain can load several products at once
* Custom domain is included in the implementation snippet used to load and display the widget/notice
  {% endtab %}
  {% endtabs %}

For your convenience, Didomi has compiled the differences between custom domain usage in the table below:

<table><thead><tr><th></th><th data-type="checkbox">Serve a hosted page</th><th data-type="checkbox">Serve Didomi SDK</th></tr></thead><tbody><tr><td>Loads Didomi SDK (CMP, PMP, Privacy requests)</td><td>false</td><td>true</td></tr><tr><td>Loads preference center or privacy request UI</td><td>true</td><td>false</td></tr><tr><td>NS record validation required</td><td>true</td><td>true</td></tr><tr><td>Reused across products</td><td>false</td><td>true</td></tr><tr><td>Tied to a widget</td><td>true</td><td>false</td></tr><tr><td>Allow bots to crawl across domain</td><td>true</td><td>true</td></tr><tr><td>Detach widget before deletion</td><td>true</td><td>false</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.didomi.io/organization-and-account-settings/domains/domain-usage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.