Practical Guides
Your review count changed. What does that actually prove?
A practical month-end check for review totals: match the listing, separate net change from new reviews, preserve missing data and assign a useful next action.
By Mister Ripple ·
Interactive tools load with JavaScript. The article text and source links are available below.
Key takeaways
- A missing observation is unknown, not a recorded zero.
- Compare the same location, platform and definition at two recorded times.
- The difference between two public totals is net movement. It does not identify every new review or its source.
- Investigate changes before assigning blame, claiming campaign results or changing how customers are invited.
Start with the label beside the number
A location manager sees 108 reviews on a listing. A monthly report shows eight. A campaign screen shows twelve redirects. Those figures can all be accurate while describing different events. The mistake is treating them as interchangeable measures of new public reviews.
Before discussing whether a campaign worked, write a plain definition: public review total for this specific listing, reviews dated within a selected period, or recorded activity inside a campaign. Include the platform, location, observation time and filters. A number without those details is a clue to investigate, not a performance verdict.
This guide offers an operating method for that investigation. It is not a claim that every platform exposes the same reporting fields, that Ripple observes every external review, or that a public count change can be attributed automatically to a QR scan.
Check the exact location before comparing totals
Two branches can share a trading name, website and central phone number. A search for the brand can open a different location from the one used in last month’s screenshot. A group-level report can also include several locations while the public page displays just one.
Record the exact public listing link and the branch address together. Where available, keep the listing’s stable identifier as well. Open the link and confirm the address rather than relying only on a similar name. If a profile has merged, moved or changed, note that event before calling the two snapshots comparable.
Use a separate row for each location and platform. Do not copy one branch’s public rating or count onto an entire group. An unverified match should remain unverified until someone checks it; filling the gap with a plausible nearby business makes the spreadsheet look complete while making its conclusion less reliable.
| Field to keep | Why it matters | If it is missing |
|---|---|---|
| Branch and exact listing | Prevents comparing different locations with similar names. | Hold the comparison and verify the destination. |
| Platform and measure | Separates a public total from a filtered period count or campaign event. | Write the definition before doing arithmetic. |
| Observation date and time | Shows when the public number was actually checked. | Label it undated rather than inventing a month-end snapshot. |
| Known profile or import changes | Makes a possible discontinuity visible to the next reader. | Ask the responsible operator and record uncertainty. |
Net movement is not a list of new reviews
Consider a fictional branch with a recorded public total of 100 at the start of a comparison and 108 at the end. The arithmetic is eight more reviews in the displayed total. That is the only result the two observations establish by themselves.
They do not prove that exactly eight people posted during the interval. For illustration, ten additions and two removals could produce the same movement. That is a teaching example, not a diagnosis of what happened to a real profile. A total alone does not identify the individual changes.
Google describes several reasons that reviews may be missing or delayed, including policy checks and recently merged profiles. Use that guidance to decide what to inspect. It does not establish which explanation applies to your business, and a lower total does not automatically mean someone deleted legitimate criticism.
If you need a count of reviews published during a period, use available review records with their dates and a clear reporting definition. If the available records are incomplete, say so. Do not subtract two totals and rename the answer new customer reviews or reviews generated by this campaign.
Sources: Google Business Profile: missing or delayed reviews
Keep an unavailable snapshot visibly unknown
A blank field may mean the listing has not been checked, an import failed, the source was unavailable or the wrong location was matched. It does not mean the business has no reviews. Treating all four cases as zero can manufacture a dramatic increase the next time data arrives.
A genuine observed zero is useful evidence and should remain zero. A missing start value should remain missing. In a working table, use a separate observation-status field so colleagues can distinguish recorded zero, recorded nonzero and not recorded without interpreting formatting or cell colour.
If you only have today’s total, make today the first documented observation. Do not reconstruct the earlier value from memory or put zero in the starting column to make a formula run. Assign a date for the next check and preserve the earlier gap in the report.
Keep campaign activity beside public evidence
A QR scan, a form submission and a redirect are different recorded steps. A redirect shows that a route was opened; it does not prove a person posted a public review. A customer may stop, choose not to post or return later. A public count change also does not identify which invitation, if any, led to it.
Build a small reconciliation table with separate columns for the campaign activity you can actually observe and the public observations you have checked. Name the source of each column. Where individual attribution is unavailable, describe the relationship as an observation during the same window rather than a verified conversion.
Ripple’s configured campaign analytics can provide context for recorded journey activity. Review destinations help you inspect the intended route. Those capabilities do not turn every redirect into a completed external review. Bring the exact campaign and location scope to a product walkthrough before choosing the measure your team will report.
| Recorded event | What it supports | What it does not establish |
|---|---|---|
| Scan or page visit | The entry point recorded activity. | A new public review or a distinct paying customer. |
| Form submitted | The configured form received a submission. | External review completion or marketing permission beyond the actual consent. |
| Review destination opened | The configured route was opened. | A posted review, its rating or its author. |
| Two comparable public totals | Net movement between those observations. | The exact additions, removals or campaign attribution. |
Choose a next action that matches the evidence
When the location is unclear, verify the listing. When a field is unavailable, repair the observation or import before discussing growth. When comparable totals move, inspect the available dated review records and relevant profile changes before assigning a cause. When the campaign route is wrong, correct and test the destination before inviting more people through it.
Keep the customer invitation rule neutral while you investigate. Google prohibits selectively soliciting positive reviews and offering incentives in exchange for reviews. A measurement gap is not a reason to ask only the customers expected to leave high ratings, pressure staff into review quotas or make a benefit depend on proof of a review.
Give the action to a named role, with a source to check and a date to return. The useful outcome of this meeting may be a repaired measurement, a corrected destination or an honest unknown. It does not have to be a claimed increase in reviews.
Sources: Google Maps: genuine experiences and rating manipulation
Leave a comparison the next operator can repeat
A compact handoff can read: Same branch and platform confirmed; public total checked at two recorded times; net movement observed; individual additions and campaign attribution not established; destination owner to verify the live route before the next campaign.
Keep customer-identifying details out of a general team note. If a particular review needs attention, use the authorised workspace and its access controls. A public reply and private support follow-up also need their own status; neither should be inferred from the count column.
Use the working card in this guide to rehearse that handoff with fictional observations. It calculates a net difference only after you confirm comparability. It is a page-only planning aid, not a connected Google report, a saved Ripple record or a prediction of future results.