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. In order to side step the restrictions you have the option to set cookies through the server rather than having to rely on document.cookie. This is true for our AMP and website implementations. To accomplish this, you need to set up a CNAME DNS record for a 1st party subdomain and include it in the AMP or website's configuration snippet.
There are two ways to set up the CNAME record for your AMP and website implementations. The difference between the two methods depends on whether Sourcepoint is setting up the TLS certificates for https traffic or whether you are setting up your own TLS certificates and provide Sourcepoint with the details.
Set up a 1st party subdomain and create a CNAME record pointing to
Notify Sourcepoint that the CNAME record has been set up.
Sourcepoint establishes a TLS certificate for the cname record.
Sourcepoint then creates an account specific CDN endpoint. If the account ID is 222 then Sourcepoint sets up the subdomain of
Sourcepoint then notifies you that the CDN endpoint has been set up.
Finally, update the CNAME record to point to the new Sourcepoint CDN endpoint. In our example, this is
Set up a 1st party subdomain and inform Sourcepoint that you want to use your own TLS certificate.
Sourcepoint provides you with the CSR file for the subdomain TLS cert application.
Apply the certificates and send the certificate back to Sourcepoint.
Sourcepoint tests and verifies the certificate.
Sourcepoint deploys the certificate.
Sourcepoint then creates an account specific CDN endpoint. If the account ID is 222 then Sourcepoint sets up the CDN endpoint of
The site then updates the CNAME record to point to the new Sourcepoint CDN endpoint. In our example, this is
The subdomain for which the CNAME record was created is referenced in the parameters for the AMP and website configuration snippets.