# Share end-user consent across multiple domains

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

Didomi supports sharing end-user consent across multiple domains via a "group cookies" configuration that is stored and shared from a sub-domain that is delegated to Didomi. In this article, we will cover the following requirements to enable this configuration:

* [Prerequisites](#prerequisites)
* [Considerations](#considerations)
* [Customize consent notice content](#customize-consent-notice-content)
* [Enable group cookies for consent notice](#enable-group-cookies-for-consent-notice)

***

### Prerequisites

Before continuing with the configuration to share end-user consent across multiple domains, your organization will need a subdomain that you own which is then delegated to Didomi. This delegated domain is then used to store and share end-user consent across configured websites.

* [Delegate custom domain](/organization-and-account-settings/domains.md)

{% hint style="warning" %}
**Note**: End-user consents are only shared with domains that enable the group cookies configuration using the specified domain.
{% endhint %}

### Considerations

When implementing the methodology included in this article, be aware of the following changes and/or limitations to your implementation:

<table data-header-hidden><thead><tr><th width="220"></th><th></th></tr></thead><tbody><tr><td>Third-party cookie limitations</td><td>The methodology included in this article is dependent on browsers accepting third-party cookies. More browsers, by default, are blocking the use of third-party cookies. Therefore, end-users browsing with default settings on Safari, Firefox, or Chrome on iOS, or end-users who have blocked third-party cookies, will not be able to store third-party cookies in their browser. Didomi will fall back to using first-party cookies when third-party cookies are not available.</td></tr><tr><td>Switching from first-party cookies</td><td>If you organization is already using Didomi with first-party cookies (the default behavior) and decide to switch to third-party cookies, the consent notice will be displayed to all visitors again to recollect consent.</td></tr><tr><td>Load time</td><td>Sharing consent between domains increases the load time of the SDK as it involves additional asynchronous operations for reading and writing consent from a different domain.</td></tr></tbody></table>

### Customize consent notice content

When sharing end-user consent across domains your organization will need to inform its end-users via the consent notice. The following information should be included in the consent notice:

* Statement that end-user consent is shared across multiple websites
* List of websites and legal entities where end-user consent is shared

To edit the content of an existing consent notice, click **Consent notices** on the left-hand panel and select the **Edit** icon inline with a consent notice name.

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

Click the **Customization** tab and select to the **Content editor** sub-tab on the subsequent page.&#x20;

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

Navigate to the appropriate layer where your organization plans to inform the end-user about consent sharing and use the text field in the editor to include the information.

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

{% hint style="info" %}
If your organization uses different consent notices for the websites that will share the end-user consent, then you must include the text informing end-users of the sharing to each of those consent notices.
{% endhint %}

### Enable group cookies for consent notice

With the consent notice updated to inform end-users of consent being shred across domains, your organization will need to update the consent notice configuration to indicate that the consent notice is using group cookies and from where the end-user's consent is stored and shared.

Review the tabs below to learn more about how to enable group cookies from either the Didomi console or directly on page:

{% tabs %}
{% tab title="Didomi console" %}
From the consent notice, click **Advanced settings** in the upper right-hand corner and select **Custom JSON** from the drop-down menu.

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

Use the subsequent field to enable group cookies and to input the delegated domain that will be used to store and share the end-user consent cookie.

```json
{
    "cookies": {
      "group": {
        "enabled": true,
        "customDomain": "privacy.your-domain.com"
      }
    }
}
```

Click **Save** when finished.

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

Publish your consent notice.&#x20;

{% hint style="info" %}
If your organization uses different consent notices for the websites that will share the end-user consent, then you must enable group cookies for each of those consent notices.
{% endhint %}
{% endtab %}

{% tab title="On-page" %}
If your organization is managing consent notice configuration directly on-page for your websites, your organization should use the `window.didomiConfig` object to enable group cookies and input the delegated domain that will be used to store and share the end-user consent cookie.

```
<script type="text/javascript">
  window.didomiConfig = {
    cookies: {
      group: {
        enabled: true,
        customDomain: 'privacy.your-domain.com'
      }
    }
  };
</script>
```

{% hint style="info" %}
This configuration should be added to every website included in the group of domains that are sharing end-user consents.
{% endhint %}
{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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:

```
GET https://docs.didomi.io/consent-management-platform-cmp/introduction/share-end-user-consent-across-multiple-domains.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.