Collect client feedback on staging sites

The work that most needs review — staging builds, pre-launch previews, client sites you don’t own — is exactly where a screenshot tool falls apart. Pogpin gives you three ways in, depending on how much access you have.

Option 1 — Embed the widget

If you can edit the staging site, install the widget. This is the smoothest experience: reviewers see the launcher the moment they land. Gate it to non-production so it never ships to your live site — render the tag only when your environment isn’t production:

<!-- server-render this only outside production -->
<script
  src="https://api.pogpin.com/widget.js"
  data-project-slug="YOUR_PROJECT_SLUG"
  data-project-key="YOUR_PROJECT_KEY"
  data-api-origin="https://api.pogpin.com"
></script>

Option 2 — Chrome extension

Can’t touch the code? Reviewers install the Pogpin Chrome extension and pin on any page they can open. Pins sync to the same project as the widget, so feedback lands in one place regardless of source.

Option 3 — Zero-install proxy review

For URLs where reviewers won’t install anything, share the project’s review link. Pogpin serves the page through a reverse proxy with the widget injected — no code changes, no extension. Each project gets its own proxy origin, and reviewers pin as guests. This is the same link used for guest reviews.

Which should I use?

Keep pre-launch work private

Pair proxy review with a guest access code (Settings → Guests) so only people with the code can open the preview — useful when a staging URL is guessable. For sites behind HTTP basic auth, share credentials over your usual secure channel; the reviewer’s browser prompts as normal.

Once feedback is flowing, turn it into a backlog with triage pins into tracked issues.