The Scenario
You are a product manager. Three weeks ago you shipped a redesigned checkout flow. Users are completing it at a lower rate than before and the support team is getting anecdotal complaints about confusing UI elements.
You open Sentry and there are session replays. The tag data shows rage clicks and dead clicks. But the Sentry interface shows you one selector at a time, in one project at a time.
You need all of it in a Google Sheet before your design review on Thursday morning.
The slow version:
- Open Sentry Replays, filter to the checkout project
- Read through the selector list, copy the element names and click counts into a sheet
- Switch to the second project (mobile-web), repeat
- Try to rank by combined click count across both projects
- You copy twenty selectors, realize you missed the pagination, and find twenty more hiding on page two.
The fast version is one prompt.
The Easy Way: One Prompt in SheetXAI
SheetXAI reads the Sentry replay selector data and writes it into the sheet, so you have a ranked list of problem UI elements before the design review.
Open the SheetXAI sidebar and type:
Get all Sentry replay selectors with rage clicks or dead clicks for organization 'my-org' over the last 7 days and write each selector, click type, click count, and project ID into this sheet, one row per selector. Sort by click count descending.
SheetXAI calls the Sentry replays API, pulls every selector with rage or dead clicks from the last seven days, and writes the full list into the sheet. You have a ranked list of the worst-offending UI elements before you have opened a design file.
What You Get
A ranked selector table:
- Selector — the CSS selector for the element (e.g.
button.checkout-submit,div.promo-banner > a) - Click type — rage click or dead click
- Click count — how many times this element was clicked in the last seven days
- Project ID — which project the replay came from
Sort by click count descending and the top five elements are your design review agenda. The selector string tells the designer exactly which element to look at in the codebase.
What If the Data Is Not Quite Ready
UX investigations always surface follow-up questions once the data is in the sheet.
When selector strings are too cryptic to share with designers
CSS selectors like div:nth-child(3) > button.w-full do not mean anything to a non-engineer designer.
Get all Sentry replay selectors with rage or dead clicks for 'my-org' over the last 7 days. Write selector, click type, click count, and project ID into columns A through D. In column E, write a plain-English label for each selector based on what the CSS class names suggest (e.g. 'Primary checkout button', 'Navigation link in header').
When you want to filter to only one specific project
The mobile-web project is the one under review. You do not need the data from the other three projects.
Get all Sentry replay selectors with rage or dead clicks for project 'mobile-web' in organization 'my-org' over the last 7 days. Write selector, click type, and click count into columns A through C. Only include selectors with a click count greater than 5.
When the design team wants to know which selectors improved versus last week
This week's data needs to be compared against last week's to find whether the situation is getting better or worse.
Get Sentry replay selectors with rage or dead clicks for 'my-org' over the last 7 days and write them into the 'This Week' tab: selector, click type, click count. Then get the same data for days 8 through 14 and write them into the 'Last Week' tab. In the 'Comparison' tab, write each selector and its count change, marking 'worse', 'better', or 'new' in column D.
When you want the full UX investigation artifact: selector list, total replay count, and a written summary in one shot
The design review needs an executive summary paragraph, not just raw data.
Get all Sentry replay selectors with rage or dead clicks for 'my-org' over the last 7 days. Write them into rows 3 and below with selector, click type, click count, and project ID. Fetch the total session replay count for the organization over the same 7 days and write it in cell A1. In cell A2, write a one-paragraph summary describing the top three problem UI elements and what the click patterns suggest about user friction.
The pattern: instead of reading selector lists inside Sentry one project at a time, you pull the full ranked list into a sheet and share it directly with design.
Try It
Get the 7-day free trial of SheetXAI and use it to pull Sentry replay selector data into a sheet before your next UX review. The Sentry integration is included in every plan. See also how to pull Sentry tag values for root-cause analysis or the Sentry in Google Sheets overview.