In your Settings & Members section, you’ll be able to manage everything you need from your dashboard. From inviting new members, crafting note templates, controlling Trackingplan’s digest, setting global warnings, and much more —all in one place.

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.

☝🏻

To better differentiate your standalone accounts, you can assign aliases to them, making it easier to identify which account corresponds to which GTMID or environment at a glance.

☝🏻

Learn more about how to split destinations by account ID.

Automatically disable newly detected destinations

If you only care about monitoring specific destinations (for example, a defined set of GA4 or Google Ads accounts), you can enable this setting to automatically disable any newly detected accounts.

When this option is enabled, only the destinations that already exist or were detected during Trackingplan’s Learning Phase remain active. Any destination discovered after that point will be automatically disabled by default, always ready to be re-enabled later if needed.

This means that newly detected accounts:

Will not appear in your Destinations sidebar.
Will not be included in your Digests.
Will remain hidden, but can always be enabled later if needed

This helps you keep your monitoring environment clean and focused, preventing unexpected or unknown accounts from adding noise to your setup.

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.

☝🏻

If these default tolerance levels do not meet your needs, you can always request custom tolerances tailored to your specific requirements. To enable this feature, simply contact our support team.

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”.

☝🏻

Important note: Before enabling Forbidden Properties, make sure that Trackingplan has fully completed its auto-training process and has learned your real traffic patterns.

If you activate this option too early, Trackingplan will assume that only the properties and destinations it has already seen are valid. This can lead to misleading warnings or missing data later on.

For example, if some destinations, events, or properties you care about haven’t received traffic yet and you enable Forbidden Properties before Trackingplan has detected them, those properties may later be treated as forbidden or may not appear as expected.

Best practice: Only activate this setting once your tracking has been stable for a while and Trackingplan has observed traffic across all relevant events, properties, and destinations.

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.

🤔

Learn more about all the errors and updates that Trackingplan notifies you about.

Digests & Notifications

The Digests & Notifications section helps you keep your team informed and proactive through automated email summaries and real-time alerts. From high-level overviews to highly targeted updates, you can control what information is sent, to whom, and when, directly from your settings.

Within this section, you can configure the following options:

Regular Digests

Regular Digests allow you to send automated daily or weekly summaries to keep your team aligned on tracking activity and potential issues.

From the settings, you can:

Enable or disable daily and weekly digests.
Define who receives them by adding one email address per line.

This is ideal for teams that want a consistent overview without needing to log into the platform every day.

🤔

Learn more about Trackingplan’s Digests.

Personalized Digests

Personalized Digests let you go one step further by ensuring that 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.

Using personalized digests, you can:

Create custom digests based on specific criteria.
Send focused insights to different teams or roles.
Reduce noise for large organizations with multiple stakeholders.

🤔

Learn more about Trackingplan’s Personalized Digests.

Real-Time Notifications

In addition to digests, you can enable real-time notifications to be alerted immediately when critical tracking issues occur.

These notifications help you:

React quickly to breaking changes.
Detect critical errors as soon as they happen.
Avoid waiting for the next digest to take action.

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.

🤔

Learn more about how to use Trackingplan's Notes Templates to optimize team collaboration.

AI Features

The AI Features section in Settings is where you can enable or disable Trackingplan’s AI-powered functionalities.

☝🏻

Trackingplan AI runs on Amazon Web Services (like the rest of the platform), and the data never leaves its premises, nor is it shared with model providers or used for training.

Trackingplan AI features only use the minimal data needed and don't use any personal information. The AI Debugger only sends warning information, its appearance history, and correlation data.

Yet, while all AI features are disabled by default and are opt-in, we recommend reviewing the updated Data Processing Agreement (DPA) you have signed with Trackingplan to ensure it aligns with your company’s data and privacy policies.

For more information, contact Trackingplan Support if you need a permanent, non-switchable ban of AI features for your plan, or refer to our Privacy & Security documentation to learn more about how Trackingplan handles data, security, and compliance across the platform.

Warning Analysis Instructions

Within the AI Features settings, you can also configure instructions for the AI agent used in Warning Analysis.

These instructions let you adjust how AI-generated explanations are written to better fit your team’s context and way of working.

For example, you can:

Add specific context about your plan (e.g. the data layer is not relevant for us).
Define the language of the responses (e.g. answer in Spanish, use French for all explanations…).
Ask for a specific tone or level of detail (e.g. be less technical or explain it as if you were talking to a digital analyst who is short on time, give actionable recommendations only, skip background details, summarize explanations in bullet points for quick reading).

These instructions will be automatically included in the AI Warning Analysis prompts, allowing the AI agent to adapt its explanations as closely as possible to your needs.

👇🏻

Learn more about Trackingplan AI Debugger in the video below.

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.

🤔

Learn more about sharing.

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).

User Account

Trackingplan also includes optional support for Two-Factor Authentication (2FA) to add an extra layer of security to user accounts during login.

While 2FA is disabled by default, each user can enable it individually from their Settings under User Account.

You can choose between the following verification methods:

Email verification code: Receive a code by email when signing in.
Authenticator app: Use any compatible authentication app (Google Authenticator, Authy, etc.) to generate time-based verification codes.

🛠

Want us to set 2FA up for your whole team? Contact support.

← Previous

Change History

Destinations