---
title: "Cookie-Free Insider Tag Integration"
slug: "cookie-free-insider-tag-integration"
description: "Explains how to integrate Insider One's Cookie-Free Insider Tag, covering setup, CookieBot, GTM, OneTrust, BayCloud, Wix, and verification steps here."
tags: ["cookie-free insider tag", "integrate cookie-free tag", "check insider tag integration"]
updated: 2026-08-26T16:54:16Z
published: 2026-08-26T16:54:16Z
canonical: "academy.insiderone.com/cookie-free-insider-tag-integration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cookie-Free Insider Tag Integration

Cookieless World allows you to show campaigns to all visitors, regardless of whether they accept cookies. To support this flexibility, Insider One provides two different flows:

- Cookie-Free Insider Tag
- Standard Insider Tag (ins.js)

To integrate the Cookie-Free Insider Tag, also known as tracking website visitors without relying on cookies, contact the Insider One team. Once enabled, the status badge will display “Enabled.”

> [!NOTE]
> The Cookie-Free Insider Tag requires a separate integration. **Existing customers** must update their current integration to ensure seamless operation. **New customers** should follow the steps outlined here to use the Cookie-Free Insider Tag.

> [!NOTE]
> Load only one Insider Tag per page.
> 
> Do not run the Cookie-Free Insider Tag and the Standard Insider Tag at the same time. Load a single version based on the visitor’s cookie consent status. Running both flows together can cause conflicts in campaign behavior, including repeated reinitialization and incorrect display results.
> 
> Select the tag from the visitor’s consent status, and push the user' choice according to this integration article so that only one tag initializes per page:
> 
> - When the visitor has not given consent, load the Cookie-Free Insider Tag.
> - When the visitor gives consent, load the Standard Insider Tag.

![This image shows an enabled cookie-free Insider tag screen.](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1759412485857.png)

You can integrate the Insider Tag into your website in multiple ways. The main logic follows this algorithm:

```plaintext
if (cookies_accepted) {
    load Insider Tag
} else {
    load Cookie-Free Insider Tag
}
```

The condition inside "**if**" varies according to the partner.

## Standard Insider Tag (ins.js)

1. Define **insiderFlow** variable globally and set it to 3:

```plaintext
window.insiderFlow = 3;
```

2. Integrate the script from the following source:

```plaintext
YOURPARTNERNAME.api.useinsider.com/ins.js?id=YOURPARTNERID
```

If you are using Cookie Bot (or a similar tool), declare this script under **Marketing Cookies**.

## Cookie-Free Insider Tag

1. Define **insiderFlow** variable globally and set it to 1:

```plaintext
window.insiderFlow = 1;
```

2. Integrate the script from the following source:

```plaintext
YOURPARTNERNAME.api.useinsider.com/ins.js?c=0
```

If you are using Cookie Bot (or a similar tool), declare this script under **Essential Cookies**.

> [!NOTE]
> The integration can be done in either HTML or JavaScript. If you are using Google Tag Manager (GTM), you must use the HTML approach.

## Custom Implementation

You can also apply the Cookie-Free Insider Tag using a custom integration. This can be set up either via Google Tag Manager (GTM) or by hard-coding values directly into your website code.

For example, if you are using Drupal Cookie Compliance, you can check the user’s cookie status with the following snippet:

```plaintext
Drupal.eu_cookie_compliance.getCurrentStatus()
```

This function returns a value if cookies are accepted. It returns an empty string if cookies are not accepted.

For other custom setups, the condition may rely on:

- A cookie value, or
- A global variable provided by your cookie consent solution.

This flexibility lets you align Insider Tag logic with your existing consent management flow.

## CookieBot and GTM Integration for Insider Tags

When using [CookieBot](https://www.cookiebot.com/) with Google Tag Manager (GTM), several events are fired depending on the user’s consent selection.

If the marketing option (or all options) is selected, the **cookie_consent_marketing** event is triggered. The consent information is stored under the **CookieConsent.consented** variable.

Below are the steps for implementing Insider Tag and Cookie-Free Insider Tag using CookieBot and GTM.

### Implement Insider Tag

1. On your GTM account, add the script as HTML and select the **Once per event** option in the firing options. ![This image shows how to select tag firing options on GTM for cookie-fee Insider tag.](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686655554094.png)

2. Choose **Custom Event** to trigger, type **cookie_consent_marketing** as a value, and save the configuration. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686655601988.png)

### Implement Cookie-Free Insider Tag

1. Add the script as HTML and select the **Once per page** option in the firing options.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686655922341.png)

2. Select **Custom Event** for trigger and type **gtm.load** as the event name. Note that this event is triggered after the CookieBot banner, so it can safely be used here.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686656305603.png)

3. Select **New Variable** in the **Event** field. Then, select **JavaScript Variable** from **Page Variables**.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686656664656.png)

4. Type **CookieConsent.consented** as the variable name and save it. Then, select **equals** from the dropdown menu and type *false* as the condition.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686656887124.png)

5. Save and publish your setup.

When CookieBot is integrated via GTM and a user withdraws their consent, the update only takes effect after a page reload:

- If a user initially accepts cookies → the Insider Tag loads.
- If the same user then withdraws consent on the same page, the Cookie-Free Insider Tag will not load immediately.
- It will load correctly on the next page reload.

**![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686671334493.png)**

## OneTrust

