Getting started

How to use

Features

Other

Hi planner!

Here is where you can stay tuned for all the new features and improvements at Trackingplan so that you can squeeze the most out of our solution.

Missing something? What other functionalities would you include? We would love to hear your thoughts to help us improve.

Your feedback makes us better.

If you used to struggle to find the root cause of those warnings related to properties missing or not conforming to the validation rules specified, we’ve got you.

Our new Debug Warning View has been designed to provide you with key insights about the correlation between the detected warning and your tags, properties, and attributions.

By default, the value with the greatest potential influence found in the correlation between these values and the warning will be displayed on top. That way, if you are investigating an error with the property “device_type”, which has been set as required but has been missing in 24% of the hits, you will easily see that this property, when its value is “web-mobile”, has influenced the appearance of the error 91.27% of the time compared to the values “web-pc” and “app-commerce”, that have generated 0 errors.

Yet, if you haven’t decided which property you want to investigate, the default screen will show you the values that correlate the most with all your event elements.

With Trackingplan you can now create custom events by filtering them from the data of your existing events to track and validate them with more granularity (e.g.: create a custom event called premium_user_search to follow the search event closely when it is triggered by a user of premium segmentation).

This way, once Trackingplan starts detecting hits that correspond to the premium_user_search event, you’ll be able to monitor its behavior directly from your Trackingplan’s dashboard.

And you’ll be able to add it to your starred items list, customize its warnings to adjust it to your specs, create validation rules, or view it through your Daily Digest like any of your other standard events!

Spotting the regressions found in your test cases and your baselines is now easier with our Page Diff module.

Yes, you read it right: our Page Diff will provide you with precise information about the specific pages on which Trackingplan has spotted extra or missing hits to know where the problem needs to be solved without changing your current tests. Exactly, just plug & play 👇

Ready to try it out? Contact us to get Trackingplan’s Regression Testing module and easily spot where your warnings are located with our Page Diff feature.

And speaking of regressions… after comparing a test session or a specific test case with any of its compatible baselines and seeing that some regressions have been found between them, you’ll need some meaningful contextual information to fix those errors before compromising your data.

And once again, Trackingplan has you covered.

Trackingplan’s Request Log provides you with key information about all the tracks generated throughout a session to get all the necessary details to analyze and debug them locally.

Just contact us for more details to try it out.

To ensure your user attributes are sent to your data repositories in the expected format, Trackingplan now allows you to set up the data type to which your user attributes should conform, including Enums and Regexes!

If Trackingplan detects any inconsistencies, we will automatically send you a warning.

Effective communication is key, especially if you want to avoid all these little misunderstanding gaps that usually lead to implementation bugs 🐛

With Trackingplan's Notes Template, you can define the parameters required when filling out event descriptions.

We understand the challenges posed by variations in characters and accents. To ensure seamless recognition by the server, Trackingplan now offers the option to ignore cases and diacritics in your Regexes and Enums to prevent potential issues where the server might identify them as implementation problems.

Now, Trackingplan lets you validate your properties with Enums!

Enums will allow you to specify in advance the values you expect for a property. That way, if it receives a value that does not conform to the list of predefined constants you have specified, we will automatically send you a warning.

The best thing? You can even autocomplete an Enum with the values that have been observed in a property for the last 30 days. As a result, you’ll just need to check that all the values are correct and, in case they’re not, edit or delete them.

Easy, huh?

To learn more about how to validate property values with Enums, click here.

Now picking test sessions and knowing their compatible baselines with Trackingplan’s regression testing module is easier than ever.

Our new view allows you to see all your tests and baselines at a glance without having to wait for your tests to load. Moreover, after selecting a test, you’ll be able to instantly see the baselines you can compare them with.

But that’s not all! We’ve also implemented the option to filter your tests and baselines to spot them quickly.

Ready to try it out? Click here for more details.

Now you can also visualize Trackingplan’s Histogram of Property Values in your properties tab. This will give you easy access to the most frequent values a property has received across events.

To see it, just click on the small button shown below 👇

Trackingplan’s regression testing module allows you to validate that the analytics performed in each test session match the expected baseline and, in case it's not, understand why.

