All Collections
How can I ensure the privacy of my users when using FullSession?
How can I ensure the privacy of my users when using FullSession?
Abed avatar
Written by Abed
Updated over a week ago

Managing rules within the app through Settings

If there's a lack of available engineering resources or specific situations that make it impractical to handle data capture rules primarily through code, Admin users can opt to handle these rules using the Element recording rules UI within the application. This UI is accessible via clicking on the profile avatar in the right upper corner. Then you need to select sites and organization from the side settings navigation menu on the left. A page view will appear with all added domains to the subscribed account. Select the domain that you want to add privacy rules to by clicking on the 3 dots on the right.

You need to click on the create rule button at the element recording rules section as shown in the figure above.

From this point, you have the ability to generate or adjust data capture rules utilizing CSS selectors. Furthermore, exceptions can be incorporated to prevent some elements from being masked or excluded by the added rule.

Upon clicking the "Create Rule" button, the interface for adding an Element Data Capture Rule will appear. This widget enables the input of the CSS selector, and the selection of the rule type. A corresponding widget for editing rules exists as well.

CSS Supported by Element Data Capture Rules

CSS selectors serve as the primary means for controlling Exclude, Mask, and Unmask functions within the FullSession UI. It is crucial to employ comprehensive selectors judiciously, particularly during Unmasking, to maintain the Data Capture Rules list in a manageable state. When it comes to rule management, FullSession accommodates a wide array of CSS selector types, nearly encompassing the entire range. You can view the comprehensive list of supported selectors here:

Direct descendent: a > b

Attribute word selector contains: [a~=b]

Arbitrary attributes

Attribute hyphen contains: [a|=b]

Attribute equals: [a=b]

Attribute exists: [a]

Attribute starts with: [a^=b]

Id selectors: #a

Attribute ends with: [a$=b]

Class selectors: .a

Attribute contains: [a*=b]

Type (element) selectors: a

Any descendant: a b

For reference, Element Data Capture Rules DO NOT support the following CSS selectors:

Any sibling: a ~ b


Direct sibling: a + b

:is() (formerly :matches())

Universal selector: *

:nth-child /nth-of-type /etc

Grouping (OR): a, b

Here are some examples of some broad CSS selectors that have been used for unmasking larger sets of things:

Example CSS Selector



All selectors where the class contained “filter” making all search bars visible

[class^="panel container"]

All selectors where the class starts with “panel container”


All divs where the class contains “someClass”


Elements with a class attribute of "btn"

Please note: These examples worked in the case of a specific test site and may not apply to all sites.

Did this answer your question?