Trackingplan’s Advanced Reports help you monitor, compare, and analyze your tracking data in detail, making it easier to detect irregularities, validate implementations, and ensure data reliability across destinations.

You’ll find them by navigating to the Reports section in Trackingplan’s sidebar.

There, you’ll find a dropdown listing all advanced reports available, each accompanied by a short explanation to help you understand what data it provides and in what context it's useful.

Once selected, the report will display in a table view, allowing you to explore and analyze all the data efficiently.

Duplicate Events Finder

This report helps identify potentially duplicated events by searching for user sessions where the same event appears several times in the same second. This can help you spot unintentional duplications, such as a “purchase” or “signup” event firing more than once per user interaction.

☝🏻

Use this report to detect events that are being triggered multiple times in the same second, a common symptom of double tracking or incorrect event implementations.

To start, simply select the specific date you want to investigate — for example, a date right after a release or a tag change. Trackingplan will automatically scan your event data and identify any cases where the same event was fired multiple times within a single second for the same user session, displaying a detailed table with the following columns:

Destination: The analytics or marketing platform where the duplicated event was recorded (e.g., Google Analytics 4, Meta Pixel, Segment, etc.).
Event Name: The name of the potentially duplicated event (purchase, signup, add_to_cart)…).
Affected Sessions: The number of unique user sessions where this event was fired multiple times in the same second. These are the sessions you may want to inspect more closely.
Total Sessions: The total number of sessions in which this event was recorded at least once, whether duplicated or not. This helps you understand the scale of the issue.
Duplicate %: Percentage of sessions with duplicates compared to total sessions. A higher percentage suggests a broader or recurring issue in your tracking setup.
Example Sessions: A list of specific session IDs where this duplication was detected. You can click or copy these IDs to explore them within Trackingplan’s Tracks Explorer for a closer look at what happened in each case.

Tips and Considerations

Some events naturally occur multiple times: Events like impression or scroll may naturally occur multiple times and might not indicate an issue.
Focus on transactional or one-time actions: Events like purchase, signup, or form_submit should typically happen only once per user interaction. If you see that the purchase event appears twice in one second for several sessions, it could mean the purchase confirmation page triggers the event on both page load and button click
Beware of false positives: Take into account that batched events can be a source of false positives. In some platforms (like GA4), events are sent in batches every few seconds. This can make multiple identical events appear to happen “in the same second,” even though they were collected separately.

Unique Session ID Comparison Report

This report helps you compare the total number of unique sessions recorded by Trackingplan versus other destinations (e.g., Google Analytics, Segment, Amplitude…).

☝🏻

Use it to identify potential issues with session tracking.

Once you’ve selected a timeframe, the report will display a detailed table with the following columns:

Destination: The analytics or marketing platform being compared (e.g., GA4, Amplitude, Segment).
Trackingplan Sessions: Total number of unique sessions detected by Trackingplan during the selected timeframe.
Provider Sessions: The number of unique sessions detected by each integrated provider.
Difference (%): The percentage difference between the number of unique session IDs tracked by Trackingplan and the number of unique session IDs tracked by each destination.

A positive difference indicates that the destination is tracking more sessions than Trackingplan.
A negative difference indicates that Trackingplan is tracking more sessions than the destination.

☝🏻

Normal variations (±10%) are usually expected due to timing differences or platform-specific definitions.

Example

Let’s say you compare sessions between Trackingplan and Google Analytics 4 for the last week and see the following:

Destination	Trackingplan Sessions	Provider Sessions	Difference (%)
GA4	48,000	57,600	+20%

How to interpret this:

GA4 is reporting 20% more sessions than Trackingplan. This might be due to differences in:

Session timeout duration (e.g., GA4 resets after 30 minutes of inactivity).
Event batching or deduplication settings.
A missing hit or an inconsistent session ID setup in your instrumentation.

On the other hand, if Trackingplan shows more sessions, it could mean:

Some hits have never reached the destination (network errors or tag misfires).
Your destination has applied filters or privacy settings that discard part of the traffic.

Consent Percentages Report

This report helps you verify whether your website or app correctly respects users’ consent preferences — for example, ensuring that no marketing, analytics, or personalization data is sent when users haven’t granted permission.

☝🏻

Use it to validate your Consent Management Platform (CMP) configuration and prevent accidental data collection that could violate privacy regulations, like GDPR or CCPA.

Once you access the Consent Percentages Report, you’ll see a panel on the left where you’ll be able to adjust the following parameters:

Date: Select a specific day to analyze, or a date range to spot trends over time and understand how consent evolves.

Consent Source (DataLayer, Finsweet, OneTrust, CookieYes, etc.)
Analyze consent by:

Overall: Provides a global overview of consent compliance across all categories.
By destination: Measures how often specific analytics or marketing platforms are triggered under each consent state.
By destination and event: Breaks it down further, showing how each (destination, event_name) pair behaves relative to consent.
By cookie / pixel / domain: Helps you analyze technical elements (cookies, pixels, or third-party domains) that may be active even when consent is not granted.
By contacted domain: Average distinct third-party domains contacted per page load

Group by (optional): Compare consent behavior by country, device, language, or any other attribution field to detect localized implementation differences (for example, “France vs. Germany” or “mobile vs. desktop”).
Enable experimental validation: While any value above 0% may deserve review, this feature helps you quickly identify what requires immediate attention and what is less urgent.

