What is Trackingplan
Overview
The Trackingplan Way
Automonitoring
Events
Properties
User Attributes
Pages
Acquisition
Platform Metrics
Automated Alert System
Warnings & Updates
Consent and Cookie Monitoring
Pixel Monitoring
Privacy Monitoring
Naming Conventions Monitoring
Discover Releases
Data Validation
Deep Audits
Digests
Getting Started
Installing Trackingplan
For Websites
Webhooks
For Apps
For ssGTM
Post-Install Warm-Up
Inside Trackingplan
Dashboard
Search
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
AI Debugger
Attribution
Customize Warnings
Ensure Privacy
Marketing Observability
Enhance Collaboration
Extend detection
Ensure Privacy
<aside>
💡
</aside>
With features built to automate compliance, enforce consent rules, and minimize data exposure, here’s how Trackingplan simplifies the path to a secure, privacy-compliant data stack:
Trackingplan’s Privacy Report: Instantly Detect Sensitive Data Collection
Since Trackingplan automatically monitors all the data sent from your websites or apps to third-party integrations, if it detects potential privacy issues — like personal data being collected or shared without proper consent — you’ll be notified immediately.
Trackingplan’s Privacy Report offers a centralized view of all detected personal or security-sensitive data being sent to analytics and marketing platforms.
- Identify if private or sensitive data (e.g., emails, IPs, names) is being tracked.
- See which events, properties, or destinations are affected.
- Understand how this data was collected and where it’s going.
This proactive approach enables you to take immediate action before compliance issues arise, helping protect both your business and your users' trust.
<aside>
☝🏻
</aside>
Privacy SDK: Mask & Protect Sensitive Data at the Source
Trackingplan’s Privacy SDK masks sensitive information on the user’s device before it leaves the browser or app, helping teams implement privacy by design while maintaining full visibility into their tracking data.
PII masking is enabled by default in the SDK (e.g. usePrivacy: true), so customers do not need to activate a privacy mode or make configuration changes to protect sensitive fields. The default masking rules can be extended or customized to match specific use cases.
Here’s how it helps your team stay in control:
- Automatic masking of personal identifiers such as names, emails, phone numbers, and IP addresses.
- Protection at the source: private fields are masked on-device before data is sent to Trackingplan.
- No raw PII in Trackingplan: personal data is masked before it reaches our systems, logs, or dashboards.
- Data quality visibility without exposing personal data: teams can monitor and troubleshoot their tracking while keeping sensitive information protected.
This is especially useful for organizations that handle sensitive data or operate in regions with strict privacy requirements.
<aside>
💡
</aside>

<aside>
☝🏻
</aside>
Google’s Consent Mode & Trackingplan