Notes & Labels

To help teams across departments adopt accessible and easy-to-understand definitions for all the members involved in the data collection process, Trackingplan’s customized notes allow you to add descriptions and labels on your events, properties, and acquisition data to ensure everybody clearly understands all the necessary details.

Notes

Trackingplan allows you to add customized notes and labels to overcome the not-so-easy challenge of seamless communication between different organizational divisions.

Moreover, if you need to write a longer description for a specific event, you can click on the icon shown above to expand all the information (right column) and edit it from there (left column) using Markdown formatting.

Trackingplan’s Notes Templates

💡

Trackingplan's Notes Templates are specifically created to help you define and establish efficient tracking and consistent annotation of data-related procedures and decisions, powering seamless collaboration across the various teams within an organization. You can think of these Templates as “your specialized stationery for data-centric dialogue”.

To create Trackingplan’s Notes Templates, just go to Settings & Members and click on “edit template” to add all the elements needed to foster the understanding of all the different teams involved in the data collection process. Don’t forget to save the changes.

From that moment on, your template will appear in your notes section, where you will be able to edit it from there.

🔎

Deep dive into Trackingplan's Notes Templates by seeing its practical use with some real-life examples here.

#labels

Moreover, Tackingplan’s notes section also supports #labels, which can be used to create categories to easily search them in the Advanced Search Filter (#P0, #purchasefunnel #onboarding), or even create Personalized Digests to ensure every department is aware of its responsibilities and encourage the ownership of every squad in the analytics generated by their developments.

In this sense, you could create personalized digests with the label #BUG that, for instance, only developers would receive, create tailored digests for each of your teams and departments, etc. While the possibilities are endless, let’s see some useful examples:

#BUG: Use this label to easily spot in your searches bugs that are currently reported.
#TEAM: Use this label to ensure every department is aware of its responsibilities for seamless collaboration across all teams (#DEV, #PRODUCT, #MKT), or squads (development teams) to encourage the ownership of the analytics generated by their developments.
#ECOMMERCE: You can use this label to define events belonging to the same funnel or critical path.

🔎

Learn more about personalized digests here.

← Previous

Personalized Digests