Automated FullStory Frustration Scorecard
Every Monday, WebRun opens FullStory, pulls last week's rage clicks, dead clicks, and error sessions by page, logs each page's counts and week-over-week change to Airtable with replay links, and emails the product team a scorecard.
How do I get a weekly report of the pages frustrating my users most?
WebRun pulls rage clicks, dead clicks, and error sessions from FullStory every Monday, logs each page's counts and week-over-week change to Airtable with replay links, and emails the product team a scorecard that leads with what got worse. It turns raw session data into a weekly list of exactly which pages need attention.
- The team sees which pages got worse, not just raw click counts
- Every top session is linked and ready to watch, no manual searching
- Frustration trends show up weekly instead of surfacing in a support ticket
Built for product teams · UX researchers · product managers · growth teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.fullstory.comin a real browser with your saved login - no setup, no API keys. -
1
FullStory - pull frustration signals
fullstory.com
WebRun opens FullStory to pull frustration signals. - Open FullStory and pull last week's rage click, dead click, and error-session counts by page
- Compare each page against the prior week
- Note the pages with the sharpest increase
Done when Every tracked page has last week's frustration signals pulled.
-
2
Airtable - log the sessions
airtable.com
WebRun opens Airtable to log the sessions. - Log a row for each page with its frustration signal counts and week-over-week change
- Link the top sessions so a teammate can watch the replay
Done when The tracker has this week's row for every tracked page.
-
3
Gmail - email the scorecard
gmail.com
WebRun uses Gmail to email the scorecard. - Email the product team a scorecard of the week's frustration signals
- Lead with the pages that got worse, not just the raw totals
Done when The team has this week's scorecard in their inbox.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change anything in the product based on what it finds?
No. WebRun only reports the frustration signals it finds. Shipping a fix or changing the UI is left to your product and engineering team.
How does it decide which pages to highlight?
It compares each page's rage click, dead click, and error-session counts to the prior week, so the scorecard leads with what got worse, not just the biggest raw numbers.
Can I see the actual session replays?
Yes. Each row in Airtable links to the underlying FullStory sessions, so anyone can watch the replay behind the numbers.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.