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.

Real-Time Visibility without SQL knowledge

Trackingplan’s Tracks Explorer allows you to see all your tracks in raw, parsed, and DataLayer format without downloading them, allowing you to see which tracks have been sent to your servers and analytics providers. Moreover, the Cookies & Consent tab lets you monitor how cookies and user consent settings affect the data being collected.

To access Trackingplan’s Tracks Explorer, go to the Reports section in your dashboard.

By clicking on it, you’ll be able to access a list of all tracks and sessions generated in your websites and apps, sorted by date. In it, all the data collected during a real user journey 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. You’ll find it in the top right corner of your Tracks Explorer view.

☝🏻

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 exploring your data.

Here are some possibilities:

Tracks vs. Sessions: View your data either as individual tracks or as unique sessions. Useful to gain additional context about each session and be provided with a more complete understanding of user behavior to make it easier to identify potential tracking issues in a broader context.

Pin sessions to a specific day, making it easier to analyze user behavior on a given date.

Use Trackingplan’s Event Selector to search for sessions where specific events have occurred. This would allow you to search for sessions where the purchase event has occurred across GA4, Adobe Analytics, Bing, and Meta—all in the same view, catching issues early and avoiding wasting ad spend due to missing or broken events.

☝🏻

Need to go broad? You can also select all events or filter by a specific source (e.g., “all events from Meta”) to get a complete overview of all the tracks generated by that provider.

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 or isolate your own session to distinguish your events from other hits being collected. Perfect for debugging, validating implementations, or simply following a specific user journey through your different destinations.
Customize your Tracks Explorer view by adding extra columns to see exactly the data that matters most to you. From Attributions, to UTMs, Consent Options, Properties, Tags, DataLayer, Query String, or Post Payload values, this allows you to create multiple columns in your Tracks Explorer view, making it easy to analyze data across various parameters simultaneously.

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.

Refining your searches

To make your analysis easier in Tracks Explorer, use Command + click (on Mac) or Ctrl + click (on Windows) to open any session in a new tab. This is helpful to view multiple sessions simultaneously without losing the context of the main view, compare sessions side by side to identify patterns or discrepancies, and perform deeper analysis without interrupting your current workflow.

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: Trackingplan’s Advanced conditions also allow you to 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.

However, to avoid manually entering conditions, you can also apply filters directly by selecting any element in your Tracks Explorer view.

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.

☝🏻

Finally, by clicking this button, you’ll be able to collapse the side search panel, maximizing horizontal space and reducing visual clutter. This allows you to focus more effectively on your analysis.

In-Depth Session Data

Trackingplan’s Tracks Explorer provides a detailed, session-level view of all tracked events. By clicking on any specific track, a side panel opens to reveal comprehensive technical information organized into tabs. This allows you to debug issues, validate data, and investigate tracking behavior deeply—without needing to open a browser console, run scripts manually, or download external files.

Properties Tab

This is your command center for validating context. Here, you can confirm that user and device information is correctly captured and that events contain the expected attributes. It’s especially useful for QA, debugging, and auditing tracking setups.

Let’s see it in more detail:

Properties

Displays all metadata associated with the event, including session ID, session count, and other relevant context. This ensures that key identifiers and custom properties are being sent correctly.

Data Layer

If you use GTM, Tealium, or other tag managers, this tab shows the exact data pulled from your data layer at the moment the event fired. This helps validate that variables are being correctly populated and passed to your analytics SDK.

Attributions

Trackingplan supports a broad range of attributions. This tab allows you to correlate events with user paths, geographic locations, browser types, devices, marketing campaigns, or even specific GTM releases. It helps identify patterns, segmentation issues, or tracking gaps.

Learn more about Trackingplan attribution here.

Tags

Shows internal Trackingplan tags used to classify and filter tracks. Tags can indicate the type of event, its origin, or any custom categorization you’ve set up, which simplifies filtering and troubleshooting.

Learn more about tags here.

Request Tab

The Request Tab gives a developer-focused, "under-the-hood" view of the communication between your SDK and the server. It’s essential for debugging network requests and ensuring payloads match your specifications.

Here’s all you can see in it:

Request

Displays all details of the HTTP request sent by the SDK, including headers, endpoint, and request type. This helps verify that events are being sent correctly and to the right environment.

DataLayer Array

Shows the complete state of your DataLayer at the time the event was fired. Use this to confirm that all expected variables were populated correctly and no values were missing or malformed.

Cookies

Lists all cookies present in the browser when the event is fired. This is critical for debugging consent management, session tracking, and identifying potential cookie-related issues.

Raw Track

Displays the raw event payload exactly as sent by the SDK. This lets you check that all fields and values are present before any parsing or transformation occurs.

Parsed

Shows how Trackingplan interprets and parses the raw payload. Compare this with the raw track to ensure all properties are being mapped correctly.

Consent Tab

Check users’ consent status at the exact time the event was recorded. This tab gives you complete visibility into what consent data (if any) was detected when that track was recorded, along with which cookies were present in the browser at that moment.

