Skip to content

Commit 761f1f4

Browse files
committed
reorganize sections [netlify-build]
1 parent fbd1b74 commit 761f1f4

File tree

1 file changed

+32
-28
lines changed

1 file changed

+32
-28
lines changed

src/connections/sources/custom-domain.md

Lines changed: 32 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,38 @@
11
---
22
title: Custom Domain
33
plan: custom-domain
4+
hidden: true
45
---
56

6-
Custom Domain is a fully-managed service that enables you to configure a first-party subdomain over HTTPS to track event requests through your domain (for example, cdp.mydomain.com), instead of tracking events through Segment's default domain (segment.com). Tracking events through your domain lets you reclaim some of the first-party data lost to end user ad-blockers and browser privacy controls that block Segment's default domain. With more complete first-party data comes a more complete view of your customer's behaviors. For more robust profiles, more accurate attribution, and, ultimately, greater ROAS.
7+
Custom Domain is a fully-managed service that enables you to configure a first-party subdomain over HTTPS to track event requests through your domain (for example, cdp.mydomain.com), instead of tracking events through Segment's default domain (segment.com). Tracking events through your domain lets you reclaim some of the first-party data lost to end user ad-blockers and browser privacy controls that block Segment's default domain. With more complete first-party data comes a more complete view of your customer's behaviors, and can lead to more robust profiles, more accurate attribution, and, ultimately, greater ROAS.
78

89
> success ""
910
> Segment recommends configuring Custom Domain alongside [Consent Management](/docs/privacy/consent-management/) to ensure you are respectful of your end users' consent preferences.
1011
12+
## Compare Segment's domain delegation solutions
13+
14+
Segment has two domain delegation solutions:
15+
- **Custom Domain**: Uses a DNS subdomain that you delegate to Segment
16+
- **[Custom Proxy](/docs/connections/sources/catalog/libraries/website/javascript/custom-proxy/)**: Uses a Canonical Name (CNAME) to map an alias name to a true or 'canonical' domain name. The CNAME record allows you to alias one domain name to another. You create a CNAME record to alias a subdomain that points to the Segment domain.
17+
18+
### How DNS subdomain delegation works
19+
DNS subdomain delegation is a process where the control of a specific subdomain is assigned to another DNS server, allowing that server to manage the DNS records for the subdomain. This delegation is useful for distributing the management of DNS records and enables specialized handling of subdomain traffic.
20+
21+
### How CNAME records work
22+
When a user tries to access the alias domain, the DNS resolver looks up the CNAME record, finds the canonical name, and resolves it to the IP address of the target. For example, you could alias your subdomain to point to the Segment domain. If a user accesses your site, they are redirected to the Segment domain, but their browser's address bar still shows the alias domain.
23+
24+
CNAME records provide flexibility and centralized management, making it easier to handle domain redirections and subdomain configurations.
25+
26+
### Benefits of Custom Domain over Custom Proxy
27+
- **Automatic SSL management**: Segment manages the SSL certificates for your subdomain, ensuring secure communication.
28+
- **Continuous monitoring**: Segment has security monitors in place, ensuring a quick responses to any issues.
29+
- **Easy setup**: Segment handles all DNS changes, so you have to complete minimal additional work.
30+
- **No maintenance**: Segment handles all ongoing infrastructure management.
31+
1132
## Supported sources
1233

1334
Custom Domain supports the following sources:
14-
- [Analytics.js][docs/connections/sources/catalog/libraries/website/javascript/]
35+
- [Analytics.js](docs/connections/sources/catalog/libraries/website/javascript/)
1536
- [Clojure](/docs/connections/sources/catalog/libraries/server/clojure/)
1637
- [Go](/docs/connections/sources/catalog/libraries/server/go/)
1738
- [Java](/docs/connections/sources/catalog/libraries/server/java/)
@@ -23,43 +44,24 @@ Custom Domain supports the following sources:
2344

2445
## Getting started
2546

