This feature is not supported on FullStory for Mobile Apps.
Have you ever wanted to search for sessions where a particular element has been displayed to a user, but they may not have interacted with it in any way? Now you can do just that!
Watched Elements help you determine if an element rendered on the page and if it was visible in the user’s viewport.
Error dialogs like these are great candidates for becoming watched elements.
Implementing Watched Elements
This feature must be configured by an Admin or Architect user.
There are two ways to implement Watched Elements on your site:
- Create Watched Elements under Settings > Recording and Privacy > Recording.
Create Watched Elements using Page Insights.
We’ll explore both methods below. But first, let’s cover a few need-to-knows.
- Watched Elements must be instrumented.
- Watched Elements are not retroactive. When you search for sessions where a Watched Element rendered or was visible, you’ll see results starting from the time of instrumentation.
- Instrumenting Watched Elements that load frequently or across many pages can potentially impact site performance. Use Watched Elements judiciously.
- FullStory indexes up to 10 Watched Elements per second per page and up to 30 Watched Elements per minute per page.
- All events after 10 in a one-second time frame and 30 in a one-minute time frame will not be indexed or searchable.
- Watched Elements uses a browser technology called ResizeObserver. While ResizeObserver will catch a great many things, it does have some limitations.
Create Watched Elements Under Settings > Recording and Privacy > Recording
Head to Settings > Recording and Privacy > Recording to create, edit, and delete Watched Elements in your account.
To create a new Watched Element:
- Go to Settings > Recording and Privacy > Recording and scroll down to Watched Elements.
- Click Create Watched Element.
- Add your element’s information:
- Element Name: a word or two that describes the selector in language a human would understand. For example, “Error Message.
- CSS or Application Element Selector: the selector you’d like to watch.
(Optional) Element Description: reasons why a Watched Element was added, an explanation of the chosen selector, or anything else you think might be helpful to include.
Create Watched Elements Using Page Insights
If you’re unsure of what specific selector you should use to instrument a Watched Element, creating the element using Page Insights is helpful. Using this method, you can use Inspect Mode to simply point and click on your desired element during session replay.
- While watching a session, navigate to Page Insights > Inspect Mode.
- Click on the element you’d like to watch, then click Watch Element.
Fill out the details and click Create Watched Element.
Using Watched Elements
After you instrument Watched Elements, you can search for them using OmniSearch and analyze their impact on Conversions.
Searching for Watched Elements
To find sessions where a Watched Element is rendered during the user’s session, create a search using the “Watched Element” event filter.
This shows you sessions where the element rendered on the page, but may or may not have been visible in the user’s viewpoint.
Time Duration Visible
To get more specific, use the “Refine event by…” icon to scope your search.
This helps you find sessions where the Watched Element loaded and was visible in the user’s viewport for a specific amount of time.
Time Duration Rendered
Time Duration Rendered is the total time that a Watched Element was rendered on the page. The count starts when the element is inserted into the DOM and stops when it is removed.
- Time 0: Watched Element Rendered
- Time 100: Watched Element Hidden
- Time 200: Watched Element Rendered
- Time 400: Watched Element Hidden
Analyzing Watched Element Impact on Conversions
Watched Elements can also be used as a signal for analysis in FullStory’s Conversions product. Learn more about Conversions and how to analyze the impact of Watched Elements here.
Watched Element Rate Limits
FullStory limits the number of watched element events we produce to ensure we aren't producing too many per page or single point in time. To see if you've hit a rate limit, look for Watched Element API errors using FullStory search.
Rate limiting is most often caused by choosing a selector that is too broad, matches too many elements on the page, or gets removed and added to the DOM repeatedly. As such, please check your Watched Element selector rules to make sure they are as precise as possible.