The replay library provides several ways to refine your list of replays, including global filters that persist across much of Pendo, advanced filters for specific interactions or visitor behaviors, and suggested replays based on your filters. By combining these filters, you can quickly pinpoint the replays that matter most and streamline your workflow with saved configurations.
Global and advanced filters
Global filters are the filters at the top of the page that persist across most other pages in Pendo. These include segment, date range, account, application, and favorites. Global filters work the same way that they do in other parts of Pendo, though the date range filter applies exclusively to the replay library and doesn’t affect date ranges on other pages.
Advanced filters allow you to refine your replays further by focusing on specific event interactions (for example, Page or Feature views, guide interactions), frustration indicators (for example, rage clicks and U-turns), and replay duration. You can combine multiple advanced filters to find replays that match your specific criteria.
Replays of event interactions
Event filters are tied to interactions with specific events that take place in your application, specifically interactions with tagged Pages and Features, guides, or entire Product Areas. To apply an event filter, select Add filter below the global filters, choose Event, then select an event type.
Depending on your selection, choose the specific event or Product Area from the dropdown menus, then specify whether it was interacted with during a replay, then select Apply.
Replays of potential frustration
Frustration filters surface replays containing potential user friction within your application. Frustration indicators include:
| Frustration type | Description | Icon |
| Rage click | Repetitive clicks in a focused area of your application. |
|
| Error click |
A click generated a client-side JavaScript error. For it to qualify as an error click, the client-side JavaScript error must occur within 100 milliseconds of the Feature click. If an error message is explicitly defined, it appears in the event log, which you can copy to your clipboard to share with your team. You can also create an issue directly from the event log. |
|
| U-turn |
A visitor navigated to a Page and returned to the previous Page within seven seconds. Even if Feature clicks occur within those seven seconds, it's still considered a U-turn. However, if other Pages are navigated to within seven seconds, that isn't considered a U-turn. U-turns are only identified on tagged Pages. |
|
| NPS detractor | A visitor submitted an NPS response rating of 0 to 6. |
|
| Over-guidance | At least three guides appeared to a visitor within five minutes, five guides appeared within six or more minutes, or at least 10 guides appeared within at least 61 minutes. |
|
| Dead click | A click that doesn't result in any visible changes within your application, such as updates to the page structure (DOM mutations), document events (like text selection or scrolling), or browser events within a short time period. |
To apply a frustration filter, select Add filter below the global filters, then choose Frustration. Select the frustration indicator type and its occurrence, then select Apply.
Tip: If an interaction is incorrectly flagged as frustration, you can mark it as expected behavior. In the event log, select the ellipsis next to the event, then select Ignore as [frustration type]. This ensures that the interaction is no longer flagged as frustration in current and future replays. Find all ignored frustrations in your replay settings (under Settings > Subscription Settings > Applications > select application > Replay Settings > Ignored frustrations).
Replays of specific duration
Duration filters focus on replays based on how long a replay lasts. This can help you isolate particularly short or lengthy replays to better understand user behavior.
When filtering by Duration, select the appropriate operator (is greater than, is less than, or is between), specify the duration values in minutes, then select Apply.
How replay filters apply
Only "AND" rules are supported for filters. This means that the table results display replays that contain all of the selected filters, rather than replays that contain at least one.
When you apply an advanced filter, it adds inline annotations to the corresponding replays so that you can easily locate the specific interactions within a replay. Select an annotation to skip to that part of the replay, or hover over the annotation and select View details to view the details page for the corresponding event.
Saved replay filters
Create a saved filter to preserve your current filter selections and table configurations. This allows you to save your most-used filters so that you can monitor your replay queue for the replays that matter most to you. You can create multiple saved filters.
To create a saved filter, apply your desired set of filters above the Replays table and modify the table layout to your preference. Depending on where you are in the replay library, you might have different selections for saving your filters:
-
Save as. This option appears if you're viewing an uneditable saved filter, such as the default All replays saved filter that opens the first time you open the replay library.
This action opens the Create Replay saved filter window where you can add a title and optional description to the saved filter, then select Create saved filter.
-
Save filters. This option appears if you're viewing an editable saved filter, like one that you or a teammate has already created. This overwrites the original filter selections and table layout and applies your current view to the saved filter.
You can also select the dropdown next to Save filters to instead:- Save as new saved filters. Opens the Create Replay saved filter window so that you can save your filter selections and table layout as a new saved filter.
- Revert changes. Removes any newly selected filters and table modifications that you applied since opening the saved filter.
Replay filter actions
After setting up your replay filters, you can manage and share them using the options at the top of the page.
In the top-left corner of the page, you have two options:
- All Replay saved filters. View the full list of saved filters across your team. You can also create a new saved filter from here by selecting Create saved filter.
- Change saved filter. Switch between recently accessed saved filters.
In the top-right corner, you have four options in addition to saving your filters:
- Favorite saved filter. Use the star icon to mark this saved filter as a favorite. You can later filter by favorites when viewing all saved filters.
- Add to dashboard. Add the saved filter to a new or existing dashboard using the Replay Saved Filters dashboard widget. This widget displays the 10 most recent replays for this filter and lets you open the filter in the replay library to view all associated replays.
- Delete saved filter. Use the trash icon to remove the saved filter from your library.
- Copy link. Copy the link to your device's clipboard so that you can share the saved filter with other Pendo users.
Filters in suggested replays
The filters you apply at the top of the page change the list of suggested replays shown.
Hover over the filter icon in the top-right corner of each suggestion tile to see which of your selected filters apply to the insight. Not all filters are supported for each suggestion. For example, the usage trends always provide information related to the last seven days, regardless of your current date range filter.
Event filters for specific Pages or Features function as "OR" rules and help surface relevant insights for suggested replays. With event filters applied, suggested replays might include:
- Rage clicks on the selected Pages or Features.
- Usage increased or decreases for the selected Pages or Features over the past week.
- Insights related to Features on the selected Pages, except for those specifically excluded by your filters.
Event filters only apply to suggested replays when they're inclusive of a particular Page or Feature (that is, set to viewed or clicked rather than not viewed or not clicked). For example, if you have a filter of Page A not viewed, suggestions won't include Page A or its features, unless you also have a filter like Feature A viewed applied if that Feature is located on that Page.
If you have event filters applied and no suggestions display, that means no rage or error clicks occurred on that Page or Feature, and there wasn't at least a 50% increase or decrease in views or clicks for that Page or any Features on that Page.