What is Trackingplan
The Trackingplan Way
Getting Started
Dashboard
How to…
Others
Explore Tracks
By accessing it, you’ll be able to instantly view and analyze all tracked events sent to your servers and analytics providers in raw, parsed, and data layer formats, without the need for downloads.
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...).
Personalizing your Tracks Explorer View
Trackingplan’s Tracks Explorer allows you to filter by specific days, destinations, events, status, or session IDs, providing you with maximum customization for viewing all your tracks. Here are some possibilities:
- Pin sessions to a specific day, making it easier to analyze user behavior on a given date.
- Filter by tracks within specific destinations (GA4, Adobe Analytics, Meta, etc.)
- Search for sessions where specific events have occurred (e.g.: sessions where the 'purchase' event has occurred).
- Search only for tracks with warnings to focus on tracks that have not passed the validation check.
- Filter your tracks by a known session identifier.
- Customize your Tracks Explorer view by adding extra columns to see exactly the data that matters most to you.
This means that, in addition to the default columns, you can also choose from a wide range of attributions, UTMs, Consent Options, DataLayer values, and more. This is particularly useful for checking data persistence within the same session, ensuring fields like the ‘referrer’ stay consistent throughout a session, or for identifying changes in consent mode during user interactions.
Pro tip: By clicking on the Time column in your session view, you’ll be able to see it in timestamp format. This allows you to easily identify duplicate events or events captured simultaneously, providing a more precise view of your data.
Additionally, you can filter by advanced conditions to refine your searches further. This enables you to tailor your results based on specific criteria, helping you identify relevant tracks within your users’ sessions more efficiently. Let’s explore its possibilities:
- Equals (=): The "Equals" operator allows you to filter your tracks by an exact match. For example, if you want to find all tracks where the UTM Medium is exactly “cpc”, this operator ensures that only those are returned.
- Matches Regex: Useful for refining your search to a specific set of events or data attributes, or for comparing similar events across different providers to analyze consistency (e.g., 'Purchase' and 'CompletePayment').”
- Does not match Regex: Conversely, the "Does Not Match Regex" condition allows you to exclude specific events or data attributes from your Tracks Explorer view. For example, in the example below, we’ve been able to isolate an error within the purchase event, specifically, on the checkout page, where the system was failing to display the thank you page within the purchase flow.
After filtering according to your needs, simply click on any session from the list to access the raw, parsed, and data layer tracks displayed in JSON format, which you can copy and paste without downloading them.
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.
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.
← Previous
Next →