Skip to content

Added a clarification around content policy #7149

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
forstisabella merged 2 commits into from
Oct 16, 2024
Merged

Added a clarification around content policy #7149

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f45cb43
Update custom-domain.md
prigiattiperrut Oct 16, 2024
a907f7e
Update src/connections/sources/custom-domain.md
forstisabella Oct 16, 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: 2 additions & 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 @@ -51,7 +51,8 @@ To configure Custom Domain:
- **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.
- **Source names**: Select the sources you would like to use for Custom Domain. 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.
- **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 have a Content Security Policy (CSP) enabled, you must add the new subdomains provided by Segment to your CSP once the Custom Domain feature is enabled. This ensures that the subdomains are not blocked by your CSP when loading Segment.

- **Description**: Enter an optional description for your service request. If you are requesting Custom Domain for multiple workspaces, enter any additional workspace slugs and source names into this field.
4. Segment provides you with a list of nameservers you should add to your DNS. Once you receive the nameservers from Segment, update your DNS.
5. After you've updated your DNS, Segment verifies that you've made all required updates and then provides you with two custom domains, one for the Tracking API and a second for your CDN.
Expand Down