A data layer is a data structure on your site or app that holds the information you want to process and sends it to other applications, like a tag management system.

The information you can pass through a data layer includes user actions on your site, app, or portal, such as page views, scrolls, or clicks, and additional details like product IDs and prices or cart value.

A tag manager can read data from your data layer and use it for tags, triggers, and variables, just like it would use data from the page’s source code. Your analytics data gets enriched with a record of all user behaviors, increasing opportunities for website or web-based application tracking.

With a data layer, you can:

  • Enhance your tracking capabilities.
  • Act on the data stored in a data layer to improve user experience.
  • Collect data in post-login areas.
  • Establish communication between the website or app with other tools like tag manager or analytics.
  • Benefit from a simpler debugging process.
  • Easily test changes or new features.
  • Simplify the execution of custom event tracking.
  • Facilitate personalization campaigns.

Learn more about data layers in analytics:


  • PHI and PII

    HIPAA violations and fines: What healthcare organizations need to know

    Quick summary HIPAA violations happen when a covered entity or business associate fails to meet the HIPAA Privacy, Security or Breach Notification Rule. Civil penalties range from a few hundred dollars to more than $2 million per violation, set across four tiers based on how much the organization knew.  What this guide covers: HIPAA violation…

  • The EDPB’s new data anonymization guidelines: what they mean for your analytics data

    Removing names, cookies and IP addresses is no longer enough to anonymize data. Here’s what the 2026 EDPB framework actually requires for anonymous data collection, what’s still unresolved, and how to configure your analytics to stay compliant while keeping the full view of traffic marketers rely on.