What is Trackingplan

Overview

The Trackingplan Way

Automonitoring

EventsPropertiesUser AttributesPagesAcquisitionPlatform Metrics

Automated Alert System

Warnings & UpdatesPixel MonitoringPrivacy MonitoringNaming Conventions MonitoringDiscover ReleasesData ValidationDigests

Getting Started

Installing Trackingplan

For WebsitesWebhooksFor AppsFor ssGTM

Post-Install Warm-Up

Inside Trackingplan

Dashboard

SearchHealth SummaryStarred ItemsReports

Data ExplorerTracks ExplorerRoot Cause AnalysisPresence MapAdvanced ReportsSession Finder

Privacy ReportChange HistorySettings & Members

Destinations

How to…

Manage Warnings

Mute WarningsDebug WarningsAttributionCustomize Warnings

Ensure Privacy

Privacy Report

Cookies & ConsentConsent Mode Privacy by Design

Marketing Observability

Campaign ValidationPixels Summary

Enhance Collaboration

SharingNotes & LabelsPersonalized Digests

Extend detection

TagsChrome ExtensionData Layer Audit Explore your DataEnvironments

Multi-Account Management

Plans OverviewJSON Export/ImportSplit Destinations

Others

Google Spreadsheet App

Looker Studio Connector

Omnibug Extension

Trackingplan Public API

Supported Trackers

SDK Update

Release Notes

Privacy and Security

Settings & Members

Destinations

Destinations are third-party services to which you send your event data, such as Google Analytics, Amplitude, or Mixpanel. Trackingplan automatically detects all the destinations you’re sending your data to, without the need to add them manually.

In the Destinations section in your settings, you’ll be able to enable or disable them according to your preferences.

Moreover, you’ll also be able to view and individually manage your ID accounts, grouping them under a single destination, making them function independently, or disabling them to prevent traffic from reaching your dashboard.

Warnings

In this section, you’ll be able to configure global parameters, fine-tune how and when warnings are triggered, and customize validations depending on your tracking needs.

Event Warnings

Here is where you’ll see your tracking plan’s global settings and make changes to your current configuration as needed.

Trackingplan provides customizable traffic warning tolerances for Traffic Drops and Traffic Peaks using the following levels:

• Low (Strict): By setting a low tolerance, warnings will be triggered at the slightest variation, making it ideal for monitoring critical events.
• Medium (Default): Offers balanced monitoring, reducing the risk of false positives while maintaining reliable alerts.
• High (Lenient): By setting a high tolerance, warnings will only be triggered in extreme cases, minimizing disruptions. Ideal for less critical events, such as optional user interactions, where variations are less significant.

These warnings and tolerances can be set globally, per event, or for acquisition dimensions (e.g., campaigns, landings, etc.). Just navigate to it and click on “Customize Warnings”.

Destination Warnings

Trackingplan automatically implements a first set of validation functions to verify certain values and their limits in Google Analytics.

These Google Analytics Implementation Warnings will be activated automatically whenever Trackingplan detects hits for that provider, but they are also customizable, allowing you to disable them through your settings at any time.

Digests

Digests are automated email summaries designed to keep your team aligned and proactive. Whether you need a quick daily overview, a comprehensive weekly report, or a custom digest tailored to each team, you can ensure the right people always receive the right insights at the right time.

Regular Digests

The Regular Digests section in your settings lets you enable or disable daily and weekly summaries according to your team's needs. Here, you can also specify exactly who should receive these digests by entering their email addresses — simply add one email per line.

Personalized Digests

The Personalized Digests section in your settings is where you can set up personalized digests to ensure only the right information goes to the right people. This is ideal for large teams or different stakeholders who need focused insights without the noise.

Templates

With Trackingplan’s notes templates, you can define the parameters that are required when filling out any of your event or property descriptions.

For it, just edit the template with all the elements needed to foster the understanding of all the different teams involved in the data collection process and save the changes.

Team Members

The Team Members Settings section allows you to effortlessly add new team members and allocate their roles and permissions within your Trackingplan account.

These are the user roles that specify different permission levels in your Trackingplan account:

• Admin: Allows team members to make changes to the workspace settings and preferences, invite new members, and edit the tracking plan. Admins are also the only members who can remove other members from the team.
• Editor: Allows team members to make edits to the tracking plan but does not allow them to edit the workspace settings and preferences. Editors cannot invite new members to the workspace.
• Viewer: Allows team members to view the tracking plan only. They can’t make any edits or invite new members.

Sharing

In the Sharing section of your Settings menu, you can choose to show or hide daily hits and property samples from users who access your tracking plan through a shared permalink.

Plan ID

When you have multiple tracking plans in your account, it’s important to quickly identify and organize them. You can do this by using aliases and groups.

Plan Alias

If you have multiple tracking plans in your account, aliases allow you to assign a custom, easy-to-recognize name to each of your dashboards. You can add or edit an alias for each one in your Settings menu.

Groups

On the other hand, groups allow you to organize multiple plans under a common category, helping you keep all your plans tidy within your Plans Overview. For agencies, groups are especially useful to separate and organize tracking plans by client, or by business sectors such as retail, healthcare, or others. For example, you could have a group named MyShop that contains all related alias plans (MyShop APP, MyShop WEB), clearly distinguishing them from plans belonging to other clients or projects.

Here are some examples:

• By vertical: For example, by industry sector such as “eCommerce” or “Media”.
• By client: Group plans by specific clients (e.g., Zalando's Android, Zalando Web).
• By team or analyst: Organize plans by team members in charge (e.g., Kate’s or Mike’s plans).