Skip to content
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

Added a clarification on Additional Domains #7419

Merged
merged 2 commits into from
Jan 31, 2025
Merged

Added a clarification on Additional Domains #7419

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8383b6d
Update custom-domain.md
prigiattiperrut Jan 31, 2025
0e4d186
Update src/connections/sources/custom-domain.md
stayseesong Jan 31, 2025
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
2 changes: 1 addition & 1 deletion src/connections/sources/custom-domain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ To configure Custom Domain:
- **Topic**: Select **Custom Domain**.
- **Subject**: Enter a subject line for your support request.
- **Domain Name**: Enter the subdomain that Segment should use for event request tracking.
- **Additional Domain Name**: If applicable, add an additional subdomain. This field is optional.
- **Additional Domain Name**: (*Optional*) If applicable, you can add an additional subdomain. You can have multiple domains within the same workspace; however, each source can only be associated with one domain. A single domain can be associated with multiple sources.
- **Source names**: Select the sources you would like to use for Custom Domain. Segment recommends starting with a stage or dev source. For initial setup, an [Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/) source is required. For a list of all sources that support Custom Domain, see [Supported sources](#supported-sources).
- **Is the domain name enabled for Content Policy**: Select either Yes or No. You are not required to create a Content Policy prior to requesting Custom Domain. If you've enabled a Content Security Policy (CSP), you must add the new subdomains provided by Segment to your CSP once you've enabled the Custom Domain feature. This ensures that the CSP does not block the subdomains when you load Segment.

Expand Down
Loading