How do I create exceptions to element data capture rules?

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 for Mobile Apps: 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.

Note for Private by Default: Rule exceptions apply only to elements that are masked or excluded by a specific element data capture rule. They do not apply to elements that are masked by Private by Default. If your site uses Private by Default and you need to unmask an element, you must create a specific unmask rule for that element. Adding a rule exception will not unmask elements that are masked through Private by Default.

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 selectorinput.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 input elements. 
 

Getting Started

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.

Frequently Asked Questions

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 and 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.

Can rule exceptions unmask elements that are masked by Private by Default?

No. Rule exceptions only apply to specific element data capture rules you create—they cannot override the Private by Default global setting. If you need to unmask an element that is masked by Private by Default, you must create a specific unmask rule for that element.

However, rule exceptions work perfectly fine with additional rules you create on top of Private by Default. For example, if you have Private by Default enabled and you create a rule to exclude certain input fields, you can use rule exceptions to specify which of those input fields should not be excluded. The rule exception applies to your configured rule, not to Private by Default itself.