Clarity & Cookie: new requirements

Clarity is the tool that most of us use for heatmapping and recording users on the site and has gradually replaced the more famous Hotjar, Crazyegg, etc. thanks to its simple and intuitive operation.

Yesterday, however, an email arrived directly from Microsoft requesting the express “ping” towards Clarity of the user’s acceptance of cookies (statistical, profiling, technical… in short, those in which you have pigeonholed the software), under penalty of losing the ability to generate video recordings, funnels and custom events.

There is no actual roll out date but the email talks about “early 2025”.

At this point the question that arises is: what should I do to make Clarity work normally?

There are two ways to configure Clarity: via tag sequencing via GTM or via the Luratic template tag.

Clarity: GTM Tag Sequencing

To create the sequencing tag you need to create a Custom HTML Tag that contains the following code:

<script>
window.clarity('consent');
</script>

and subsequently, in the settings of the tag itself, activate the sequence and insert the standard Clarity tag (purified of any trigger) as the clean up tag.

This cHTML Tag will need to be triggered when the user accepts marketing cookies (at your discretion if it is launched with other cookies).

Once set, activate the GTM preview and test the acceptance and rejection of the cookie banner through the Developer Console > Applicaton > Cookies: if cookies are accepted, the _clck and _clsk cookies will appear and in the Developer Console > Network section, filtering by collect, you will find the call to Clarity.

If you refuse the cookie banner, neither cookies nor the “collect” call described above should be triggered.

Clarity: Luratic Tag

If instead of using the official Clarity tag you are using the Luratic tag, simply enter the wording “Consent Mode” in the “Privacy” field and it will automatically send the signals to Clarity (it is assumed that the Consent Mode is set correctly).