Show Menu

About first-party cookies

Analytics uses cookies to provide information on variables and components that do not persist between image requests and browser sessions. These harmless cookies, which originate from a domain hosted by Adobe, are known as third-party cookies.
Many browsers and anti-spyware applications are designed to reject and delete third-party cookies, including those used in Analytics data collection. To support your tracking of how your visitors interact with your website, you can implement first-party cookies.
Two options are available to implement first-party cookies:
  • The Experience Platform ID Service. The ID Service can set the cookie in the first-party context using JavaScript.
  • DNS entries on your company's DNS server to configure a CNAME alias to an Adobe hosted domain. Please note that while various Adobe products support using a CNAME, in all cases the CNAME is used to a create a trusted first-party endpoint for a specific customer and is owned by that customer. If that customer controls multiple domains, they may use a single CNAME endpoint to track users across their domains, but as this requires third-party cookies for all domains outside of the CNAME’s domain, it does not work when third-party cookies are blocked and so is not recommended. Adobe CNAMEs are never used to track an individual or device across domains owned by different customers.
Even when using the first option with the Experience Cloud ID Service, Apple's ITP will make the first-party cookies short-lived, so it is best used in conjunction with the second option.
For the second option using a CNAME, if your site has secure pages using the HTTPS protocol, you can work with Adobe to obtain an SSL certificate in order to implement first-party cookies. Adobe strongly recommends that you exclusively use HTTPS for data collection as we will be dropping support for HTTP collection in the second half of 2020.
The SSL certificate issuance process can often be confusing and time consuming. As a result, Adobe established a partnership with DigiCert, an industry leading Certificate Authority (CA), and developed an integrated process by which the purchase and management of these certificates is automated.
With your permission, we will work with our CA to issue, deploy, and manage a new SHA-2 SSL certificate for you. Adobe will continue to manage this certificate and ensure that an unexpected expiration, revocation, or security concern, does do not threaten the availability of your organization's secure collection.

Adobe Managed Certificate Program

The Adobe Managed Certificate Program is the recommended process for implementing a new first-party SSL certificate for first-party cookies.
The Adobe Managed Certificate program lets you implement a new first-party SSL certificate for first-party cookies at no additional cost (for your first 100 CNAMEs). If you currently have your own Customer Managed SSL certificate, speak with Adobe Customer Care about migrating to the Adobe Managed Certificate Program.


Here is how you implement a new first-party SSL certificate for first-party cookies:
  1. Fill out the First-party cookie request form and open a ticket with Customer Care requesting to set up first-party cookies on the Adobe Managed program. Each field is described within the document with examples.
  2. Create CNAME records (see instructions below).
    Upon receiving the ticket, a customer care representative should provide you with a pair of CNAME records. These records must be configured on your company's DNS server before Adobe can purchase the certificate on your behalf. The CNAMES will be similar to the following:
    Secure - For example, the hostname points to: .
    Non-secure - For example, the hostname points to: .
  3. When these CNAMES are in place, Adobe will work with DigiCert to purchase and install a certificate on Adobe's production servers.
    If you have an existing implementation, you should consider visitor migration to maintain your existing visitors. After the certificate has been pushed live to Adobe’s production environment, you can update your tracking server variables to the new hostnames. Meaning, if the site is not secure (HTTP), update the s.trackingServer . If the site is secure (HTTPS), update both s.trackingServer and s.trackingServerSecure variables.

Maintenance and Renewals

SSL certificates expire each year, meaning Adobe must purchase a new certificate for each implementation on a yearly basis. All supported users within your organization will receive an email notification each time an implementation is close to expiration. For Adobe to renew your hostname, one supported user must reply to the email from Adobe and indicate that you plan to continue using the expiring hostname for data collection. At that point, Adobe automatically purchases and installs a new certificate.

Frequently Asked Questions

Is this process secure?
Yes, the Adobe Managed program is more secure than our legacy method as no certificate or private key changes hands outside of Adobe and the issuing certificate authority.
How can Adobe purchase a certificate for our domain?
The certificate can only be purchased when you have pointed the specified hostname (for example, ) to an Adobe owned hostname. This is essentially delegating this hostname to Adobe and allows Adobe to purchase the certificate on your behalf.
Can I request that the certificate be revoked?
Yes, as the owner of the domain, you are entitled to request we have the certificate revoked. You will only need to open a ticket with Customer Care to have this completed.
Will this certificate be using SHA-2 encryption?
Yes, Adobe will work with DigiCert to issue a SHA-2 certificate.
Does this incur any additional cost?
No, Adobe is offering this service to all current Adobe Digital Experience customers at no additional cost.

Create CNAME records

Your organization's network operations team should configure your DNS servers by creating new CNAME record(s). Each hostname forwards data to Adobe's data collection servers.
The FPC specialist provides you with the configured hostnames and what CNAMEs they are to be pointed to. For example:
  • SSL Hostname :
  • Non-SSL Hostname :
  • Non-SSL CNAME :
As long as implementation code is not altered, this step will not affect data collection and can be done at any time after updating implementation code.
The Experience Cloud Visitor ID service provides an alternative to configuring a CNAME to enable first-party cookies, but because of recent Apple ITP changes, it is still recommended to allocate a CNAME even when using the Experience Cloud ID Service.

Validate hostname forwarding

The following methods are available for validation:

Validate using a browser

If you have a CNAME set up and the certificate installed, you can use the browser for validation:
You will see a security warning if a certificate is not installed.

Validate using curl

Adobe recommends using curl from the command line. (Windows users can install curl from: )
If you have a CNAME but no certificate is installed, run: curl -k Response: SUCCESS
(The -k value disables the security warning.)
If you have a CNAME set up and the certificate is installed, run: curl Response: SUCCESS

Validate using nslookup

You can use nslookup for validation. Using as an example, open a command prompt and type nslookup
If everything is successfully set up, you will see a return similar to:
Address:    canonical name =

Update implementation code

Before you edit code on your site to utilize first-party cookies, complete these prerequisites:
  • Request an SSL certificate, by following the steps described above in the Implement section of the Adobe Managed Certificate Program .
  • Create CNAME records (see above).
  • Validate the hostname(s) (see above).
After you have verified your hostname(s) are responding and forwarding to Adobe data collection servers, you can alter your implementation to point to your own data collection hostnames.
  1. Open your core JavaScript file ( s_code.js/AppMeasurement.js ).
  2. If you want to update your code version, replace your entire s_code.js/AppMeasurement.js file with the newer version and replace any plugins or customizations (if any). Or , if you want to update the code only pertinent to first-party cookies, locate the s.trackingServer and s.trackingServerSecure (if using SSL) variables, and point them to your new data collection hostnames. Using as an example: s.trackingServer = "" s.trackingServerSecure = ""
  3. Upload the updated core JavaScript file to your site.
  4. If you are moving to first-party cookies from a long-standing implementation, or changing to a different first-party collection hostname, we recommend migrating visitors from the previous domain to the new domain.
See Visitor Migration in the Analytics Implementation Guide.
After you have uploaded the JavaScript file, everything is configured for first-party cookie data collection. We recommend that you monitor Analytics reporting for the next several hours to ensure that data collection continues as normal. If it does not, verify that all above steps have been completed and have one of your organization's supported users contact Customer Care.