Who can use this feature?
- Available with all plans.
Fullstory’s Data Quality Monitoring system can easily identify Elements, Events, and Pages that may have configuration issues. It’s important to regularly check your objects to maintain data continuity and archive any outdated data objects.
Issues
Issues arise when a CSS selector you've defined in Fullstory is no longer being seen. Usually, it’s due to underlying website changes. These changes could range from minor modifications to significant structural changes in your website's HTML, or shifts in your site's design or functionality.
Identifying Issues
In Settings > Data Management, filter the Elements, Events, or Pages table by Has issue to view objects with data tracking issues. When the data object has stopped receiving data traffic within the past 72 hours, an issues icon will display. Pending indicates that a change has been made to an data object you are monitoring. For example, this could mean the definition was modified.
The 30-Day Volume column represents all activity over the past 30 days. Some examples include clicks, highlights, hovers, etc.
Investigating Issues
Once an issue is identified, it’s time to investigate the problem! Click on the object to open the definition modal. The modal will display an Issue banner stating event traffic has not been generated within the last 72 hours.
You can snooze the notification for three days, seven days, or until activity returns. If you don’t want to snooze the issue, navigate to the Activity tab to visualize the volume, and jump to the most recent session, or review the change history!
Understanding element, event, or page usage
If you’d like to see where an element, event, or page is being used, you can go to the References tab of the Data Studio. From there, you can view library objects that are using the element, event, or page. You can also go to the library object to view how the element, event, or page is being used.
Best Practices with Issues
Use the OR statement to include a new selector in the definition when:
- The historical data is useful, relevant, or should be maintained to refer back to.
- There are multiple selectors used to define the event or object.
Replace the broken selector with a new one in the definition when:
- The selector used is too broad for the definition.
- The historical data captured by the selector is not useful to maintain or refer back to.
- The dynamic content varies the appearance or structure of the element on the page.
Snoozing events helps reduce the noise of issues. Snoozing is commonly used in cases where:
- There is a thematic marketing campaign, landing page, or an experiment in the form of A/B testing where the UI with a given element is on hold. In this case, snoozing an element issue will reduce the noise until the UI is live again.
- An element tracks rare occurring behavior, such as an error that is expected to happen a few times in a given month. In this case, snoozing the element issue will reduce the noise between 3 or 7 days, while still keeping track of the issue.
FAQ
Will Data Quality Monitoring ever stop being tracked?
Data quality monitoring will stop if an org exceeds its session quota. Volume and issue updates will stop until the quota resets. Read more on this here.
Why don't I see a most recent session on my element flagged with an issue?
A most recent session will only display if the element’s Last Seen date is within the past 30 days. If the Last Seen date is over 30 days ago, then a session is not available.
If I make a change to my elements, will this be retroactive?
No, changes to elements that have been named are only retroactive when used for search.
Is Data Quality Monitoring available for both user-defined events and API events?
Yes. However, API Events with issues cannot go into a pending state now. Instead, you have options to archive the API event or set up a new API event.
Why don't I see references for API events?
References for API events is currently not supported.
If I make a change to my defined events, will this be retroactive?
No, changes to defined events are only retroactive when used for search.