The ability to prolong custom cookies using Cookie Keeper is available for Business (and higher) plan users. You only need one thing to do: activate our power-up Cookie Keeper.

You can find the list of standard cookies that Cookie Keeper prolongs here.

How it works:

1. Add cookie name and expiration time in days. 

2. The Cookie Keeper will always restore the specified cookies when the expiration time is set to auto.

3. It remembers each user's unique ID. This "master cookie" fits with all ITP regulations and is kept on your website as a first-party cookie.

4. If any marketing cookies (for example, Google Analytics, Google Ads, TikTok, Facebook, or Stape) are missing or destroyed, the Cookie Keeper will restore these cookies using the master cookie's information.

5. The Cookie Keeper power-up sets the cookie to the domain with dot (not stape.io but .stape.io).

Note: Cookie Keeper will set the cookie on .domain.com, not domain.com
This means that the Cookie Keeper will get all cookies that are available for the client’s custom domain, and save cookies that the client sets on the Cookie Keeper setup page to be saved. 

And Cookie Keeper will set them on .domain.com (with dot before the domain name, not domain.com).

The value for the Domain attribute contains no embedded dots, and the value is not .local.

How to use Cookie Keeper:

1) Activate Cookie Keeper in Stape Power-Ups for your container. In the settings, select the platforms you need, and add custom cookies if necessary.

For Business-tier users and above, you can also use any additional custom cookies. For example, if you use Twitter Ads, you can add the "twclid" cookie so that the click ID cookie for Twitter is also restored for the necessary duration.

2) To use Cookie Keeper, you'll need to replace the GTM loader snippet.

Domain - from the list of domains connected to your container, select the necessary ones. 

Web GTM ID - add web Google Tag Manager ID. Check out how to find web GTM ID in our guide.

GA4 ad block bypass - enables bypassing adblockers' impact on the GA4 tracking code. Note that this setting will affect all container domains. Be sure to debug both the web and server GTM containers after enabling this toggle.

Same Origin Path - if you are using same origin approach for configuring custom domain, please specify the proxy path for requests. Learn more.

Platform - the custom loader code differs for each platform. Select your platform or "Other" if it is not on the list.

Additional settings:

• Data Layer variable name - specify if you use a non-standard ‘dataLayer’; otherwise, leave it empty.
• Generate with CDN - available only if the selected domain has an active Stape CDN. If enabled, the container will be loaded from a server closer to your site visitors.
• Use the original GTM code - if enabled gtm.js will not be replaced and your GTM container ID will not be encrypted. With this option enabled, the protection against adblockers will be much lower.
• Generate with Cookie Keeper - available if you have the Cookie Keeper power-up active. If enabled, the code will also add Cookie Keeper operation along with GTM loading.
• User identifier type - available if the ‘Generate with Cookie Keeper’ option is active. The recommended method of identification is Cookie. For more details, see the article on how to choose a User Identifier. 

Click “Generate”. Please note that just generating it doesn't do anything; you also need to make the necessary changes on the website (add code) or in the Stape applications if you use any.