Requirements
This feature is only available for private embed use cases. Additionally, the domain you select has a set of requirements:- Only one vanity domain is allowed per Omni organization.
- Have a multi-part domain like
products.ecommerce.comordev.products.ecommerce.com. - You must use a new, dedicated subdomain:
- Omni needs to configure specific DNS records and SSL certificates for the domain.
- The domain must be set up to proxy requests to Omni’s infrastructure.
- Existing endpoints serve different content and can’t be repurposed for Omni embeds.
Selecting a domain
When selecting a domain, keep the following in mind:- A vanity domain must have three, or more, parts. For example,
ecommerce.comwithoutproductsprepended will not be considered a valid vanity domain. - The top-level domain of the vanity domain must match the embedding page to support first party cookies.
- If your embedding page is
ecommerce.com, then your embedded vanity domain should beomni.ecommerce.com - If your embedding page is
ecommerce.comand you provide an embedded vanity domain ofecommerce.omni.comthen you may still run into third-party cookie limitations on some browsers like Safari or other iOS applications.
- If your embedding page is
SDK example
Typescript SDKVanity domain of analytics.blobsrus.com
Setup
- Reach out to Omni support with the vanity domain you want to use, e.g.
products.ecommerce.com. - Omni will reach back out with DNS configuration details and ask that you update your DNS configuration.
- Notify Omni that the update is complete.
- Omni will notify when the setup is complete.