Configure subdomain with CNAME DNS record

In this article, we will cover how to configure a subdomain with a CNAME DNS record for your property.


Benefits of subdomain with CNAME DNS record

By configuring a subdomain with a CNAME DNS record for your property, your organization can side step the following issues:

  • Certain browser environments restrict the use of 1st-party cookies (e.g. Safari's ITP) and limit our ability to persist user consent records for a longer period of time.
  • It can be the case that an end-user's adblocker inadvertently blocks the Sourcepoint script from running on your property.

In order to side step these issues, you have the option to set cookies through the server rather than having to rely on document.cookie. To accomplish this, you need to set up a CNAME DNS record for a 1st-party subdomain and include it in the website's configuration snippet. 


Configure subdomain with CNAME DNS record

  Note: If you already have a CNAME record pointing to either the mms.sp-prod.net or message.sp-prod.net, Sourcepoint recommends setting up a new subdomain to make the transition to the new single name CNAME solution easier.

Additionally, in order to reduce the risk of being identified by block lists, Sourcepoint recommends that your organization avoids using cmp or privacy in your subdomains (e.g. cmp.domain or privacy.domain). Instead, consider using the following or a variation of the following: consent.domain or cmpv2.domain.

Sourcepoint requires that new clients who wish to configure a subdomain with a CNAME DNS record follow the below instructions:

  1. Set up a 1st party subdomain and create a CNAME record pointing to cert.privacy-mgmt.com.
  2. Notify Sourcepoint that the CNAME record has been set up.
  3. Sourcepoint establishes a TLS certificate for the CNAME record.
  4. Sourcepoint then creates an account specific CDN endpoint. If the account ID is 222 then Sourcepoint sets up the subdomain of cdn-222.privacy-mgmt.com.
  5. Sourcepoint then notifies you that the CDN endpoint has been set up.
  6. Finally, update the CNAME record to point to the new Sourcepoint CDN endpoint. In our example, this is cdn-222.privacy-mgmt.com.
  7. Update the baseEndpoint in your client configuration script with your CNAME:
    ...
    window._sp_ = {
        config: {
            accountId: 22,
            baseEndpoint: 'https://cname.subdomain',
            ccpa: { },
            gdpr: { }
        }
            ...
  8. Update the URL to messaging library in your client configuration script with your CNAME property and following the below format:
    ...
     <script src="https://cname.subdomain/unified/wrapperMessagingWithoutDetection.js" async> </script>      
    ...
Was this article helpful?
0 out of 0 found this helpful