> For the complete documentation index, see [llms.txt](https://docs.avada.io/cookie-help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avada.io/cookie-help-center/settings/share-consent-across-sub-domains.md). # Share consent across sub-domains ### What is this feature? **Syncing Consent** helps keep customer consent consistent across sub-domains of the same store, so customers don’t need to respond to the cookie banner multiple times. ### Benefits for your store ✅ **Better customer experience**: *Customers see the consent banner only once, even when moving across sub-domains.* **✅ More accurate tracking & analytics:** *Consent is shared correctly across sub-domains, helping reduce data loss for marketing and analytics tools.* **✅ Easy setup, no technical work:** *Import store domains automatically or add them manually in just a few steps.* ### How it works * Consent can be shared only within the same root domain and its sub-domains * Consent cannot be shared across different root domains Example: * ✅ shop.example.com ↔ account.example.com * ❌ example.com ↔ example.net ### Setup Guide #### Step 1: Open Syncing Consent settings[](https://help.avada.app/cookie/how-to-integrate-with-meta-pixel/#step-1-setting-up-for-integration) 1. Go to **Settings** 2. Open the **Syncing consent tab**

*** #### Step 2: Import store domains (recommended)[](https://help.avada.app/cookie/how-to-integrate-with-meta-pixel/#step-1-setting-up-for-integration) 1. At the top right hand of the card, click **more action button** 2. Click **Import store domains** 3. The app will automatically imports all domains available in store' Shopify Domains 👉 This covers most storefront and account domains setted up in your stor3

*** #### Step 3: Add more store URLs (optional)[](https://help.avada.app/cookie/how-to-integrate-with-meta-pixel/#step-1-setting-up-for-integration) You can use this if your store uses domains outside Shopify Domains and want to sync consent with additional sub-domains **How to add a store URL** 1. Enter the store URL 2. Click **Add** **Notes** * The URL must be a valid storefront domain * Paths or parameters are no need for this

*** #### Step 4: Manage your domain list[](https://help.avada.app/cookie/how-to-integrate-with-meta-pixel/#step-1-setting-up-for-integration) In the table, you can: * ✏️ Edit a domain if needed * 🗑 Remove a domain if it’s no longer in use (you can delete bulk by choosing check box per item)

And that's it! You've successfully set up share your customer consent across all your store domains. If you have any questions or need further assistance, please don't hesitate to ask. We're here to help! --- # 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.avada.io/cookie-help-center/settings/share-consent-across-sub-domains.md?ask=&goal= ``` `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.