These are the 3 common consent scenarios you may encounter:

Consent cookie detected, with accepted categories: This is the ideal and most common scenario when consent is properly managed.
Consent cookie not found in this request, but found in other tracks: Sometimes, the CMP may not be ready when the first events are sent — either because the user hasn’t interacted with the cookie banner yet, or the CMP took time to load.
Consent cookie not found in this request, nor any other track: If Trackingplan can’t find a consent cookie in any of the tracks from your site or session, it will display the following message: This could mean your CMP isn’t correctly implemented, isn’t firing for the environment you’re testing (e.g., staging), or that your CMP is not currently supported by Trackingplan.

Learn more about Cookies and Consent here.

Warnings Tab

In this tab, you’ll 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.

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.

☝🏻

By opening a track from the list, the arrow icon next to it will turn grey, making it easier to identify which tracks you’ve already explored. Moreover, the last opened track will keep the hover highlight in green.

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

What is Trackingplan

The Trackingplan Way

Automated Alert System

Warnings & Updates

Pixel Monitoring

Privacy Monitoring

Naming Conventions Monitoring

Discover Releases

Data Validation

Digests

Getting Started

Installing Trackingplan

Inside Trackingplan

How to…

Marketing Observability

Campaign Validation

Pixels Summary

Enhance Collaboration

Multi-Account Management

Plans Overview

JSON Export/Import

Split Destinations

Others

Looker Studio Connector

Omnibug Extension

Trackingplan Public API

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.

Real-Time Visibility without SQL knowledge

To access Trackingplan’s Tracks Explorer, go to the Reports section in your dashboard.

☝🏻

👇🏻

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

Finding Your Own Session

☝🏻

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.

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

💡

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

Personalizing your Tracks Explorer View

Here are some possibilities:

Tracks vs. Sessions: View your data either as individual tracks or as unique sessions. Useful to gain additional context about each session and be provided with a more complete understanding of user behavior to make it easier to identify potential tracking issues in a broader context.

Pin sessions to a specific day, making it easier to analyze user behavior on a given date.

Use Trackingplan’s Event Selector to search for sessions where specific events have occurred. This would allow you to search for sessions where the purchase event has occurred across GA4, Adobe Analytics, Bing, and Meta—all in the same view, catching issues early and avoiding wasting ad spend due to missing or broken events.

☝🏻

Need to go broad? You can also select all events or filter by a specific source (e.g., “all events from Meta”) to get a complete overview of all the tracks generated by that provider.

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 or isolate your own session to distinguish your events from other hits being collected. Perfect for debugging, validating implementations, or simply following a specific user journey through your different destinations.
Customize your Tracks Explorer view by adding extra columns to see exactly the data that matters most to you. From Attributions, to UTMs, Consent Options, Properties, Tags, DataLayer, Query String, or Post Payload values, this allows you to create multiple columns in your Tracks Explorer view, making it easy to analyze data across various parameters simultaneously.

☝🏻

Refining your searches

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.

☝🏻

However, to avoid manually entering conditions, you can also apply filters directly by selecting any element in your Tracks Explorer view.

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.

☝🏻

In-Depth Session Data

Properties Tab

Let’s see it in more detail:

Properties

Displays all metadata associated with the event, including session ID, session count, and other relevant context. This ensures that key identifiers and custom properties are being sent correctly.

Data Layer

Attributions

Learn more about Trackingplan attribution here.

Tags

Learn more about tags here.

Request Tab

Here’s all you can see in it:

Request

Displays all details of the HTTP request sent by the SDK, including headers, endpoint, and request type. This helps verify that events are being sent correctly and to the right environment.

DataLayer Array

Shows the complete state of your DataLayer at the time the event was fired. Use this to confirm that all expected variables were populated correctly and no values were missing or malformed.

Cookies

Lists all cookies present in the browser when the event is fired. This is critical for debugging consent management, session tracking, and identifying potential cookie-related issues.

Raw Track

Displays the raw event payload exactly as sent by the SDK. This lets you check that all fields and values are present before any parsing or transformation occurs.

Parsed

Shows how Trackingplan interprets and parses the raw payload. Compare this with the raw track to ensure all properties are being mapped correctly.

Consent Tab

These are the 3 common consent scenarios you may encounter:

Consent cookie detected, with accepted categories: This is the ideal and most common scenario when consent is properly managed.
Consent cookie not found in this request, but found in other tracks: Sometimes, the CMP may not be ready when the first events are sent — either because the user hasn’t interacted with the cookie banner yet, or the CMP took time to load.
Consent cookie not found in this request, nor any other track: If Trackingplan can’t find a consent cookie in any of the tracks from your site or session, it will display the following message: This could mean your CMP isn’t correctly implemented, isn’t firing for the environment you’re testing (e.g., staging), or that your CMP is not currently supported by Trackingplan.

Learn more about Cookies and Consent here.

Warnings Tab

☝🏻

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

Root Cause Analysis