# Properties Docs DocsProperties [All docs](/docs) What is Trackingplan - [Overview](/docs/overview) The Trackingplan Way - [Automonitoring](/docs/how-it-works) - [Events](/docs/events) - [Properties](/docs/properties) - [User Attributes](/docs/user-attributes) - [Pages](/docs/pages) - [Acquisition](/docs/acquisition) - [Platform Metrics](/docs/platform-metrics) - [Automated Alert System](/docs/automated-alert-system) - [Warnings & Updates](/docs/warning-and-updates) - [Consent and Cookie Monitoring](/docs/consent-and-cookie-monitoring) - [Pixel Monitoring](/docs/pixels-presence-monitoring) - [Privacy Monitoring](/docs/data-privacy-monitoring) - [Naming Conventions Monitoring](/docs/naming-conventions-monitoring) - [Discover Releases](/docs/autodiscover-releases) - [Data Validation](/docs/data-validation) - [Deep Audits](/docs/deep-audits) - [Digests](/docs/digests) Getting Started - [Installing Trackingplan](/docs/installing-trackingplan) - [For Websites](/docs/installing-trackingplan/installing-trackingplan-on-your-websites) - [Webhooks](/docs/installing-trackingplan/installing-trackingplan-using-webhooks) - [For Apps](/docs/installing-trackingplan/installing-trackingplan-in-your-apps) - [For ssGTM](/docs/installing-trackingplan/for-ssgtm) - [Post-Install Warm-Up](/docs/post-install-warm-up) Inside Trackingplan - [Dashboard](/docs/dashboard) - [Search](/docs/search) - [Health Summary](/docs/health-summary) - [Starred Items](/docs/starred-items) - [Reports](/docs/reports) - [Data Explorer](/docs/data-explorer) - [Tracks Explorer](/docs/tracks-explorer) - [Root Cause Analysis](/docs/root-cause-analysis) - [Presence Map](/docs/presence-map) - [Advanced Reports](/docs/advanced-reports) - [Session Finder](/docs/session-finder) - [Privacy Report](/docs/privacy-report) - [Change History](/docs/change-history) - [Settings & Members](/docs/settings) - [Destinations](/docs/destinations) How to… - [Manage Warnings](/docs/warning-management) - [Mute Warnings](/docs/mute-warnings) - [Debug Warnings](/docs/debug-warnings) - [AI Debugger](/docs/ai-debugger) - [Attribution](/docs/attribution) - [Customize Warnings](/docs/customize-warnings) - [Ensure Privacy](/docs/ensure-privacy) - [Cookies & Consent](/docs/cookies-consent) - [Consent Mode](/docs/googles-consent-mode) - [Privacy by Design](/docs/privacy-by-design) - [Marketing Observability](/docs/enhance-marketing-observability) - [Campaign Validation](/docs/campaign-validation) - [Pixels Summary](/docs/pixels-summary) - [Enhance Collaboration](/docs/enhance-collaboration) - [Sharing](/docs/sharing) - [Notes & Labels](/docs/notes-labels) - [Personalized Digests](/docs/personalized-digests) - [Extend detection](/docs/extend-trackingplans-detection-capabilities) - [Tags](/docs/tags) - [Chrome Extension](/docs/trackingplans-chrome-extension) - [Data Layer Audit](/docs/data-layer-audit) - [Explore your Data](/docs/explore-your-data) - [Environments](/docs/environments) - [Multi-Account Management](/docs/multi-account-management) - [Plans Overview](/docs/plans-overview) - [JSON Export/Import](/docs/export-import-json-schemas) - [Split Destinations](/docs/split-destinations) Others - [Data Studio Connector](/docs/trackingplan-connector-for-data-studio) - [Omnibug Extension](/docs/trackingplan-omnibug-extension) - [Trackingplan Export API](/docs/trackingplan-export-api) - [Trackingplan Exploration API](/docs/trackingplan-exploration-api) - [Supported Trackers](/docs/supported-trackers) - [SDK Update](/docs/sdk-update) - [Release Notes](/docs/release-notes) - [Privacy and Security](/docs/privacy-and-security) [The Trackingplan Way](/docs) Updated January 29, 2026 # Properties Automatically monitor your properties to be notified whenever these don’t conform to the values inferred by our algorithm or the ones you've specified. > Properties (parameters in GA4) are the metadata or the dimensions of an event. In other words, properties are the insights of each event and provide relevant information such as the time, the user, the place, or the device with which the action was performed. Properties help you organize and analyze your data more efficiently by clearly stating what type of data is. This is why Trackingplan automatically monitors them to notify you whenever your properties don’t conform to the values inferred by our algorithm or the ones you have specified. ![](/images/spr-fb42db9e-Screenshot_2024-04-03_at_16.37.png) ### Property Type Monitoring In this regard, while Trackingplan can automatically interpret which property type is being tracked, you can make as many manual adjustments as necessary and choose between *boolean, number, string, array, object, regex, enum,* or keep it unconstrained with *any.* If Trackingplan detects that the events sent do not conform to these specifications, a warning will be generated. ![](/images/spr-6e58e16d-Tooltip_-23.png) ### Property Presence Monitoring Moreover, Trackingplan will also interpret which property presence is being tracked, but you can easily make manual adjustments between *required*, *nullable*, *optional*, *forbidden*, and *conditional* as shown below. Let’s see this in more detail: ![](/images/spr-3e1b645c-Screenshot_2025-10-29_at_12.54.png) - **R****equired:** If required properties are not being tracked in each of your event hits, as we see in the example below, Trackingplan will automatically send you a warning. ![](/images/spr-59c21d78-Tooltip_-24.png) - **Nullable:** If you set a property as “Nullable”, this means that emitting a property without value will not be considered a missing property in warnings and statistics. However, Trackingplan will send you a warning in case there are missing hits. - **Optional:** Setting a property as “optional” means there may be events where these are present and others that are not. In that case, Trackingplan won’t send you a warning in case no hits are tracked in the properties you’ve marked as optional. - **Forbidden:** You can set a property as “forbidden” to indicate to your teammates that this property should not appear in a specific event. This approach helps maintain a clean and consistent tracking setup, avoiding unexpected data collection and unnecessary warnings. > 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. - **Conditional:** Setting a property as “conditional” can be very useful for events that occur on many different pages. In this sense, adding a conditional could allow us to differentiate between required and nullable within the very same property, depending on its value. Let’s think about an example to illustrate it. > For this, we’ll use the event ***page\_view***, which is usually triggered on many different pages. By using a conditional, we can modify the property ***page\_type*** and only set the ‘home page’ and the ‘checkout page’ as *required*, while leaving the rest as nullable. That way, Trackingplan will notify us only if there are missing hits on those pages you’ve marked as required, allowing you to be much more precise on your requirements. ![](/images/spr-a48ada50-div.modal-content_-9.png) > **Pro tip:** To help you stay compliant with [Google’s Consent Mode](https://developers.google.com/tag-platform/security/concepts/consent-mode), you can also use conditionals to ensure your properties are always required as long as their consent is granted. Learn more about [Google’s Consent Mode & Trackingplan](/docs/googles-consent-mode) here. ![](/images/spr-65765819-Screenshot_2024-05-10_at_16.10_1.png) ## Find Correlations for Missing Properties > With Trackingplan, you can easily identify correlations for any property that isn’t complete—even optional ones—helping you pinpoint where a property might be missing. To do so, just go to any property that isn’t arriving 100% of the time and click the **Find Correlations** button. ![](/images/spr-93730b25-Screenshot_2024-12-31_at_10.33.06_1_-1.png) What this button will do is find which other properties in the DataLayer, the page, or the event correlate with this issue. ![](/images/spr-a2a9d6d1-19648530-76e7-4e4d-a06f-f6791ad09b59.png) For all the juicy details and examples, give this video a watch: ## Mark Unintended Properties as Forbidden Suppose you only want a property to appear in 4 events, but Trackingplan shows it appearing in 11 events. 1. Go to the **Properties** tab. 2. Click on the specific property. Trackingplan will expand a list of all events where this property is present. ![](/images/spr-fc1efea5-643a5dbd-3f94-46c9-b408-76e168d62ccf.png) 3. Mark all events as **forbidden** except for the 4 events where the property is supposed to appear. ![](/images/spr-e81edefc-7a943316-f45f-4773-baea-a5ad04552f8d.webp) > This allows you to enforce strict property rules while still allowing the property where it’s intended. [← Previous**Events**](/docs/events) [Next →** User Attributes**](/docs/user-attributes) Was this useful? Write to [support@trackingplan.com](mailto:support@trackingplan.com) On this page 1. [*01*Find Correlations for Missing Properties](#find-correlations-for-missing-properties) 2. [*02*Mark Unintended Properties as Forbidden](#mark-unintended-properties-as-forbidden)