Cookieless World

Cookies are small text files stored on a customer's device. They primarily track users and collect information on their activities across devices. However, with the growing demand for privacy, users want control over how their personal data is used. In addition, new regulations have been implemented that limit the placement of cookies or other similar technologies on organizations' websites without the users' consent.

Thanks to Cookieless World, you show your campaigns to all visitors regardless of their cookie acceptance status. To enable this flexibility, Insider has two different flows: Cookie-free Insider Tag and Insider Tag (ins.js).

In the Cookie-Free Insider Tag, campaigns will be triggered even if the user's cookie consent is not provided, without storing Local Storage and Cookies.

Reach out to the Insider One team if you want to integrate and use the Cookie-Free Insider Tag.

If you are an existing customer and want to integrate and use the Cookie-Free Insider Tag, you need to update your current Insider Tag integration.

If you are a new customer and want to integrate and use the Cookie-Free Insider Tag, you need to complete the integration according to the Cookie-Free Insider Tag guidelines.

In this guide, you will find answers to these questions:

• How does a Cookie-free Insider Tag work?

• What are the limitations of the Cookie-free Insider Tag?

• What products and templates can be visible in the Cookie-free Insider Tag?

• What products and templates cannot be visible in the Cookie-free Insider Tag?

• What rules cannot work in the Cookie-free Insider Tag?

How does a Cookie-free Insider Tag work?

When a user visits your website, the Cookie-free Insider Tag will be initialized directly, and campaigns that meet the criteria will be visible to your users. Until the user accepts marketing cookies, the Cookie-free Insider Tag will work with the restricted functions. When the user consents, the Insider Tag will replace the Cookie-free Insider Tag, and the current flow will continue. When the cookie acceptance status changes, the flow will change, too. For example, the Insider Tag will be replaced with the Cookie-free Insider Tag if an opted-in user rejects cookies or vice versa.

Flow 1 - Cookies are rejected

Assume a user visits your website, and a cookie bar appears to request their consent. Even though they do not take any action, the Cookie-free Insider Tag is loaded into the website because you classify Insider Tag codes under Essential cookies. Essential cookies are exempt from user consent, as they are necessary for the website's functionality. As the Cookie-free Insider Tag is loaded, the user will be eligible to see OnSite campaigns. However, as they have not yet agreed to be tracked by third parties, none of the data will be stored via Local Storage, which means you cannot measure how many users view campaigns or what kind of interaction users have with them. For example, a user can see a “Back to Top” campaign when they scroll down or a “Hello Bar” campaign when they land on the category page if these campaigns are suitable for the Cookie-free Insider Tag. Still, you cannot track the analytics of the campaigns that come from opted-out users. The overall analytics refer only to the data of users who accept cookies.

Flow 2 - Marketing Cookies are accepted

After visiting some pages, the user changes their mind and wants to see a personalized experience, accepting Marketing Cookies or All Cookies. The Insider Tag (current ins.js) is loaded when they click the accept button. You can start tracking and storing data via Local Storage, retrieve unique statistical data, and display all eligible campaigns to the user.

What are the limitations of the Cookie-free Insider Tag?

• Local Storage and Cookies will not be set (except essential cookies), so there will be no data tracking for those users.

• Essential Local Storage will be stored only in the same session.

• Data will not be collected as statistical data requires the acceptance of “Analytical Cookies.”

• Segmented campaigns will not be included since they require setting values in Local Storage.

• There will be no variation in stickiness. This means that they will see the first variation now but might see the second one in the next session.

• User-based Recommendations will not be included since they require setting values in Local Storage.

• Coupon Code campaigns will not be included since they require setting values in Local Storage.

• Campaigns that include more than one variant will not be visible in the Cookie-free Insider Tag if any of the variants are unsuitable.

• Campaigns that require Local Storage to function will not be included.

What products and templates can be visible in the Cookie-free Insider Tag?

What products and templates cannot be visible in the Cookie-free Insider Tag?

What rules cannot work in the Cookie-free Insider Tag?