Term | Definition |
Tag Monitor | A component of Code Cube that monitors your website’s tags (client-side and server-side) in real-time, alerts you when they fail, fire too late, or don’t fire at all. |
DataLayer Guard | A module that monitors your frontend datalayer (or simulates one if none exists) and validates every event, parameter and value to ensure data quality across sessions. |
Tag | A snippet of code (e.g., for analytics, marketing, tracking) embedded on your website that triggers certain operations or data collection. (implicitly described by Tag Monitor) |
dataLayer | A JavaScript object/array on your website that holds structured data (user actions, page metadata, transactions) which tags or other tools read. |
Alert | A notification sent by Code Cube when an anomaly is detected (e.g., tag failure, volume drop or invalid data in dataLayer) so you can remediate quickly. |
Anomaly detection | The capability (within Tag Monitor) to learn usual tag behaviour (volume, patterns) and detect deviations beyond static thresholds. |
Measurement plan | A documented specification of your tracking/dataLayer setup (events, parameters) that ensures consistent implementation and can be auto-generated/validated by DataLayer Guard. |
Real-time monitoring | Continuous or near-instant inspection of tags/dataLayer as users interact with your website, enabling fast detection of issues. |
Client-side / Server-side tagging | Client-side: tags executing in the user’s browser; Server-side: tags or events processed on a backend server container. Tag Monitor supports both. |
Validation / QA (Quality Assurance) | The process of checking that your data collection, tags and dataLayer are implemented correctly, without manual effort, often automated by Code Cube. |