The help you need to…

Import the specifications of your tracking plan into your own dashboards, connect it to Notion, add it to Google Sheets… - you asked for it; we got it!

The new Trackingplan’s API allows you to access your data and export it to use it however you want, wherever you want.

You can export your own plan in JSON or CSV format just by adding your TP_ID, your sharing token, and the environment of the plan you want to export (production, staging… you name it!).

To get access, contact us here and we’ll send you the link.

Looking for a tool to debug your analytics implementations in real-time directly on your websites?

Trackingplan’s Chrome Extension lets you do just that.

When used together with Trackingplan SDK, our brand-new extension can help you automatically find problems in your digital analytics:

Curious to try it out? Contact us here and we’ll immediately send you the link.

Do you need to quickly locate the root cause of your warnings to easily debug them? Now you can quickly do it with our Warning Tag Distribution report.

This will show you, for each warning, the value distribution of the tags you have. For instance, in the example below, you can see that the event Product_impression has observed a validation error which has been found in iOS_Portugal 100% of the time.

We never thought that moving the search bar to the top of our interface would bring so many possibilities. While this might sound insignificant, this will allow you to have a personalized warning history aligned with your searches!

That means that you will now have a single-event view with the warning history of any specific event or collection of them. All you need to help other members of your organization have a clear view of their status at a glance!

This is what you can now quickly answer using Trackingplan’s Tag Filter. Tags will allow you to distinguish your warnings by their custom tag value. That way, you can filter your warnings by their release version, their build number, the app version in which they appeared, or their Test Name in staging or preproduction environments among others.

Apart from knowing in which app version your warnings appear while ignoring older or outdated versions, if you run functional tests (e.g. Cypress tests), you can label them with tags to filter them by test name and quickly spot which one failed in your tracking plan.

Tags can also enable you to debug and perform root-cause analysis on your warnings.

All the tags set up in the SDK init call will be shown in your warnings samples. You will find them by hovering the cursor over the warning you want to tackle and clicking on the “See Samples” button.

This will allow you to find out where the error appeared (depending on which tag is used, its release version, the app version, its test name, or even its web module like blog/shop/news, etc.)

If you want to configure custom tags in your Trackingplan, contact us here.

Upon popular request, we started providing you with meaningful contextual information about where and why property specification errors happened by showing you a random sample of a payload that did not pass the validation. As we’ve seen this has significantly helped our users to debug their warnings, we’re now providing multiple of them!

You can download up to 7 warning samples of the tracks that generated your warnings. This way, if you’ve had a warning running for seven days or less, you can now download a sample for each of the days the warning has been running.

Inside the properties of an event, our brand-new Histogram of Property Values can help you visualize the most frequent values a property has received along with their frequency. To see it, just click on the small button shown below.

Need to see the Property Values of any specific day? We’ve got you!

Just click on any of the days shown in your daily hits graph to check if you are getting the expected values in a property on the day you’re interested.

To date, Trackingplan provided statistics about the results of your marketing investments by showing you detailed daily, weekly, and monthly of your UTM campaigns, mediums, sources, originating referrers, and landings.

Now, you can see the statistics of all your pages loaded by your users and track their daily, weekly, and monthly evolution. All you need to dig deeper into understanding your site’s traffic and quickly identify which pages are performing well and which ones can be improved!

The cherry on top? Now you can also set up warnings for all your referrers, campaigns, mediums, sources, landings, and pages. To do it, just hover the cursor over the items you want to track closely and click on Customize Warnings to configure them according to your specifications.

The tooltip now shows all the warnings this property has across events, and provides a link to jump to those events in which the property has issues.

Have you ever had the need to see all the warnings a property has across events?

Well, you needed it, you got it. We’ve just added a tooltip where you can quickly jump and see at a glance those events in which your properties have issues.

You can create new events and define the type and required constraints you expect from them with the Draft Event button you’ll find in the top right of your Dashboard.

Once an event appears for the first time, Trackingplan will automatically show it and will validate it according to the specification you had already set up, generating warnings if applicable. As long as no hits are detected, the event will appear as OFF.

