Tracklution Dashboard: Event Validation & Debugging

From the Tracklution container dashboard, you can see all events Tracklution has captured, including details like timestamps, sources, event values, and the Connectors they were sent to. For deeper inspection, you can drill down into individual sessions to view event payloads, ClickIDs, and UTM tags, helpful for both validation and troubleshooting. Filtering and search tools make it simple to focus on specific events, time ranges, or Connectors, so you can quickly identify and resolve any issues before sending data to your ad platforms.

Validate your setup and debug with Tracklution - Video guide

The Tracklution Dashboard

Filter events

You can filter the data on the dashboard with:

• Events
• Connectors the events were delivered to
• Sources or the sessions (Note! The source is marked only if a ClickID was tracked)
• Date range

In order to filter the data with event or Connector (Source / Delivered), simply click on the desired event / connector above the chart and the processed data table and the chart will be filtered. You can also use the filter on the right upper corner. In the example below, the dashboard is filtered to show all Lead events that occurred in the past 30 days and were delivered to Meta. To do this, click the Meta connector card, choose “Delivered”, then the “Lead” event card. After that you can use the date range filter and selected to show only the past 30 days.

Processed Data table

The Processed Data Table shows the events that Tracklution has processed and sent to your Connectors. Access The Processed Data Table by scrolling past the chart on the dashboard.

The table shows the following information:

• Timestamp: The time that the event was triggered.
• Source: The source of a session if such source is identified. The source is only marked if a click ID was tracked in the session.
• Details: The details or contact information of the user that triggered the event
• Value: The value of the purchase the user made.
• Events: Number of events that the user triggered.
• Delivered to: The Connector(s) that the event was sent to.
  

Individual session data

Event sources

When you drill down to the individual session level by clicking the arrow on the session row, you can see all the events fired within this specific session and additional information on each event, such as ClickID's and UTM tags recorded for this specific session. In Tracklution, we use three types of source identifiers to help track and attribute conversions more accurately:

• Primary ID: This is the main identifier used to attribute conversions. For example, when a user clicks on a Google ad, the gclid (Google Click Identifier) would be considered the Primary ID.
• Secondary ID: This field helps us specify which type of click ID was used as the Primary ID. Think of it as a label that adds more context. For example, if the Primary ID is a Google Click ID, the Secondary ID could be: gclid for Google Ads wbraid or gbraid for different types of Google campaign attribution.
• Tertiary ID: This is used to track alternative or additional identifiers that aren't part of the main click ID logic. A common example is: fbp – a browser ID used by Meta (Facebook) for tracking events, especially when there's no click ID available.
  

Event delivery statuses

You will also see the event delivery status, which can be used for debugging purposes; Tracklution will point out if the conversion delivery statuses as follows:

• Pixel Success: API deliveries were not made, but at least one pixel delivery was successful. This is expected with GA4.
• Success: Delivery was successful at least to one Connector
• Virtual: This is virtual event. It was not delivered.
• Delivery error: View error details from the event payload by clicking the error.
• Pending: This event is waiting for processing. It normally takes couple of minutes.
• Invalid Connector settings: Connectors were found but their settings are not valid. Please check your Connectors settings.
• No active Connectors: No Connectors were found for this event. Please check your Connectors settings.
• Rejected: This event was rejected. Normally this is because of set rejection rules.
• Generic error: Event had a generic error. Please contact support.
• System error: The error message was not found. Please contact support.

Event payloads

By clicking the arrow on the event row, you will be able to see the payloads for each event, from where you will be able to tell exactly what data was tracked and what was delivered to Connectors. There are three different payloads:

• Pixels Fired: These are small pieces of JavaScript code (like Facebook, TikTok, or Google Ads pixels) placed on your website. When a visitor performs an action like viewing a page, signing up, or making a purchase, the pixel “fires,” meaning it triggers a signal that the action happened. Pixels send this event data directly from the browser to the ad platform.
• API Request: After a pixel fires, Tracklution can send the event data server-to-server via an API request. This is a structured message containing all the event information (like purchase value, user identifiers, page URL) sent from Tracklution’s servers to the ad platforms. API requests allow tracking even when pixels might be blocked or fail in the browser.
• API Response: Once the ad platform receives the API request, it sends back an API response. This response tells you whether the event was successfully received, processed, or if there were any errors (like a missing click ID). It’s how Tracklution knows if the data reached the platform correctly.

Tracklution Debug Quest

Are you missing an event that should be delivered to Meta or Google Ads? Find your missing event by going through the Tracklution Debug Quest.