Learn how to use Google Tag Manager Data Layer values to adapt when the Crisp chatbox appears.

When your website already exposes plan, pricing, account, or lifecycle data through the Data Layer, Google Tag Manager can use that context to decide which visitors should see Crisp or which custom script should run.

Before you start

This setup is useful when your website already knows who the visitor is, for example an authenticated user with a plan, role, lifecycle stage, or monthly spend. You can then reuse those attributes in Google Tag Manager without editing the Crisp code directly every time.

You will need:

• Crisp chatbox installed on your website
• Google Tag Manager installed on the same pages
• User attributes exposed in the Data Layer or available from your website code
• A clear rule for when Crisp should load, show, hide, or trigger a specific action

Expose useful values in the Data Layer

First, push the values you want Google Tag Manager to read. The example below exposes the visitor plan and price, but you can adapt the keys to match your own business data.

<script>
  window.dataLayer = window.dataLayer || [];

  window.dataLayer.push({
    typePlan: "Essentials",
    price: "95"
  });
</script>

Make these values dynamic in your production code. For example, typePlan should come from the authenticated user account, not from a static snippet copied into every page.

Create Google Tag Manager variables and triggers

Open the Variables section

In Google Tag Manager, open your container and go to Variables. This is where you will create variables that read the values pushed to the Data Layer.

Create a Data Layer variable

Scroll to User-defined Variables, create a new variable, and choose Data Layer Variable. Use the same key name you pushed earlier, such as typePlan or price.

Build a trigger from that variable

Create a trigger that uses your new variable as a condition. For example, you can fire a Crisp-related tag only when typePlan is not Free, or when price is higher than a threshold you define.

Connect the trigger to your Crisp setup

Once the trigger is ready, attach it to the tag that loads Crisp or to the custom script that controls Crisp behavior. Depending on your setup, this can be used to load the chatbox only for a specific audience, show it on selected pages, or trigger a custom action after the chatbox is loaded.

Before publishing, use Preview mode in Google Tag Manager to confirm that your Data Layer values are present and that your trigger fires only for the visitors you expect.

Updated on: 03/05/2026