Data Quality Monitoring

FullStory’s Data Quality Monitoring system allows you to easily identify data objects (i.e. Elements) that may have configuration issues. It’s important to regularly check your objects in order to maintain data continuity and archive any outdated data objects. 


Element 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 Element Issues

First, navigate to Settings and select Elements. The table allows you to easily identify elements with data tracking issues by viewing the Issues column or filtering the table by Has issue. When an element 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 element you are monitoring. For example, this could mean the element definition was modified. 

The 30-Day Volume column represents all activity over the past 30 days. Some examples include clicks, highlights, hovers, etc. 

Investigating Element Issues

Once an element issue is identified, it’s time to investigate the problem! Click into the element to open the element definition modal. The modal will display an Issue banner stating the selector used to define the element has not generated event traffic within the last 72 hours.

You can choose to snooze the notification for 3 days, 7 days, or until activity returns. If you don’t want to snooze the issue, navigate to the Activity tab to visualize the event volume and jump to the most recent session that includes the element with an issue. 

Screen Recording 2023-08-11 at 03.25.50 PM.gif

Best Practices with Element Issues

Use the OR statement to include a new selector in the element definition when: 

  1. The historical data is useful, relevant, or should be maintained to refer back to.
  2. There are multiple selectors used to define one element. 

Replace the broken selector with a new one in the element definition when:

  1. The selector used is too broad or for the element definition.
  2. The historical data captured by the selector is not useful to maintain or refer back to.
  3. The dynamic content varies the appearance or structure of the element on the page.

Snoozing events helps reduce the noise of element issues. Snoozing is commonly used in cases where: 

  1. 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. 
  2. An element is tracking 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. 


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.

Need to get in touch with us?

The FullStory Team awaits your every question.

Ask the Community Technical Support