> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.pandectes.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Cookie Domain Setup and Cross-Domain Consent (Legacy Version)

|| This article applies to the Legacy** Banner** (v4). If you are on the New Banner, please refer to the [Cookie Domain Setup and Cross-Domain Consent (New Version)](https://help.pandectes.io/en/article/cookie-domain-setup-and-cross-domain-consent-new-version-5trk5b/) article.

When your store runs on both a **main domain** and one or more **subdomains**, you may encounter issues where the cookie banner reappears even if the visitor has already given consent.

This happens because by default, cookies are stored on the specific domain or subdomain where the visitor first interacts with the banner. To ensure a smooth user experience and consistent compliance, you can configure the **cookie domain option** to cover all subdomains under the same root domain.

### Why Cookie Domain Matters

Let’s say your site runs on:

* Main domain: `www.somesite.com`
* Subdomain: `marketing.somesite.com`

If a visitor lands first on `marketing.somesite.com`, the cookie consent is saved there. But when the same visitor navigates to `www.somesite.com`, the banner appears again, because the cookie is not shared across both.

By setting the **cookie domain** to the root domain `somesite.com`, the consent cookie will be valid for both the main domain and all subdomains. This ensures:

* **Cross-domain consent**: Visitors only need to give consent once, and it applies everywhere within your domain and its subdomains.
* **Better user experience**: No repeated banners across different parts of your site.
* **Consistent compliance**: Consent is tracked uniformly across all your store’s properties.

### How to Configure Cookie Domain

1. Go to **Settings > Banner**.
2. Locate the **Cookie Domain** option.
3. Set the domain to your **root domain** (e.g., `somesite.com`).


![](https://storage.crisp.chat/users/helpdesk/website/1a5af239e847cf00/after1_jsv3do.png =1000x405)

### Example Scenario

* If traffic first comes to `marketing.somesite.com`, consent is saved on `somesite.com`.
* When the visitor later navigates to `www.somesite.com`, the banner does not reopen.
* Both main and subdomains share the same consent status.

### Benefits of Cross-Domain Consent

* **Seamless browsing:** Users won’t be annoyed by repeated consent prompts.
* **Improved trust:** A consistent consent experience shows professionalism and respect for user privacy.
* **Technical efficiency:** Your consent logs remain centralized and easier to manage.

### With vs. Without Cookie Domain


![](https://storage.crisp.chat/users/helpdesk/website/-/1/a/5/a/1a5af239e847cf00/image_13lqz6y.png =500x623)

![](https://storage.crisp.chat/users/helpdesk/website/-/1/a/5/a/1a5af239e847cf00/image_i75f1o.png =500x373)