Skip to content

Commit b364219

Browse files
Update custom-domain.md
1 parent 12a66b7 commit b364219

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

src/connections/sources/custom-domain.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -60,10 +60,7 @@ To configure Custom Domain:
6060
## FAQ
6161

6262
### Can I set up multiple Custom Domains?
63-
For best practices, Segment recommends using only **one** custom domain per domain and only in **production** environments. It is not recommended to create multiple custom domains for the same source, and there are several reasons for this:
64-
65-
- For default settings of the Analytics.js library, our customers only use a single segment.io - so having a single domain would be adequate.
66-
- If you are working in the development or stage environment, we recommend that you disable any adblockers / user consent managers so that a custom domain will not be required in this case.
63+
For best practices, Segment recommends using only **one** subdomain (e.g., `mysubdomain.mydomain.com`) per domain. Multiple custom domains for the same source are not supported.
6764

6865
### What sources can I use with Custom Domain?
6966
Custom Domain was largely developed to support JavaScript sources. It helps with comprehensive collection of first-party data from your website when accessed over any platform (desktop, mobile, and more). You can use the subdomain for all other non-JavaScript sources as well, for consistency, but it will have no impact on data collection for those sources.

0 commit comments

Comments
 (0)