Explore Raw Tracks | Trackingplan

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

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...).

Moreover, by clicking on Trackingplan’s Live Mode button, you’ll be able to see hits coming into your website and apps in real-time, getting a live view of your tracking data as it flows in.

☝🏻

This is particularly useful for reproducing the exact sequence of user actions that led to an error. Whether you’re an analyst validating data, a developer testing a new implementation, or troubleshooting tracking issues, Live Mode allows you to immediately see how each of your actions translates into hits as you interact with your site, identifying validation errors on the spot and diving into those tracks for deeper analysis.

👇🏻

For a detailed demonstration and practical examples, watch the following video:

Finding Your Own Session

☝🏻

While Live Mode provides a real-time view of incoming tracking data, if a website has high traffic, distinguishing your hits from thousands of others can be challenging. To simplify debugging, Trackingplan allows you to isolate your session to easily see how each of your actions translates into hits when testing new implementations or troubleshooting tracking issues.

Simply click on the "Find Your Own Session" button and enter the URL where you’ll be navigating. Then, click on “Create New Debug Session”.

☝🏻

If you've previously used this feature, you can quickly resume your last debug session instead of creating a new one.

Trackingplan will automatically generate a unique session ID for you and set your SDK into debug mode, with disabled sampling and batching turned off, to help you see every event exactly as it happens in real time.

As you browse, your session’s hits will appear instantly in Trackingplan’s Tracks Explorer.

💡

This functionality is particularly useful for developers implementing new features, analysts validating data accuracy, and anyone troubleshooting tracking issues. It works similarly to GTM’s debug session feature, providing a precise, session-specific view of tracking data.

For a detailed demonstration and practical examples, watch the following video:

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.

☝🏻

Pro Tip: By using Trackingplan’s Advanced conditions, 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.

💡

However, filtering conditions can be applied directly by selecting any element within your Tracks Explorer view, eliminating the need to manually enter conditions and reducing the risk of errors.

For example, to focus on page views, simply click on the button shown above to filter by this condition. Then, hit the Explore button again to refresh your view with the selected filters.

From there, you can continue refining your search—filtering by page to display only page views within the “pricing” page.

Or narrow it further to page views inside “pricing” from users browsing with Chrome. The possibilities are extensive, allowing for deeper insights with just a few clicks.

Filters will dynamically update in the Advanced Conditions fields as selections are made, ensuring a more interactive experience. This flexibility enables quick adjustments, such as adding, modifying, or removing conditions as needed.

In-Depth Session Data

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.

☝🏻

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

Data Explorer

Marketing Observability