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

# Radar and your cookie banner

> How Radar works with a cookie or consent banner: when the script runs, why your numbers can drop after you add a banner, and what to check if nothing arrives.

A cookie banner, also called a consent banner, is the message that asks your visitors whether they accept tracking on your site. Radar does not notice your banner on its own: the two work together only if you connect them. This page explains what that changes for your numbers, and what to check when something looks wrong.

> [!NOTE]
>
> This page explains how Radar behaves. It is not legal advice. To decide whether your own site needs a banner, start with [privacy, cookies and GDPR](https://docs.taap.it/help/radar/privacy-and-consent.md).

## How Radar and a banner work together

Radar respects your banner only if you connect the two.

| Your setup | What happens |
| - | - |
| The Radar script is loaded through a tag manager or a consent tool, set to fire once tracking is allowed | Radar runs only after the visitor allows tracking. It does not see the sessions of visitors who have not accepted. |
| The Radar script is not connected to your banner | Your banner changes nothing for Radar. |

## Quick check: is Radar connected to your banner?

Do this before you change anything.

**1. Open your published site**

Use a browser where you have not answered your banner yet, so the banner shows.

**2. Browse without answering the banner**

Load two pages and click a link. Then look at Radar: when the script runs, a visit shows up within a few seconds.

**3. Accept tracking, then browse again**

Accept in your banner, load two pages, click a link, and look at Radar again.

| What you see | What it means |
| - | - |
| Your visit appears only after you accept | Radar is connected to your banner. |
| Your visit appears before you answer the banner | Radar is not connected to your banner. |
| No visit, even after you accept | The problem is not the banner. Go through [I installed the script but I see no data](https://docs.taap.it/help/radar/no-data.md). |

## Your numbers dropped after you added a banner

This is expected. Once Radar waits for consent, it does not see the sessions of visitors who have not accepted, so your figures are lower than your real traffic.

To measure the change, compare the weeks before and after the banner went live. See [choose a period and compare it with another](https://docs.taap.it/help/radar/features/date-range-compare.md).

## Radar shows nothing since you added a banner

**1. Test as a visitor who accepts**

Open your published site, accept tracking in your banner, then load two pages and click around. If Radar is held back by the banner, it only runs after this step.

**2. Check the tag in your tag manager**

If Radar is loaded through a tag manager, check that the Radar tag fires when tracking is allowed. See [install Radar with Google Tag Manager](https://docs.taap.it/help/radar/install-with-google-tag-manager.md).

**3. Go through the full checklist**

Still nothing after you accept? The cause is somewhere else: the domain, the project key, or a site that was not published. See [I installed the script but I see no data](https://docs.taap.it/help/radar/no-data.md).

## Connect Radar to your banner

How you connect the two depends on the banner tool you use. The usual way is to load the Radar script through your tag manager or your consent tool, and to make sure it fires once tracking is allowed. With Google Tag Manager, follow [install Radar with Google Tag Manager](https://docs.taap.it/help/radar/install-with-google-tag-manager.md).

How you set this up is your decision as the site owner.

## Do you need a banner for Radar?

It depends on how you use Radar:

* With anonymized analytics only, a banner is often not needed, depending on your use case and on how GDPR is read in your country.
* With features that identify visitors or store data on their device, a banner is required. See [identify visitors](https://docs.taap.it/help/radar/features/identify-visitors.md).

The details are in [privacy, cookies and GDPR](https://docs.taap.it/help/radar/privacy-and-consent.md).

## Still stuck?

Contact support from the chat in your dashboard or at [hello@taap.it](mailto:hello@taap.it), and send the address of your site.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.