What is Trackingplan

Overview

The Trackingplan Way

Automonitoring

Events

Properties

User Attributes

Pages

Acquisition

Platform Metrics

Automated Alert System

Warnings & Updates

Pixel Monitoring

Privacy Monitoring

Naming Conventions Monitoring

Discover Releases

Data Validation

Digests

Getting Started

Installing Trackingplan

For Websites

Webhooks

For Apps

For ssGTM

Post-Install Warm-Up

Inside Trackingplan

Dashboard

Health Summary

Starred Items

Reports

Data Explorer

Tracks Explorer

Root Cause Analysis

Presence Map

Advanced Reports

Session Finder

Privacy Report

Change History

Settings & Members

Destinations

How to…

Manage Warnings

Mute Warnings

Debug Warnings

Attribution

Customize Warnings

Ensure Privacy

Privacy Report

Cookies & Consent

Consent Mode

Privacy by Design

Marketing Observability

Campaign Validation

Pixels Summary

Enhance Collaboration

Sharing

Notes & Labels

Personalized Digests

Extend detection

Tags

💡

You can extend Trackingplan's detection capabilities by adding tags to label your data.

Tags are completely customizable and can be extremely helpful to filter your warnings and perform root-cause analysis on them.

Here are some of the possibilities tags can offer you:

Filter warnings by tags

🤔

Where is this warning happening? Which warnings have appeared after releasing v.1.23? Has any warning appeared from the Verify_orders_list test?

This is what you can quickly answer using Trackingplan’s Tag Filter.

Tags will allow you to distinguish your warnings by their custom tag value. That way, you will be able to filter your warnings by their release version, their build number, the app version in which they appeared, or their Test Name in staging or preproduction environments to quickly check if your warnings are happening only in a specific test version or in several of them.

Debug warnings and perform root-cause analysis

Tags can also enable you to debug and perform root-cause analysis on your warnings.

For those warnings related to missed properties, or with properties that do not conform to the Regexes, validation functions, or data types you have specified, you can hover the cursor over these warnings to get a clear view of the correlation between a specific warning and the tags that may have influenced its appearance.

Moreover, our RCA feature gives you the option to filter by all your tags.

☝🏻

That way, if you are investigating an error with the property “device_type”, which has been set as required but has been missing in 24% of the hits, by filtering them by your tags you’ll be able to see that the property source, when its tag value is “web_US”, has influenced the appearance of the error 99% of the times compared to the rest of your tags.

Learn more about debugging analytics problems with Trackingplan here.

Breaking down event traffic

Lastly, tags also allow you to break down event hits by the values of your tags. This means you can break down the traffic of an event by country, or any other values that you have previously tagged (release version, build number, app version, test name, country, etc.).

You can learn more about Trackingplan’s Data Explorer here.

Set up tags with Trackingplan

Learn how to install tags in your websites here.
Learn how to install tags in your apps here.

← Previous

Extend detection

Chrome Extension