Google Performance
What This Helps You Do
Section titled “What This Helps You Do”The Google report combines saved Google listing checks with activity tracked through FSRevs. Use it to understand:
- How review counts and listing-specific ratings changed
- How customers reached Google through FSRevs
- How requests that reached Google originally started
- Which attributed senders generated Google reach
The reputation story prioritizes facts Google supplied directly—review growth and rating movement—and may add an estimated recent-rating range when the saved checks support one. The activity sections stay separate because a tracked visit is not a confirmed public review.
Open Reports > Google. You need Data access for at least one location. The report includes only locations and listings you are authorized to see.
Set the Report Scope
Section titled “Set the Report Scope”The report can show these filters:
| Filter | What it changes |
|---|---|
| Date Range | Changes the saved Google comparison, chart periods, visits that occurred during the range, and the request cohort described below. |
| Location | Limits listings, reputation data, and FSRevs activity to locations you can access. |
| Google Listing | Limits the report to one real Google Place ID. In sender percentages, the ask total remains the full matching request cohort while reached Google counts only results for the selected listing. |
| Review Flow | Appears when there is more than one relevant Flow. It narrows FSRevs activity to the selected Review Flow requests only; it does not change the Google reputation story, headline metrics, or saved-check chart. Custom Form and direct Smart Link activity are outside a selected Flow scope. |
Date, Location, and Google Listing update the full report. Review Flow narrows FSRevs activity only. Changing Location also clears any listing or Review Flow selection that no longer belongs to that scope.
Choose a Reporting Period
Section titled “Choose a Reporting Period”The initial range is Last 90 days. You can also select daily and rolling ranges, Current Month, Last Month, This Quarter, Last Quarter, This Year, Last Year, Last 12 months, or a Custom range.
FSRevs compares checkpoints close to both calendar boundaries. For January, that normally means one monthly check nearest January 1 and one nearest February 1. A checkpoint must be within 16 days of its boundary, which supports consistent monthly collection dates without allowing an arbitrarily old starting point to be presented as January activity.
Active periods use the latest check saved so far and may say Google data through a date. Completed and custom periods always expose the actual observation dates used.
The FSRevs activity area uses two related timelines:
- Google Visits Through FSRevs counts visits that occurred during the selected date range.
- Request Origins and Team Contribution start with Review Flow requests and Custom Form responses created during the selected date range, then check their Google results through today. The report labels this boundary as Requests started or sent during the selected range; Google results through today.
This cohort view allows an older request to receive credit when its customer reaches Google later. It does not move that later visit into the selected-period visit total.
Read the Reputation Story
Section titled “Read the Reputation Story”For each listing, the report chooses the strongest concise story supported by the selected checkpoints:
- Rating improved when the Google aggregate rating rose while review count grew.
- Rating changed when the rating fell while review count grew.
- Rating maintained when review count grew and the displayed rating held steady.
- Google metrics changed when a rating moved while review count stayed equal or fell. This neutral wording avoids implying that incoming reviews caused the movement.
- No net change observed when the saved count and rating are unchanged. This does not claim that no activity occurred between checks.
The report may add one supporting estimated range, but observed facts always remain primary.
Headline Metrics
Section titled “Headline Metrics”| Metric | What it means |
|---|---|
| Net Google Review Change | Current saved review count minus the previous saved count. It is a net difference, not proof of how many customers submitted. |
| Total Google Reviews | Latest saved total across included real Google listings, counting each Place ID once. |
| Google Rating / Rating Range | Latest rating for one listing, or lowest-to-highest listing ratings when several are included. FSRevs does not average them. |
These three cards describe Google listing data. Request and visit results appear later under Google Visits Through FSRevs, where their different evidence and timelines can be explained accurately.
The Since We Started Tracking panel is a separate lifetime fact using its actual saved baseline date. It is not presented as activity from a calendar period that lacks boundary coverage.
When a selected period lacks a nearby opening checkpoint, listing details may instead show a clearly labeled Since first saved check comparison. This uses the earliest and latest saved values and always exposes their actual dates. It may span inactive service time, so it is kept separate from the selected-period headline and does not receive an “estimated recent rating.”
Google Reputation Progress Chart
Section titled “Google Reputation Progress Chart”Review-growth bars show net review-count changes for real observed intervals. Negative changes appear below zero.
When exactly one listing is selected, the chart also shows that listing’s Google rating on a fixed 1.0–5.0 scale. Missing rating intervals remain gaps. When several listings are selected, the chart shows aggregate review-growth bars only; it never overlays unrelated listing rating lines or creates an account-wide rating.
Every aggregate bar includes listing coverage. Contributions are combined only when listings were resolved against the same nominal period boundaries. Missing listing data stays unavailable rather than being treated as zero.
Use keyboard arrow keys, Home, and End to inspect chart periods. Escape clears the selection. The chart also supports pointer hover and touch selection and includes a complete screen-reader table.
Estimated Recent Rating
Section titled “Estimated Recent Rating”When useful, the report may show:
Estimated recent rating: 4.3–4.6 ★
Google supplies an aggregate rating and total review count, not the exact star distribution of unseen review activity. FSRevs accounts for the aggregate rating’s documented source precision and calculates the narrowest whole-star range compatible with both checkpoints under its versioned rounding assumption.
The estimate is shown only after conservative outward display rounding leaves a range no wider than 0.7 stars. A broad result such as 1.0–5.0 is hidden in favor of stronger observed facts. An exact result under the mathematical model still displays with an approximation sign because reviews may have been removed or changed between checks.
FSRevs never shows a midpoint as though it were observed, never clamps an impossible result, and never invents a confidence percentage.
Compare Listings
Section titled “Compare Listings”When multiple real listings or locations are in scope, the comparison table shows:
- Actual observed dates and coverage
- Starting and current review counts
- Net and percentage review growth
- Listing-specific rating transitions
- A recent-rating estimate when displayable
If the selected range has insufficient boundary coverage but a listing has older history, the row uses its clearly dated Since first saved check comparison rather than showing empty metrics. This is a long-term observed change, not a claim about the selected month.
If only one checkpoint exists, the row shows that latest saved count and rating as a starting point. Change and growth remain unavailable until a second check exists.
Choose View trend to focus the report on one listing and add its rating line to the chart. Select a listing name to open the public Google results page in a new tab. This is Google’s view of the listing and its reviews, not the FSRevs edit page or the write-a-review link.
Multiple FSRevs links with the same current Place ID are grouped so the real Google listing is counted once.
Check Individual Listings
Section titled “Check Individual Listings”Your Google Listings provides a card for every real listing in scope. Each card can show:
- Latest saved review count and Google rating
- Net review and rating change for the available comparison
- Tracked Google link clicks
- Observation count and latest saved-check date
- A displayable estimated recent-rating range
- The FSRevs links grouped under the same Google Place ID
The status badge distinguishes Tracking Normally, Building History, Temporarily Closed, Permanently Closed, and Check Needed states. A starting-point listing can still show its current saved values even when change needs another update.
The listing-name heading opens the public Google results page in a new tab. The same link behavior is available on each row in Listing Comparison.
Read Google Visits Through FSRevs
Section titled “Read Google Visits Through FSRevs”Google Visits Through FSRevs counts tracked Google destinations opened during the selected date range. Every visit counts, including repeat visits by the same customer. The summary also shows how many distinct requests or Form responses are represented and calls out direct Smart Link visits separately.
The linked distribution shows How customers reached Google. Active paths always total 100%:
| Visit path | What it means |
|---|---|
| Google chosen in a Review Flow | The customer selected Google from the Review Flow’s review destinations. |
| Google follow-up from a Review Flow | The customer opened the Google link configured as the Review Flow’s completion destination. |
| Google follow-up from a Custom Form | The customer opened the Google link configured as the Custom Form’s completion destination. |
| Direct Smart Link to Google | A Smart Link routed the customer directly to Google, outside an individual request or Form response. |
Paths with no activity are collapsed below the distribution instead of being mixed into the active percentages.
When the report says a customer opened Google and later left feedback in FSRevs, it proves the recorded order only. It does not say that the Google visit caused the private feedback, or that the customer posted publicly.
Read Request Origins
Section titled “Read Request Origins”How Requests That Reached Google Started changes the unit from visits to distinct requests. Each Review Flow request or Custom Form response created during the selected range counts once if it reached an included Google listing through today, even when it produced repeat Google visits.
The request-origin distribution classifies each reached request once:
| Start method | What it means |
|---|---|
| Sent through FSRevs | The initial request was sent using FSRevs delivery. |
| Sent from a team member’s device | A team member sent the request from their phone or computer. |
| Self-started from a QR code or link | The customer started without a recorded outbound ask. |
| Other or unavailable | Stored history does not identify one of the tracked start methods. |
This distribution answers how the request began, not which path the customer later used to reach Google. A request sent through FSRevs can still reach Google by choosing a Review Flow destination or opening a configured follow-up.
Read Team Contribution
Section titled “Read Team Contribution”Team Members Generating Google Reach uses Sent By attribution for system-origin asks in the request cohort. It does not substitute Created By, the employee the customer worked with, or the person viewing the report.
For each attributed sender with at least one result, the ranking shows:
- Total asks in the matching date, Location, and Review Flow cohort
- Distinct asks that reached an included Google listing through today
- The percentage of that sender’s asks that reached Google
Rows are ranked by asks that reached Google. The first row is marked Top contributor, but the percentage is context and is not an employee score. Small samples, customer choice, listing availability, and differences between Flows can all affect the result.
Team members with asks but no Google reach are summarized below the ranking rather than displayed as zero-result rows. Requests with missing sender information are also reported separately, including how many reached Google. Deleted historical senders remain attributable and are labeled (deleted).
Self-started requests can appear in Request Origins but do not become team-sent asks. When a Review Flow filter is active, Form responses and direct Smart Link visits are excluded because they do not belong to that Flow.
Where the Numbers Come From
Section titled “Where the Numbers Come From”Google review counts and ratings come from scheduled checks saved by FSRevs. Opening the report makes no Google provider request.
Each saved checkpoint keeps the Place ID, review count, canonical rating value, observation timestamp, and versioned source-precision interpretation. Calculated estimates are not stored; they can be reproduced from the source checkpoints if the interpretation or presentation policy changes.
First-party ratings stored on FSRevs feedback records are separate from Google ratings and are not used in this report’s Google reputation calculation.
Troubleshooting
Section titled “Troubleshooting”The Google report is missing Ask an administrator to confirm you have Data access for at least one location.
A selected period has insufficient coverage FSRevs could not find a valid checkpoint within 16 days of one or both period boundaries. Selected-period headlines and chart bars remain unavailable rather than using a misleading old baseline. Listing details may still show the clearly dated change since the first saved check.
An estimated recent rating is missing The review count may not have grown, the possible range may be too broad, source information may be incomplete, or the two checkpoints may not support an additions-only explanation. The observed review count and rating remain visible.
Visits increased but reviews did not Visits only confirm that customers reached Google. Google does not identify which visitors submitted a review.
The visit total and reached-request total differ They use different units and timelines. Visits count every Google opening during the selected range, including repeats and direct Smart Links. Request Origins counts distinct requests created during the range that reached Google through today.
A sender’s percentage changed after selecting a Google Listing The ask denominator remains the full matching sender cohort. The result count narrows to asks that reached the selected listing, so the percentage can decrease without removing the sender’s other asks.
A sender is missing from the ranking Only system-origin asks with Sent By attribution and at least one Google result receive a row. Zero-result senders and missing attribution are summarized below the ranking. Self-started requests remain in Request Origins instead.
No activity sections are shown The report distinguishes an empty filtered scope from an active request cohort that has not reached Google yet. Try a wider date range or a different Location, Review Flow, or Google Listing. If requests are active, results appear after a tracked Google destination is opened.
Related Pages
Section titled “Related Pages”- Managing Your Links — Add and verify Google review listings
- Smart Link Analytics — Analyze one Smart Link’s traffic and outcomes
- Flow & Form Reports — Analyze one customer experience
- Roles & Permissions — Understand Data access and location scope