From c559ce0a7f2c3bcc823f9ac625f80797aa0ad6a0 Mon Sep 17 00:00:00 2001 From: prigiattiperrut <47340158+prigiattiperrut@users.noreply.github.com> Date: Wed, 30 Oct 2024 15:13:17 +0000 Subject: [PATCH 1/2] Update custom-domain.md --- src/connections/sources/custom-domain.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/sources/custom-domain.md b/src/connections/sources/custom-domain.md index a8a9f570b5..ac12349b96 100644 --- a/src/connections/sources/custom-domain.md +++ b/src/connections/sources/custom-domain.md @@ -50,7 +50,7 @@ To configure 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. - - **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). + - **Source names**: Select the sources you would like to use for Custom Domain. We recommend starting with a stage/dev source. For the 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. - **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. @@ -64,7 +64,7 @@ To configure Custom Domain: Segment recommends creating a different subdomain (for example, `mysubdomain.mydomain.com`) for each source. You cannot connect multiple custom domains to the same source. ### 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. +For the initial setup an [Analytics.js](docs/connections/sources/catalog/libraries/website/javascript/) source is required. 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. ### How can I configure non-JavaScript sources to use Custom Domain? From a82cd7c14cf05308ed9f8176c504b375ea629e67 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 14 Nov 2024 12:56:46 -0600 Subject: [PATCH 2/2] relative link cleanup --- src/connections/sources/custom-domain.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/sources/custom-domain.md b/src/connections/sources/custom-domain.md index ac12349b96..a340014c01 100644 --- a/src/connections/sources/custom-domain.md +++ b/src/connections/sources/custom-domain.md @@ -50,7 +50,7 @@ To configure 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. - - **Source names**: Select the sources you would like to use for Custom Domain. We recommend starting with a stage/dev source. For the 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). + - **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. - **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. @@ -64,7 +64,7 @@ To configure Custom Domain: Segment recommends creating a different subdomain (for example, `mysubdomain.mydomain.com`) for each source. You cannot connect multiple custom domains to the same source. ### What sources can I use with Custom Domain? -For the initial setup an [Analytics.js](docs/connections/sources/catalog/libraries/website/javascript/) source is required. 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. +For initial setup, Segment requires an [Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/) source. 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. ### How can I configure non-JavaScript sources to use Custom Domain?