Skip to content

Best Practices for Custom Domains #7114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 10, 2024
Merged

Best Practices for Custom Domains #7114

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
12a66b7
Update custom-domain.md
joeynmq Oct 4, 2024
b364219
Update custom-domain.md
prigiattiperrut Oct 8, 2024
7f7461a
Update src/connections/sources/custom-domain.md
forstisabella Oct 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/connections/sources/custom-domain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,9 @@ To configure Custom Domain:

## FAQ

### Can I set up multiple Custom Domains?
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.

### What sources can I use with Custom Domain?
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.

Expand Down