Get a weekly Contentsquare friction scorecard
Every Monday, WebRun opens Contentsquare, pulls last week's zone-level friction and rage-click data for key pages, exports the full report to Drive, and posts a Slack summary that leads with the page whose friction got worse.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get a weekly report of the pages causing the most user friction?
WebRun pulls zone-level friction and rage-click data from Contentsquare every Monday, exports the full report to Google Drive, and posts a Slack summary that leads with the page whose friction got worse. It turns raw session analytics into a weekly list of exactly which pages need a design or product look.
- The team sees which pages got worse, not just raw click counts
- A full zone-level report is archived to Drive every week
- Friction trends show up weekly instead of surfacing in a support ticket
Built for product teams · UX researchers · digital experience teams · 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.contentsquare.comin a real browser with your saved login - no setup, no API keys. -
1
Contentsquare - pull zone-level friction data
contentsquare.com
WebRun opens Contentsquare to pull zone-level friction data. - Open Contentsquare and pull last week's zone-level friction and rage-click data for key pages
- Compare each page against the prior week
- Note the page with the sharpest increase in friction
Done when Every tracked page's friction data has been pulled and compared.
-
2
Google Drive - export the report
drive.google.com How to Automate Google Drive
WebRun opens Google Drive to export the report. - Export the friction report with zone-level detail to the shared Drive folder
- Name the file with the date so history stays searchable
Done when This week's friction report is saved to Drive.
-
3
Slack - post the summary
slack.com How to Automate Slack
WebRun posts to Slack to share the summary. - Post a summary of the week's friction data to the product channel
- Lead with the page that got worse
Done when The team has this week's friction summary in Slack.
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 on the site based on what it finds?
No. WebRun only reports the friction signals it finds. Shipping a fix or changing a page is left to your product and design team.
How does it decide which page to highlight?
It compares each page's zone-level friction and rage-click counts to the prior week, so the summary leads with what got worse, not just the highest raw count.
Where does the full detail live?
The complete zone-level report is saved to Drive every week, so anyone can dig into a specific zone beyond the Slack summary.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.