Activate it to apply automated assessment rules, and adjust the threshold percentage to align it with your internal consent standards.

Interpreting results

After adjusting these parameters to your needs, Trackingplan calculates the percentage of times consent was NOT GRANTED or NOT CONSENTED for each of the specified consent categories.

If a specific dimension should only be there when a consent category is granted, you should see 0% (or close to 0%). Higher percentages indicate that it is being sent or used even when consent has not been granted for that category.

Hovering over any value in the table will display a tooltip with a detailed explanation of what it represents, allowing you to understand your data at a glance. From the tooltip, you’ll be able to go directly to Trackingplan's Data Explorer or Trackingplan’s Root Cause Analysis. This will open the corresponding filtered view, saving steps and enabling further analysis or troubleshooting.

💡

To learn more about auditing cookies and consent management platforms (CMPs) with Trackingplan’s Consent Percentages Report, watch the video below.

Consent Counts Report

This report provides a summary of how many distinct entities — such as destinations, events, cookies, pixels, or domains — are active when consent is granted vs. when consent is denied.

☝🏻

Use it to verify that your tracking implementation respects user choices and identify any areas where data collection might be happening without proper consent.

While the Consent Percentages Report shows you how often consent is ignored, the Consent Counts Report shows how much tracking activity occurs under granted vs. denied consent.

For example:

If 10 analytics events fire when consent is granted but 8 still fire when denied, there’s likely a misconfiguration in your tag manager or CMP.
Similarly, if multiple marketing pixels or third-party domains load without consent, this could pose a privacy compliance risk.

This report is especially useful for auditing tracking behavior across multiple categories and destinations.

To use it, adjust the following parameters on the left-hand panel:

Date: Define the timeframe for your analysis.
Consent Source: Select the CMP or consent mechanism (e.g., DataLayer, OneTrust, CookieYes, Finsweet).
Group by (optional): Compare tracking activity across different attributions, such as hostname, country, device type, page path, or UTMs. For example, you can compare Spain vs Germany to see if consent enforcement differs regionally.

Once you configure these options, the report will calculate the average counts of distinct entities when consent is granted vs denied for each consent category:

Destinations: Average distinct tracking providers/destinations per page load.
Events: Average distinct (provider, event_name) combinations per page load.
Cookies: Average cookies per page load from cookies_list.
Pixels: Average tracking pixels per page load from event_projections.
Domains: Average distinct third-party domains contacted per page load.

Compare Hits vs. Yesterday Same Time Report (available on request)

A report to forecast traffic problems for incomplete days. This report helps you compare the number of hits or sessions for each event today vs. yesterday, based on the same time of day.

☝🏻

This report helps you monitor traffic issues, such as drops or real-time discrepancies in your recent releases or updates. It can also indicate missing data or events, helping you quickly detect any issues.

Once you access the Compare Daya Report, you’ll see a panel on the left where you’ll be able to adjust the following parameters:

Previous Date & Current Date: These fields allow you to define the two timeframes you want to compare in your report. This is especially helpful to analyze whether event volumes, hits, or session counts have increased or decreased compared to a specific reference point (e.g., yesterday, the same day last week, or a specific campaign launch).
Until Time: This parameter lets you set the cutoff time for the comparison. For example, if you want to compare data only up to 11:00 AM today vs. the same time yesterday, this field ensures your comparison is fair and reflects real-time performance. This is particularly useful when monitoring new releases, early-day issues, or campaigns that went live during the morning.
Warning Threshold (%): This value allows you to define what percentage of change is considered a warning. If a data point (such as an event or destination) has a difference greater than this threshold between the two compared periods, it will be flagged. For instance, if you set it to 30%, any change (increase or drop) greater than ±30% will appear as a warning in your report. This helps you focus only on the most significant anomalies, avoiding noise from small, expected variations.

After adjusting all these parameters to your needs, Trackingplan will calculate the expected number of hits based on historical traffic patterns and predict whether current traffic is aligned, lower than expected, or potentially problematic.

It calculates the expected number of hits for today by looking at how many hits each event had yesterday at the same time.
The % Difference column shows the predicted percentage difference between today's final value and yesterday's.
The Prediction column tells you whether the event's traffic is likely to become a problem by the end of the day. This one is calculated using the following thresholds:

Prediction	Meaning
DROP	Today's hits are expected to be more than 30% lower than yesterday.
PEAK	Today's hits are expected to be more than 30% higher than yesterday.
OK	The difference is within ±30%, so no major issue is expected.
NEW	No hits yesterday, but there are already hits today.
MISSING	There were hits yesterday, but none have been recorded today.

Playing with Your Reports

Advanced Reports are preconfigured by Trackingplan’s support team, but you can still tailor your view and interact with them in several ways:

Adjust filters and thresholds using the left panel.
Use the toggle sidebar for better readability.
Sort data by type or event to create a more tailored view.
Search within rows to quickly locate specific events or data points.
Export to CSV to share insights with your team or analyze data further in external tools.
Directly share your Advanced Reports with your teammates using the Share button.

If you need adjustments to an existing report or a new Advanced report, please contact our support team.

← Previous

Presence Map

Session Finder