You published a review of a checkout redesign on Tuesday morning and sent the link to five people: the client in Austin, their marketing lead in Chicago, your developer in Lisbon, a QA contractor in Manila, and your own account manager in Toronto. By Thursday nobody has commented. Before you chase everyone, open the owner analytics page on the review. It answers one question that changes how you follow up: did they actually read it.
What the analytics page shows on one real review
Every review you publish has an owner-facing analytics page. It shows two things: how many times the review link has been visited, and where the visitors were. Here is what that looked like for the checkout review three days after sending it.
| Metric | Value |
|---|---|
| Total visits | 11 |
| Austin, US | 4 |
| Toronto, CA | 3 |
| Lisbon, PT | 4 |
| Chicago, US | 0 |
| Manila, PH | 0 |
Eleven visits, three locations. Two of the five people you sent it to never opened it. That single fact reshapes your next message.
Reading the numbers instead of guessing
Take them one row at a time.
Austin, 4 visits. The client opened it, then came back three more times. Repeat visits from one location usually mean someone is reading carefully or showing it to a colleague on the same network. When you follow up with the client, you are not asking whether they saw it. You are asking what they think.
Lisbon, 4 visits. Your developer opened the review and returned to it, which is what you want before code starts. If they pulled the plain markdown version of the review to hand to a coding agent, that read still counts as a visit from Lisbon. High developer visit counts on a build review often mean the feedback is being worked through item by item.
Toronto, 3 visits. That is you and your account manager. Owners and their own team show up in the counts too, so subtract your own reads before you draw conclusions. Three visits from Toronto probably means you opened it twice and your AM once.
Chicago, 0. Manila, 0. The marketing lead and the QA contractor have not opened the link. No amount of waiting will produce a comment from someone who never arrived. This is the row that saves you a week. Instead of a group nudge, you send two direct messages: one to Chicago asking marketing to check the copy, one to Manila asking QA to run the test pass.
What the geography does not tell you
The analytics are counts and locations, not identities. If two people in the same city open the link, you see one location with two visits, not two names. A visitor on a VPN can show up in the wrong country. Someone who forwards your link to a stakeholder you did not expect adds a location you cannot immediately place. Treat an unexpected city as a prompt to ask, not as proof of who read it.
The page also does not tell you what anyone did once they arrived. A visit means the link loaded. It does not mean they read every item or scrolled past the first screenshot. For that signal, watch the comments. When someone posts a comment on an item, or you mark one resolved as the owner, you know the review is being worked, not just opened.
Turning a zero into an action
The practical value of visitor geography is that it separates people who ignored your feedback from people who never received it, and those need different responses. A stakeholder who read the review and stayed quiet may disagree or may be waiting on someone else. A stakeholder at zero visits may have lost the link in a thread, filtered the email, or never got it at all.
For the Chicago zero, resend the exact link with a one-line pointer to the item that concerns marketing. For Manila, confirm the contractor can reach the review at all, since a link that opens fine for you can still be blocked on their side. If reach is the recurring problem, the fix is upstream: publish reviews that open with no install and no signup so there is nothing between the receiver and the content. That is the point of the whole flow. A reviewer captures a screen, talks or types through it, and the receiver clicks a link and reads. You can start one from the browser-based capture and review tool without an account.
When to check the page
Check the analytics once, roughly two to three days after you send a review, then again if you are close to a deadline and comments are thin. Checking hourly tells you nothing useful; visit counts move slowly and each of your own opens inflates the count. If you run reviews for clients on a schedule, the same pattern shows up round after round, and you learn which stakeholders open links fast and which need a direct poke. That is worth building into how you run feedback across timezones, where you may never be online at the same time as the person who owes you an answer.
Next time comments stall, do not send the group reminder. Open the analytics, find the zeros, and message only those people. The counts tell you exactly where to spend the follow-up.