Tracks Explorer

Trackingplan’s Tracks Explorer offers a comprehensive view of user sessions, allowing you to track and analyze each of your events throughout a user journey or session.

Real-Time Visibility without SQL knowledge

Trackingplan’s Tracks Explorer allows you to see all your tracks in raw, parsed, and data layer format without downloading them, allowing you to see in real-time which tracks have been sent to your servers and analytics providers.

By clicking on it, you’ll be able to access a list of all tracks generated in your websites and apps, sorted by date. In it, all the data collected during a real session can be explored and the behavior of the data can be studied without requiring the reproduction of the error or the user's environment (language, browser, device, etc...).

☝🏻

This is particularly useful for troubleshooting issues, as it allows you to Identify and resolve issues by reproducing the exact sequence of user actions that led to an error. Learn more about Trackingplan’s wide array of attributions designed to pinpoint where errors compromising the quality of your data have occurred, understand why they happened, and take the necessary steps to resolve them.

Moreover, you also can search for sessions where specific events or properties have occurred (e.g.: sessions where the 'purchase' event has occurred, or search for sessions with specific property values like "purchase ID XXX").

Additionally, Trackingplan’s Tracks Explorer allows you to filter by specific days, destinations, events, session ID, or status, providing you with maximum customization for viewing all your tracks.

For instance, by filtering by status –especially by searching only for tracks with warnings–, you can easily focus and explore tracks that have not passed the validation check.

Additionally, you can filter by advanced conditions to refine your searches further.

☝🏻

Pro Tip: By using the advanced conditions menu, you can swiftly pinpoint specific consent actions, such as those where consent has been denied or is unknown, to facilitate proactive management and compliance with Google’s Consent Mode parameters. This is particularly useful for monitoring user consent actions and other critical events, ensuring compliance with data policies. Learn more about Google’s Consent Mode & Trackingplan here.

In-Depth Session Data

Trackingplan's Tracks Explorer provides detailed data about the entire user session, including browser information, device details, user behavior context, and more. This allows for a deep understanding of how data flows through your tracking setup.

Simply click on any session to access the raw, parsed, and data layer tracks in JSON format. This data can be copied and pasted without needing to download any file, making it easy to share or further analyze your tracks.

There, you’ll also find additional information about the warnings found in each of your tracks, allowing you to easily identify specification mismatches such as missing required parameters or incorrect data formats.

You can also access this information by hovering over the track status within this same view. This is useful for viewing mismatches while keeping the track content visible, allowing for a more streamlined review process.

Additionally, the same tooltip can be accessed by hovering over the warning icons within your tracks list. This will provide you with all the spec mismatches found, even those that haven’t triggered warnings because they fall within the allowed tolerances. This helps you address potential issues proactively before they escalate into real tracking errors.

☝🏻

Remember you can always review and fine-tune your warning tolerances in your settings.

Lastly, for easy identification, tracks with warnings that have not been triggered event-level issues will be marked in grey, making it easy to distinguish them from those with event warnings.

You also have the option to view tracks within your Debug Warning View or in Trackingplan’s Data Explorer.

🛠️

If you do not see sessions inside Trackingplan’s Tracks Explorer, it may be because you need to update the SDK. For more information, contact us here.

← Previous

Health Summary

Pixels