How to see if your Cookie Saver setup is working

Once Cookie Saver has been deployed, you will be able to evaluate if your setup is working correctly right away.

This guide explains how to evaluate your configuration by running a command or by checking the list of your cookies from a browser console. The validation of the configuration can be carried out from any browser, however, the validation of the cookies needs to be done from a Safari browser. 

Validate configuration

You can easily check that your setup does not include errors by running the following command in your browser console:

acq("validate");

This will go through your configuration and list any misconfigurations where, e.g. the specified cookie domain is not compatible with the current website domain. In the following example, everything is configured correctly for "cookiesaver.io".

Validate result (from Safari)

You will always be able to see a "_acs_DOMAIN" cookie (where DOMAIN is your website root domain), placed in the root domain. This includes the back up of your cookies set in the root domain (if using backup cookies). If you are on a subdomain, you may see one "_acs_DOMAIN" cookie per subdomain (depending on configuration). 

For "cookiesaver.io" we have the following setup (Name, Value, Domain, Path, Expiration):

Where:

• "CookieConsent" is set without a leading dot. This is intentional as cookie consent is given per domain and it should not be shared across domains. As this cookie needs to be set client-side, we have a backup in the "_acs_cookiesaver.io" cookie so it can be restored properly if deleted by ITP. Because it is set client-side expiration can max be 7 days, but Cookie Saver will make sure to restore it if unintentionally removed. 
• "_fbp" is one of the Facebook cookies. It is set with a leading dot. As the Facebook script automatically overwrites the cookie (and thus ITP restrict expiration to 1 or 7 days), Cookie Saver automatically renews the cookie from the backup if it has expired unintentionally.
• "AMCV_DE7B......" is our Adobe Analytics visitor cookie. It is configured similar to the "_fbp" cookie.
• "_acs_cookiesaver.io" is our backup cookie that contains backup versions of the cookies that we want to save, and that are configured to use a backup.
• "_ga" is or Google Analytics cookie. We have configured Google Analytics to not automatically renew the "_ga" cookie. Cookie Saver is configured to renew the "_ga" cookie every session without using a backup.