|
| 1 | +--- |
| 2 | +title: Segment-Managed Custom Domain |
| 3 | +plan: custom-domain |
| 4 | +hidden: true |
| 5 | +--- |
| 6 | + |
| 7 | +Custom Domain is a fully-managed service that enables you to configure a first-party subdomain over HTTPS. You can then track event requests through your own domain (for example, `cdp.mydomain.com`), instead of the default (`segment.com`). Tracking events through your own domain allows for more secure and complete first-party data collection by reclaiming first-party data lost to browser controls. With a more complete view of your customer behaviors, you can build more robust profiles for greater attribution and ROAS. |
| 8 | + |
| 9 | + |
| 10 | + |
| 11 | + |
| 12 | +> success "" |
| 13 | +> Segment recommends configuring Custom Domain alongside [Consent Management](/docs/privacy/consent-management/) to ensure you are respectful of your end users' consent preferences. |
| 14 | +
|
| 15 | +{% include content/domain-delegation-solutions.md %} |
| 16 | + |
| 17 | +### How DNS subdomain delegation works |
| 18 | +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. |
| 19 | + |
| 20 | +### How CNAME records work |
| 21 | +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. |
| 22 | + |
| 23 | +CNAME records provide flexibility and centralized management, making it easier to handle domain redirections and subdomain configurations. |
| 24 | + |
| 25 | +Implementing a Custom Domain using CNAME delegation requires you to add a CNAME and record for two domains that Segment generates on your behalf: one for the Segment CDN and a second for the Tracking API. You must add a CNAME and DNS record for both domains. |
| 26 | + |
| 27 | +## Supported sources |
| 28 | + |
| 29 | +Custom Domain supports the following sources: |
| 30 | +- [Analytics.js](docs/connections/sources/catalog/libraries/website/javascript/) |
| 31 | +- [Clojure](/docs/connections/sources/catalog/libraries/server/clojure/) |
| 32 | +- [Go](/docs/connections/sources/catalog/libraries/server/go/) |
| 33 | +- [Java](/docs/connections/sources/catalog/libraries/server/java/) |
| 34 | +- [Node.js](/docs/connections/sources/catalog/libraries/server/node/) |
| 35 | +- [PHP](/docs/connections/sources/catalog/libraries/server/php/) |
| 36 | +- [Python](/docs/connections/sources/catalog/libraries/server/python/) |
| 37 | +- [Ruby](/docs/connections/sources/catalog/libraries/server/ruby/) |
| 38 | +- [.NET](/docs/connections/sources/catalog/libraries/server/net/) |
| 39 | + |
| 40 | +## Getting started |
| 41 | + |
| 42 | +> info "Custom Domain is only available to Business Tier customers" |
| 43 | +> 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/). |
| 44 | +
|
| 45 | +To configure Custom Domain: |
| 46 | +1. Select the subdomain you'd like Segment to use for event request tracking (for example, `cdp.domain.com`). |
| 47 | +2. Sign into the Segment app, select your user avatar, and click **Contact Support**. |
| 48 | +3. Create a support request with the following fields: |
| 49 | + - **Topic**: Select **Custom Domain**. |
| 50 | + - **Subject**: Enter a subject line for your support request. |
| 51 | + - **Domain Name**: Enter the subdomain that Segment should use for event request tracking. |
| 52 | + - **Additional Domain Name**: If applicable, add an additional subdomain. This field is optional. |
| 53 | + - **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). |
| 54 | + - **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. |
| 55 | + - **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. |
| 56 | +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. |
| 57 | +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. |
| 58 | +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. |
| 59 | + |
| 60 | +## FAQ |
| 61 | + |
| 62 | +### What sources can I use with Custom Domain? |
| 63 | +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. |
| 64 | + |
| 65 | +Once Custom Domain is enabled for your workspace, the Segment app generates a new JavaScript source code snippet for you to copy-paste into the header of your website. For non-JavaScript sources, you can use the sub-domain as an endpoint when using the Tracking API. |
| 66 | + |
| 67 | +### Is this a fully-managed solution? What servers or infrastructure do I need to set up on my side for this proxy? |
| 68 | +Yes, Custom Domain is a fully-managed solution. |
| 69 | + |
| 70 | +You must be able to delegate a DNS subdomain to Segment and add the name servers Segment provides to your DNS. |
| 71 | + |
| 72 | +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. |
| 73 | + |
| 74 | +### Can I change my Segment subdomain after the initial setup? |
| 75 | +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 are required to redo the entire onboarding process, as several underlying components, like certificates, would need to be recreated and reassociated. |
| 76 | + |
| 77 | +### Who is responsible for managing the SSL certificate for the Custom Domain? |
| 78 | +Segment hosts and manages SSL Certificate on the Custom Domain. At this time, Segment does not support importing a certificate you may already have, as Segment must request a SSL certificate on your behalf using AWS Certificate Manager (ACM) when initially setting up your Custom Domain. |
| 79 | + |
| 80 | +Segment also uses AWS Certificate Manager (ACM) to manage and renew certificates. |
| 81 | + |
| 82 | +### Can you rename `window.analytics` with Custom Domain? |
| 83 | +Yes, Custom Domain allows Segment to rename `window.analytics` to a unique name to avoid being blocked by some ad blocking software. |
| 84 | + |
| 85 | +Customers who have access to the Custom Domain feature can rename analytics to `<workspaceid>/<sourceid>.js` by choosing an Alias for Analytics.js within the source settings that are available after the workspace is enabled for Custom Domain. |
0 commit comments