Naming css to be able to find it uniquely in FS

  • 14 February 2023
  • 6 replies

Hi all,

I am looking to gain insight into a paritcular element on our site. However, the element appears to share the name of other elements site wide. What are the steps to get an element to be uniquely searchable in FS? 


6 replies

Userlevel 4
Badge +3

Hey @rdpom without knowing exactly the elements on your site I can’t say for certain, but here are a few ideas:

  1. Refine. Use the refine feature to add specificity to your CSS elements. For example, maybe the CSS is a reused button component (a frequent culprit) but you can use the Refine feature to add when [Element text] [is] [Get Started] to make that CSS specific to that button text. (You can add another Refine to page URL and other properties too.)


  2. Aria Labels. These labels help FullStory understand which elements are unique, which can help you understand overall user behavior. And even more beneficial, Aria Labels support assistive technology so will help improve the usability of your site.

I think that’s might be it for my initial thoughts and hopefully one or both of the above help you understand elements with more specificity and therefore the user behavior that underpins it. Good luck!

Userlevel 4

Hey @rdpom! Thanks for your question and thank you @stevenshyne for your answers- these are great! 😄

I will also add that if you want to focus on just one part of the website, you can refine the event by Page or URL as seen in this example here:

If you’re working with SPAs and cannot get down to one specific URL, you can click on Full selector in Page Insights and see if there are any data attributes we are not indexing today (these will be in [brackets]). If there is something in brackets that describes the element well, you can create an indexing rule in Settings > Data Management > Indexing. You can read more on that here!

Please let me know if you have any other questions!

Hi Steven and Lindsay, this is very helpful! Unfortunately I wasn’t able to solve the issue. The CSS in question is below, looking to detect the use of the anticon-eye for the provider-info-form_ssn.

If you have any further suggestions I’d love to hear them! 


Thank you,


Userlevel 4

Hey @rdpom! Thanks for your response!

I’m sorry to hear those options didn’t work for your case. I would suggest scheduling an office hours session with one of our Customer Success Managers as they’d be able to take a closer look and walk you through any steps needed!

You can schedule this by heading to “help” at the top right of your page in FullStory and selecting, “Customer Success Office Hours” here:

Thank you and please let me know if you have any other questions! 

Userlevel 4

Hey @rdpom! I wanted to follow up here and let you know that from the screenshot you shared, it appears as though the element you may be trying to target is covered by our default privacy rules, specifically exclusion.

This means FullStory does not capture any interaction with that element so it is impossible to search for clicks or changes to it. If you need to understand interactions with this element, you would need to trigger a custom event while keeping in mind that the content of that element must not be transmitted in the custom event. You can view more about FullStory’s privacy rules here

I would still recommend booking an office hours so one of our awesome Customer Success Managers can go through this with you, but I wanted to share some context here!

Thanks and as always, please let me know if you have any other questions. 😊

Userlevel 4
Badge +2

@rdpom Maybe something like this could help