26-
> info "Custom Domain available only to Business Tier customers"
47+
> info "Custom Domain is only available to Business Tier customers"
2748
> Customers not on the Business Tier but who have interest in Custom Domain should [contact Segment's sales team](https://segment.com/demo/){:target="_blank”} for assistance with upgrading to a Business Tier plan. Segment also offers an alternative DNS record service, [Custom Proxy](/docs/connections/sources/catalog/libraries/website/javascript/custom-proxy/), which uses a Canonical Name (CNAME) and only works with Analytics.js sources.
2849
50+
To configure Custom Domain:
2951
1. Select the subdomain you'd like Segment to use for event request tracking (for example, `cdp.domain.com`).
30-
2. Sign in to the Segment app, select your user avatar, and click **Contact Support**.
52+
2. Sign into the Segment app, select your user avatar, and click **Contact Support**.
3153
3. Create a support request with the following fields:
3254
- **Topic**: Select **Custom Domain**.
3355
- **Subject**: Enter a subject line for your support request.
34-
- **Domain Name**: Enter the subdomain that you created in step 1.
56+
- **Domain Name**: Enter the subdomain that Segment should use for event request tracking.
3557
- **Additional Domain Name**: If applicable, add an additional subdomain. This field is optional.
3658
- **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).
3759
- **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.
38-
- **Description**: Enter an optional description for your service request. If you are requesting Custom Domain for multiple workspaces, enter any additional workspaces slugs into this field.
60+
- **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.
3961
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.
40-
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.
62+
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.
4163
6. Update your Javascript snippet to reference the new subdomains or use the new Tracking API custom domain as your endpoint for server library sources.
4264

43-
## Compare Segment's DNS record solutions
44-
45-
Segment has two domain delegation solutions:
46-
- **Custom Domain**: Uses a DNS subdomain that you delegate to Segment
47-
- **Custom Proxy**: Uses a Canonical Name (CNAME) to map an alias name to a true or 'canonical' domain name. The CNAME record allows you to alias one domain name to another. You create a CNAME record to alias a subdomain that points to the Segment domain.
48-
49-
### How DNS subdomain delegation works
50-
DNS subdomain delegation is a process where the control of a specific subdomain is assigned to another DNS server, allowing that server to manage the DNS records for the subdomain. This delegation is useful for distributing the management of DNS records and enables specialized handling of subdomain traffic.
51-
52-
### How CNAME records work
53-
When a user tries to access the alias domain, the DNS resolver looks up the CNAME record, finds the canonical name, and resolves it to the IP address of the target, for example, the Segment domain. The user is redirected to the Segment domain, but the browser's address bar still shows the alias domain.
54-
55-
A CNAME record is a powerful tool in DNS management, allowing domain aliases to point to other domains seamlessly. It provides flexibility and centralized management, making it easier to handle domain redirections and subdomain configurations.
56-
57-
### Benefits of Custom Domain over Custom Proxy
58-
- **Automatic SSL management**: Segment manages the SSL certificates for your subdomain, ensuring secure communication.
59-
- **Continuous monitoring**: Segment has security monitors in place, ensuring a quick responses to any issues.
60-
- **Easy setup**: Segment handles all DNS changes, so you have to complete minimal additional work.
61-
- **No maintenance**: Segment handles all ongoing infrastructure management.
62-
6365
## FAQ
6466

6567
### What sources can I use with Custom Domain?
@@ -70,7 +72,9 @@ Once Custom Domain is enabled for your workspace, the Segment app generates a ne
7072
### Is this a fully-managed solution? What servers or infrastructure do I need to set up on my side for this proxy?
7173
Yes, Custom Domain is a fully-managed solution.
7274

73-
You must be able to delegate a DNS subdomain to Segment and add the name servers Segment provides. You must first decide on your subdomain and then delegate it to Segment. Segment then asks you to add a DNS NS record to your DNS with specific values to complete the DNS delegation. From there on, Segment fully manages the infrastructure for serving AJS and ingesting events data through the subdomain.
75+
You must be able to delegate a DNS subdomain to Segment and add the name servers Segment provides to your DNS.
76+
77+
First, decide on your subdomain and then delegate it to Segment. Segment then asks you to add a DNS NS record to your DNS with specific values to complete the DNS delegation. From there on, Segment fully manages the infrastructure for serving Analytics.js and ingesting events data through the subdomain.
7478

7579
### Can I change my Segment subdomain after the initial setup?
7680
Segment does not recommended that you change the subdomain after the initial setup. If you change the subdomain, Segment must revoke the older certificates for your subdomain and you will be required to redo the entire onboarding process, as several underlying components, like certificates, would need to be recreated and reassociated.

0 commit comments

Comments
 (0)