We will also send you an alert once this event goes live in each of your environments, like staging or production, so that the person in charge of defining its specification can easily check if the dev team implemented the event correctly or vice versa. In case it’s not, you can immediately alert about the issue and get it fixed, instead of noticing when it’s too late and the data is missing.

Sounds good, huh?

For those who needed more space to write notes and labels on their events, we’ve heard you 👂

Now you can ensure your team members clearly understand all the necessary details with longer descriptions. Just click on the icon shown below to expand all the information (right column) and edit it from there (left column) using Markdown formatting.

Now you can run functional or non-functional regression testing with Cypress to stress your analytics under the watch of our system.

See how to install Trackingplan for different environments here.

Hurray! Now the information provided in our CSV will enable you to see not only the daily hits of your events, but also the properties and the specifications defined for each of them, such as their type and required constraints.

Now, knowing which environment you are looking at is now easier than ever. If you switch to an environment that is not a production one, the name of that environment will be shown in orange, as well as you will be able to see a stripe of the same color at the top of your interface.

Finding bugs and regressions in your analytics and tracking them automatically is great, but this does not avoid the emergence of problems and costs related to the data downtime between the bug and its fix are released. The classical solution to this is well-known in software development: shift-left testing. We perform functional and non-functional testing on our code before it is released, even before it is merged through unit, integration, and acceptance tests, among others. Why not do this for analytics and tracking too?

Trackingplan can now monitor your testing deployments and alert you about changes and specification errors introduced before you release the code. We leverage existing functional tests that stress your analytics and automatically create baselines. No need to write extra tests!

Please contact us to enable this feature and read more about it here.

We have added support for more analytics services and marketing attribution pixels, such as mParticle, TikTok, and Twitter. Missing yours? Let us know at support@trackingplan.com and we'll add it!

Reviewing and setting constraints among dozens of properties in hundreds of events takes time and is cumbersome. We found that property specifications, such as their type or whether they are required or not, are often shared across events or have a sensible default. To allow for such a bulk editing across events, you can now use the Properties and User Attributes tabs directly.

Your tracking plan loads up to 5x faster than before.

So far, event properties were validated based on their traffic, presence and type. A very popular request among our users has been to enable Enum and Regex-based validations. With this feature, you can now create your own rules and apply them to a selection of properties.

To date, we provided statistical information about your property specification errors. For example, how often the property name is not satisfying a set up regex when the event Page View fires. Upon popular request, we are now also providing a random sample of a payload that did not pass the validation in order to provide contextual debug information. In this example, you can download a sample Page View payload with an incorrect name registered through Segment.

Note that we are adding support for warning samples across all property specification errors.

Regexes are useful, but what if you are validating cross conditions and property prop1 is required only if property prop2 matches some value X… or even more complex scenarios? For this reason, we decided to add support for your own custom validation functions. These allow to inspect the payloads Trackingplan sees freely and log statistics about the validation results.

Please contact us to enable this feature.

Trackingplan’s Privacy Report allows you to see at a glance which private data your site is collecting from your users and forwarding to third parties.

Personal data – like user emails, IP addresses, SSNs, credit cards, and so on – will be automatically spotted and labeled here in order to detect possible privacy issues or security-sensitive data that should not have been collected or forwarded to your analytics services.

Traffic and property spec warnings appear on your tracking plan as things break, e.g. due to a new release, and they disappear just as fast when issues are fixed again. However, sometimes one needs to reflect upon issues indistinctly of whether they are already fixed or not, and possibly we need to report those fixes, work on reappearing issues, etc. All this is now possible with the new 30-day history of your plan.

All the changes your colleagues and you perform on your tracking plan can now be traced back. For example, this allows us to recall when and who changed a property spec or muted an event in order to ease working within teams on a plan or undo changes if necessary.

Change history can be retrieved at plan- or event-level using respectively the link on the sidebar or Event toolbar:

You know the deal… Copy/pasting has its limitations, so we added a button for you to export your tracking plan data and use it as you like.

We’ve made it easier to visualize the data you are sending to each destination, so that you may easily address questions like Are we sending the site id to Amplitude? To see which events are sending a specific property click on the # Events counter.

