This glossary provides clear definitions of key terms used throughout our articles and documentation. It is designed to help readers—whether new or experienced—understand specific terminology, abbreviations, and concepts relevant to our work. Each entry includes a concise definition along with any relevant context to aid comprehension.
Written By metrion
Last updated 26 days ago
Term: Enhanced
Definition:
"Enhanced" refers to data events that are enriched with additional metadata or context before being processed or stored. These events typically contain structured properties that improve reporting accuracy, segmentation, and analysis.
Explanation:
Enhanced events go beyond basic data capture. They may include user identifiers, session details, attribution data, custom properties, or any contextual signals relevant to your product or business logic. This allows for more granular insights, targeted queries, and better integration with analytics or personalization systems.
Term: Untagged
Definition:
"Untagged" refers to raw data events that are collected without custom metadata or business-specific tagging. These events usually include only the default or minimal set of properties captured by the platform.
Explanation:
Untagged events are useful for basic tracking needs or for capturing broad behavioral patterns. However, they lack the depth required for advanced analytics. They can be seen as the foundational layer of data—still valuable, but less actionable without further enrichment or tagging strategies in place.
Term: Consented
Definition:
“Consented” refers to data events captured when a user has explicitly opted in to tracking.
Explanation:
Consented events include both the platform’s default properties and all metadata, since full data collection is allowed under your consent policy. This gives you access to complete user identifiers, session details, and any business-specific tags you’ve set up.
Term: Blocked
Definition:
“Blocked” refers to data events that are not captured because (1) the user denied tracking, (2) their browser denied tracking by default or (3) a third party ad blocker denied tracking.
Explanation:
Blocked events don’t reach your system at all with regular tracking methods. No user IDs, sessions, or custom fields. This happens whenever a user opts out or employs browser privacy tools.