Learn how Trackingplan now reveals correlations between missing properties, events, and conditions—even when no warnings are triggered.
In Trackingplan, properties are inferred automatically—both their types and their presence, alerting you if a required property is missing.
Until now, you’ve always had the option to click Trackingplan’s Debug Warning to uncover correlated issues. Yet, exploring this correlation properly was not possible with those properties marked as optional, as no warning was triggered.
That’s why you can easily spot why an optional property isn’t always present and uncover patterns and relationships between properties, events, and page conditions—making debugging faster and more effective.
Happy tracking!
Transcript
hello in this video we'll dive into the find correlations feature in Trackingplan to explore how it can help you identify correlations where a property is missing so typically in Trackingplan properties are inferred automatically both their types and their presence alerting you if a property that is required is missing for example here Trackingplan is telling us that the market property which is set as required is missing in 73% of cases in the user info event until now you've always had the option to click on the warning to see its Evolution over time and click on tracking PL debug warning to uncover correlated issues for instance it might reveal that the missing Market property correlates with the language parameter in the data layer being set to English since when the parameter is set to Spanish the issue doesn't occur but what happens when a property is optional let's look at the card ID property in the user info event it's present 86% of the time but since it isn't marked as required no warnings are triggered while you as a user could mark it as required so that tracking plans starts generating a warning the next day as new data comes in the thing is with it currently marked as optional you wouldn't be able to explore this correlation properly as no warning is triggered that's why now we can go to any property that isn't complete even if it's optional like this one and a new button called find correlations will appear what will this button do is find which other properties in the data layer the page or the event correlate with this issue we can see how this correlation finder allows us to apply any configuration it reminds us that we're in the user info event and it quickly tells us that this issue occurs when the domain isy brand.com let's see what this means if we filter by domain we clearly identify that the issue happens when the card ID property is missing in the user info event when the domain is my brand.com but it doesn't occur when the domain is shoes.com this makes perfect sense as the payment Gateway is on shoes.com and the website doesn't have it here we can see that out of 512 hits in the case of shoes.com the property has never been missing whereas in the case of my brand.com the property has always been missing so the system is telling you the cause of why this condition occurs by quickly identifying such patterns saving you hours of manual debugging the important thing here is when the clarification is high let's find another example here in the purchase event we noticed that the channel property is missing 38% of the time let's investigate it using our find correlations feature and we quickly see that this isn't arriving 100% of the time because analytics consent is denied and if we keep exploring we can see that in other values it's always present so it's as clear as day that the issue is related to the consent setting if you wouldd like to explore this feature further or have questions feel free to to reach out to our support team thanks for watching and happy tracking