“All you need to know on a daily basis about your tracking in a single place.” That’s the mission of our Daily Digest feature. To get a couple steps closer to this goal we now inform you also about:

To help you get the level of detail you need from your analytics, we now provide daily, weekly and monthly growth statistics for your events.

Our User Acquisition feature now also tracks your landing pages and provides detailed growth statistics to help you understand how users arrive at your site.

Our Pixels feature that tracks all the 3rd-party integration you use on your site across pages is now available for all customers - just try it out and let us know if you are missing any integration you’d like to track!

Whenever a pixel is installed or removed from your site you will get a notification in your Health Summary:

How many pixels or trackers do we actually have on our site? On which pages are they triggering? Has the Facebook Ad Conversion Pixel been removed from this landing in the last release?...

These are the kind of questions our brand new Pixels view answers. It allows you to stay on top of all the SaaS tools used in your frontends and alerts you automatically when a Pixel is gone from a page of your site or is offline completely.

Note that as of now we are activating Pixels customer by customer. Talk to us to get it activated!

Trackingplan alerts you when errors are found in your events. In order to find the root cause of such traffic or data issues more easily, you can now see on which of your pages those events have triggered on. If the issue affects specific pages only, like the /login page in the example below, you can track down the team that is in charge of them and get it fixed.

You may have noticed that our daily Digest is providing more and more details. For example, we are now sending you daily, weekly and monthly statistics of your ⭐ starred events. Simply star the events you want to see in your tracking plan to receive them!

You now have two new ways of locating your data and see its traffic and specs. The fastest one is through the 🔍 Quick Find button where you can just start typing and find any section or piece of data in your tracking plan.

The second is built for those messy moments where one wants to find the needle in the haystack and has to answer questions like Which of my settings events are really tracking the site id?

Manually reviewing each of the new events and properties Trackingplan has detected on your site can be a tedious task if you have hundreds of events. To skip this step, we now infer the spec of each property automatically based on your traffic and start monitoring your events as soon as sufficient traffic has been observed. [See Demo]

Trackingplan provides automated alerts if your data or event statistics are off. You can now also customize these warnings for each event to better match your needs and apply tailored sensitivity levels. This includes setting a custom range of hits to detect scenarios that are relevant to your business. [See Demo]

Wouldn’t it be amazing to relate my user acquisition 👥 to each specific event? This way, I can link user behavior on my site to their actual origin, namely UTM campaigns, referrers, landings, etc., and dig deeper into understanding my site’s traffic. This is what we call the Attribution Report and it’s available for all of your tracking events if you are on JS SDK 1.9 or above (let us know if not, and we’ll help!). [See Demo]

Label your events and properties with #tags to create categories (e.g. #onboarding, #salesFunnel, #debug...) and find them quickly in our Search bar... you get the idea.

We added support for a dozen new analytics providers and Sales/Marketing integrations. New data destinations include Facebook Pixel, Pinterest, Heap and Snowplow among others. Missing yours? Let us know at support@trackingplan.com and we'll add it!

The latest version of our Trackingplan installation snippet for Websites includes support for further data destinations, advanced data capturing methods (Websockets and Beacon) and performance optimizations. Update it at https://panel.trackingplan.com/plans/<YOUR_TP_ID>/install.

Where do I get my users 👥 from? The new User Acquisition view answers this question providing detailed daily, weekly and monthly statistics about the results of your marketing investments. UTM campaigns, mediums, sources and originating referrers are supported, with more dimensions to come, such as country of origin or landing page.

It's now much easier to navigate the daily statistics of your events: Simply click on the graph to freeze on a specific date and click again to return to cursor-based navigation.

Santa 🎅 came early this year and Trackingplan got a fresh UI design with plenty of new features. The new Health Summary view stands out. It allows you to see and manage all recent activities and warnings of your tracking plan.

But there are also minor improvements, such as starring ⭐ your most important events.

Properties can now be set as required but allowing nulls. This means that emitting a property without value is not considered as a missing property in warnings and statistics.

Example values of your dynamic events now appear in a tooltip. Before they appeared as a property and that could be confusing.

On this page