[OneTrust](https://www.onetrust.com/) stores the groups of your cookies under the **window.OnetrustActiveGroups** variable and its outcome might vary. The implementation must be as follows:

### Integration via JS code on your website

```javascript
var source = 'partnerName.api.useinsider.com/ins.js?c=0'

window.insiderFlow = 1;

if (window.OnetrustActiveGroups.includes('YOUR_CONSENT_ID_HERE')) {
    window.insiderFlow = 3;
    source = 'partnerName.api.useinsider.com/ins.js;
}

var _s = document.createElement('script');

_s.setAttribute('src', source);

document.head.appendChild(_s); // head or body
```

### Integration via GTM

Alternatively, if you integrate **ins.js** via Google Tag Manager (GTM), you can do it by triggering a tag on a custom event called **OneTrustGroupsUpdated**.

1. Add **Insider code** as a Tag via **Custom HTML** option.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686660112004.png)

2. Select **Custom Event** for the Trigger type.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686660290242.png)

3. Type **OneTrustGroupsUpdated** as the event name, and select **Some Custom Events** for firing options.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686660644689.png)

4. Select **New Variable** in the **Event** field.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686660719915.png)

5. Select **JavaScript Variable** from **Variable types**. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686661268480.png)

6. Type **OnetrustActiveGroups** as the variable name and save it.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686661509523.png)7. Choose the **contains** option from the dropdown and write your consent IDs.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1686661740183.png)

8. Apply the same for Insider Tag with consent IDs for marketing or all cookies, save, and publish.

## BayCloud

If you are using [BayCloud](https://baycloud.com/cookienotice), you can import **ins.js** with the following check:

### Integration via JS Code on your website

```javascript
var source = 'YourPartnerName.api.useinsider.com/ins.js?c=0'

window.insiderFlow = 1;

if (__cqheldcStatus.agreed === 'all') {
    window.insiderFlow = 3;
    source = 'YourPartnerName.api.useinsider.com/ins.js;
}

var _s = document.createElement('script');

_s.setAttribute('src', source);

document.body.appendChild(_s);
```

## Wix

If you are using Wix to host your website, it’s best to check its cookie policy, as Wix’s cookie bar loads after the Essential codes.

- Cookies are stored in the browser, so there’s no need to wait for any function, and the following code can be applied to load the Cookie-Free Tag:

```javascript
<script>
(() => {
const getCookie = (e) => {
    let t, n, o = '[;\\s ]?' + e + '=([\\S]+(?:;?))';
    return (null === (n = null === (t = document.cookie.match(o)) || void 0 === t ? void 0 : t.pop()) || void 0 === n ? void 0 : n.replace(';', '')) || void 0;
}

const r = JSON.parse(decodeURIComponent(getCookie('consent-policy') || 'false'));

if (r || r.anl || r.adv) { return; }

window.insiderFlow = 1;

const s = document.createElement('script');
s.setAttribute('src', 'https://YourPartnerName.api.useinsider.com/ins.js?c=0');
document.head.appendChild(s);
})();
</script>
```

This code checks the existence of the cookie:

- If the cookie is not present (i.e., no consent interaction was made), the code loads the Cookie-Free Tag.
- The code loads the Cookie-Free Tag if the cookie is present, and the values do not include analytical or marketing ones.
- The code does nothing in other cases, since those are covered by Marketing Code Types.

## Check the Cookie-Free Insider Tag Integration

If Cookie-Free Insider Tag is integrated into your website, you can check the steps below to ensure the integration works properly:

### Scenario 1

1. Visit the website in incognito mode and see the cookie bot.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728282270770.png)
2. Inspect the page, open the console, and Run “*Insider*” in the console. It should be initialized with the consent variable as 1.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728283078315.png)
3. Run “*insiderFlow*” in the console. It should be “1”.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728283198909.png)
4. Go to the Application tab and open the *partnerName.api.useinsider.com* under the Local Storage. There should be a maximum of 8 storage locations, and the spUID should not be listed.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728283615149.png)

### Scenario 2

1. Accept cookies on the website and then return to the console tab.
2. Run “*Insider*” in the console. It should be initialized with the consent variable as 3.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728284024830.png)
3. Run “i*nsiderFlow*” in the console. It should be “3.”

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728284366911.png)
4. Go to the Application tab and open the *partnerName.api.useinsider.com* under the Local Storage. All the storages should be listed except for the spUID.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728284711136.png)

### Scenario 3

1. Reject the cookies after Scenario 2.
2. Open the console and run “*Insider*”. It should be initialized with the consent variable as 1.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728285205736.png)
3. Run “*insiderFlow*” in the console. It should be “1”.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728285369938.png)
4. Go to the Application tab and open the *partnerName.api.useinsider.com* under the Local Storage. There should be a maximum of 8 storages, and spUID should not be listed.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728283615149.png)

### Scenario 4

1. Close the window and open a new incognito window. Visit your website and reject the cookies.
2. Open the console and run “*Insider*”. It should be initialized with the consent variable as 1.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728285790173.png)
3. Run “*insiderFlow*” in the console. It should be “1”.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728285847667.png)
4. Go to the Application tab and open the *partnerName.api.useinsider.com* under the Local Storage. There should be a maximum of 8 storage and spUID should not be listed.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1728283615149.png)

---

If you check all these steps and everything works as expected, the integration works correctly.