Available for the following Plan types:
FullStory for Mobile Apps
Available to the following User roles:
Element data capture rule exceptions allow you to apply element capturing rules to some, but not all, elements that match a selector. This gives you a high degree of control over the user data FullStory captures. In this article, we’ll review the benefits of using element data capture rule exceptions and how to get started.
NOTE: Element data capture rule exceptions are not supported on FullStory for Mobile Apps. Additionally, if your FullStory organization has mobile enabled, you cannot use this feature for web.
The Benefits of Element Data Capture Rule Exceptions
Exclude some, but not all, elements that match a selector
There are many cases where you may wish to exclude or mask some, but not all, elements that match a particular selector.
For example, we highly recommend you configure an element data capture rule to exclude or mask all
input elements across your site. This ensures FullStory won’t capture any potentially sensitive customer data entered into form fields like email or street address.
However, you may find there are specific
input elements you would like to capture. For example, your site search contains a wealth of insights about how users navigate your digital experience. By adding an element data capture rule exception, you can tell FullStory to apply data capture rules to certain
input elements but not others.
In this scenario, you could set up a rule that excludes all elements with the selector
input and add an exception to the rule for all elements with the selector
input.safe. Then, simply add the selector
input.safe to your site search and any other elements you wish to track.
Future-proof your site against accidental data leakage
Element exception rules also provide a great way to future-proof your site with user privacy in mind. By creating restrictive data capture rules and applying exceptions to specific selectors, you ensure that new elements added to your site match the most restrictive rule by default–safeguarding sensitive data as your site evolves.
Let’s continue the example above. We’ve masked all elements with the selector
input and added an exception for elements with the selector
input.safe. If a new
input gets added to your site in the future, it will be automatically masked by default. The
input would only be unmasked if its selector was purposefully changed to
input.safe, preventing FullStory from unintentionally capturing any data from new
In FullStory, create and manage your element data capture rules under Settings > Data Capture and Privacy > Privacy > Element Data Capture Rules. Use the field “Rule Exception Element Selector” to specify which selector(s) should be exempt from the rule. Your rule will not apply to any elements that match this criteria.
Note: Exceptions must be simple selectors. Combinators are not supported.
Do element data capture rule exceptions apply to code-first rule management?
There are two different approaches to managing your element data capture rules. The first is to implement the appropriate CSS classes into your element libraries, an approach we refer to as “code-first.” The second method for managing element data capture rules is through the FullStory Element Data Capture Rules UI located in Settings > Data Capture and Privacy > Privacy.
Element data capture rule exceptions apply only to the in-app Element Data Capture Rules located in Settings > Data Capture and Privacy > Privacy. They do not apply to rules set using the code-first approach.
Why should I use an element data capture rule exception instead of creating multiple data capture rules to control which elements are masked and unmasked?
Element data capture rules will always apply the most restrictive block rule that matches an element. For example, if you have one rule that masks
input and another rule that unmasks
input.safe, FullStory will respect the most restrictive rule and apply the mask to both
input.safe. Element data capture rule exceptions allow you to manage this more effectively and reduce the number of data capture rules in your account. Win-win!
Are element data capture rule exceptions retroactive?
No. Adding a new element data capture rule exception will only affect FullStory’s data capture behavior from that point forward.