The Data Quality page helps you monitor the quality of data sent to Converge. It flags issues that might impact your reports or configured destinations.

The Data Quality page consists of two main sections:

  • Events Overview (left): Displays all tracked events within the selected time period.
  • Event Details (right): Shows detailed warnings and information for a selected event.

​
Events Overview

The Events Overview lists all events tracked from any of your event sources within the selected time period. For each event, you’ll see:

  1. Tracking method: How the event was tracked. Through a browser or server-side source or both.
  2. Event name: The name of the event as it was sent to Converge.
  3. Frequency: The average amount the event has been tracked each hour.
  4. Property warnings: A warning indicating issues with the event properties that could affect report accuracy or how events are sent to destinations.
  5. Stitching percentage: Percentage of server-side events that have been successfully stitched to web sessions. Read more about stitching percentage and why it matters here.
  6. Deduplication percentage: The percentage of deduplicated events if sent through browser and server-side sources both. Read more about deduplication percentage and why it matters here.

​
Event Details

After selecting an event in the Events Overview you will see the details about it in the right pane. On top of this section you will find the following information:

  • Tracking Method: The method used to track the events. This can be a browser or server source, or both.
  • Sales Channel: Which sales channels
     are used for the tracked events.

On the top right you will find a button which sends you to a filtered Event log showing the individual events that where tracked in Converge.

​
Overview

In the Overview tab you will see find the following details:

  • Events tracked: A graph showing how many events you have tracked per day.
  • Sources: A tab showing the sources through which the event were tracked.
  • Destinations: A tab showing the destinations which received the events.

​
Properties

In the properties tab, you’ll see all the properties sent with the event at the profile, session, and event levels.

If there are any issues with the properties, a warning will appear. Clicking on the warning provides an overview of the detected issues and how often they occurred within the selected time period.

By clicking on the arrow in the top right of each warning you will be sent to a filtered Event log showing the individual events which have incorrect values.

​
Stitching

To attribute server-side tracked events and enrich them with browser data, Converge must link these events to a corresponding web session tracked via a browser-based source, such as the Converge JS tracking pixel.

We consider a stitching rate of 95%+ healthy. If you have a lower rate, attribution and destinations might not behave as expected.

You can find more information about how Converge uses aliases to stitch browser and server events together in our Aliases documentation.

In the Stitching tab you will find:

  • Events per day: A graph displaying the stitching rate per day.
  • Stitching metrics: A table showing the number of server events received, unstitched events, and the stitching rate.
  • Unstitched events: A detailed view of individual unstitched events, including the aliases sent to Converge, event properties, and a
    link to a filtered Event Log for reviewing the specific event.
  • Delayed events: A list of delayed aliases, showing server events that Converge couldn’t stitch at the time of receipt but stitched later.
    These events were already sent to your destinations with potentially limited data but will be properly attributed in Converge reporting.

​
Deduplication

If you are sending an event through both a server-side and browser-side event source, Converge will need to deduplicate these events to avoid duplicate tracking in Converge or your destinations.

We consider a deduplication rate of 95%+ healthy. If you have a lower rate, your events might not be deduplicated properly and will cause duplicate tracking in your destinations.

You can find more information about how Converge uses event ID’s to deduplicate browser and server events in our Deduplication documentation.

In the Deduplication tab you will find the following information:

  • Events tracked: A graph showing how many events you have tracked through server and browser per day.
  • Deduplication metrics: A table showing the overlap of server and browser events per deduplication key.
  • Missing event IDs: A list of all the events which are either missing a matching server-side or browser-side event.

By clicking View event id you will be sent to a filtered Event log showing the specific event.

Was this page helpful?