# Feedback capture from any webpage with source URL

> Capture a request from the page where it came up, attach the voter immediately, and keep the source URL on the post so product sees the real context.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/feedback-capture-from-any-webpage-with-source-url/
- Source: [help.canny.io](https://help.canny.io/en/articles/5633815-chrome-extension)
- GrowthDex source hub: [Canny Help Center](/sources/canny-help-center-help-canny-io/)
- Last checked: 2026-05-28
- Rarity: rare
- Budget: low
- Channels: Sales, Support, Product
- Stages: feedback capture, context retention, voice of customer, operations


## Why this can grow

A lot of feedback shows up away from the formal portal: a LinkedIn thread, a docs page, a support ticket, or a sales tool. The problem is not hearing it. The problem is preserving the context once someone tries to log it. Canny's Chrome extension helps because the admin can add a post or vote from the live page, and the resulting vote keeps a reference to the original URL. That makes the backlog easier to trust later because the team can still inspect where the request came from instead of relying on somebody's cleaned-up summary.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where feedback capture from any webpage with source url can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Sales and Support channel.
3. Use the evidence from help.canny.io to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Canny's Chrome extension lets admins create feedback, add a vote on someone's behalf, and include an internal comment from any website, while linking the vote back to the page URL where it was captured.

## Adjacent tactics in the same lane

- [Segment-filtered voter list with opportunity value](/growth-ideas/segment-filtered-voter-list-with-opportunity-value/) - same source, 2 shared channels, 1 shared stage
- [Public comment update emails every voter](/growth-ideas/public-comment-update-emails-every-voter/) - same source, 2 shared channels
- [Public ETA on roadmap only when ready](/growth-ideas/public-eta-on-roadmap-only-when-ready/) - same source, 1 shared channel
- [Status-change-sorted public roadmap](/growth-ideas/status-change-sorted-public-roadmap/) - same source, 1 shared channel

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The feedback board should keep getting sharper after the vote](/blog/the-feedback-board-should-keep-getting-sharper-after-the-vote/) - product feedback, roadmap trust, customer operations

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.