How to Read Your PingRoom Personal Room Insights
Read scans, Pings, contact shares, repeat visitors, and timing without treating activity as proof of intent.
Open your Personal Room, choose Insights, and start with one time window: week, month, or all time. Read the screen in this order: QR scans, Pings received, accepted contact shares, repeat visitors, then Quick Ping and timing patterns.
Personal Room Insights requires PingRoom Pro. The numbers describe recorded activity in your Personal Room. They do not prove why someone scanned, whether a Ping caused a contact share, or what a visitor intended.
Pick the window before reading the numbers
Use Week for a recent event or a small change you can remember. Use Month for a steadier pattern. Use All time for context, not as the default comparison for a new experiment.
The total-Pings card can compare the selected window with the preceding one. Keep the windows aligned: this week against the prior week, or this month against the prior month. A percentage change without the underlying count can sound larger than the practical difference, so read both together.
Read the activity path from left to right
The funnel separates three events:
- QR scans record openings through a Personal Room QR.
- Pings received count Pings sent to that Personal Room.
- Contacts shared count accepted contact-share requests.
These are related stages, not a causal proof. One person may scan more than once. Someone can open a public handle without scanning a QR. A visitor can Ping without asking for contact details, and an accepted contact share does not prove that a particular design or Quick Ping caused it.
| Insight | What it describes | What it does not prove |
|---|---|---|
| QR scans | Recorded opens through the QR path | Unique people, attention, or a successful conversation |
| Pings received | Pings sent to the Personal Room in the selected window | Satisfaction or urgency |
| Accepted contact shares | Contact requests accepted in the window | That a scan or Ping caused the acceptance |
| Acceptance rate | Resolved contact requests that were accepted | The outcome of requests still waiting for a decision |
| Average response time | Time to acceptance for accepted contact requests | Response quality or time spent considering a rejection |
| Mutual exchanges | Connections where both sides shared contact access | Friendship, endorsement, or relationship strength |
| Repeat visitors | Authenticated visitors with scans on at least two distinct days | The same physical person behind anonymous or shared use |
| Top Quick Pings and time heatmap | Which Quick Pings and local day/hour slots appeared most in the data | A guaranteed best message or recommended send time |
The acceptance-rate denominator excludes unresolved requests. Average response time is based on requests that were accepted. Read those definitions before comparing two windows.
Run a five-question weekly review
Once a week, answer these questions in order:
- Was the Room available for the whole window? A break or a newly shared QR changes the opportunity for activity.
- Did scans become Pings? Note the relationship, but do not call it a conversion rate unless the events and denominator fit the question you are asking.
- Were contact requests resolved? A pending request should not be silently treated as a rejection.
- Did people return on another day? Repeat visitors can show return activity, but not the reason for it.
- Do the Quick Ping and time patterns match real conversations? Change copy only when the observed pattern and what people actually tell you point in the same direction.
Consider an illustrative conference table. During one week, the Room records more scans than Pings, a few accepted contact shares, and a cluster of “Send the details” Pings in the afternoon. A careful conclusion is: people used the QR, some chose to Ping, and that Quick Ping appeared often in that window. It is not evidence that the QR design caused the contact shares or that afternoon is universally the best time.
Pingo the Pigeon, our fictional Chief Marketing Officer, is staring at the smallest tray because it prevents the largest claim. He cannot access Personal Rooms, read private activity, or interpret anyone's intent. The scene and figures are illustrative, not customer data.
Change one thing, then wait for a comparable window
If the data and real conversations suggest a problem, make one restrained change. You might simplify one Quick Ping, improve the physical placement of a QR, or make the Room's purpose clearer.
For a QR-design change, follow the Personal Room QR proof: test contrast, the final placement, the destination, and availability. Then compare equivalent windows. Do not change the QR, Quick Pings, availability schedule, and audience at once and attribute the result to one of them.
Insights also should not become a private dossier. If someone shares contact access and you need a small reminder, use a private connection note for the minimum context you genuinely need. The aggregate Insights screen and a private note solve different tasks.
Know the limits before acting
Insights can help you notice activity that deserves a closer look. They cannot tell you what someone thought, replace consent, or establish a benchmark for every Personal Room.
There is no universal “good” scan-to-Ping ratio in this guide. A quiet Room shared with five people has a different job from a public event QR. Start with the Room's intended task, compare like with like, and ask for direct feedback when the numbers cannot answer the question.
Open Personal Rooms, choose one useful window, and write down one observation before deciding whether anything should change. Current Pro limits and feature availability are listed on the features page.
Illustrations are AI-generated editorial scenes featuring Pingo, PingRoom's official mascot and fictional Chief Marketing Officer, with fictional approved PingRoom avatars. The review scenario is an example, not customer data or a performance benchmark. The human team is responsible for product claims and decisions.
PingRoom
Short-form communication.
