Google Performance

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
Whether customers reached Google before or after a recorded reminder email
Which attributed senders generated Google reach

The reputation summary starts with Google’s reported review count and rating. When enough history is available, it may also estimate a recent-rating range. The activity sections describe customer handoffs tracked by FSRevs; 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.

Start Here

Confirm the correct Google listing is saved in My Links, with the right Place ID and location.
Open Reports > Google and choose the period and location you want to review.
Check the last update and observation dates before interpreting the review-count or rating change. A new listing needs saved history before a change can be calculated.
Read Google Visits Through FSRevs separately to see tracked handoffs. Use Request Origins or Team Contribution when the question is about requests or senders.
Select View trend for one listing when you want to investigate its rating movement.

For example, 40 Google visits and a net gain of 6 Google reviews do not establish that 6 of those 40 visitors wrote reviews. The visits can include repeat activity, and the listing’s count can also change because of activity outside FSRevs or removed reviews.

Current Report Views

Use Overview, Reputation, Activity, and Visibility to move between report sections. Reputation covers saved listing observations; Activity covers tracked FSRevs journeys; Visibility adds authenticated Google figures when connected performance is available. Older saved links can open a detailed Business Profile view directly.

For account authorization, listing associations, and reply workflows, start with Google Business Profile. For Search/Maps figures, interactions, coverage, and monthly search terms, see Connected Google Performance.

Set the Report Scope

The report can show these filters. A Review Flow filter stays hidden when its only default-scope choice would not narrow the activity:

Filter	What it changes
Date Range	Changes the saved Google comparison, chart periods, visits that occurred during the range, and the group of requests 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 request total remains the full matching request group 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

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.

The report shows when its Google data was last updated. Active periods use the latest check saved so far. Completed and custom periods expose the actual observation dates used for each comparison.

The FSRevs activity area uses 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.
Reminder Timing uses eligible Review Flow requests created during the selected date range, then compares the recorded reminder send with the first Google visit through today.

Following this group of requests 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

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

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

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

When useful, the report may show:

Estimated recent rating: 4.3–4.6 ★

Google supplies an overall rating and total review count, not the individual ratings behind the change. Because the overall rating is rounded, more than one set of new ratings may fit the same saved checks. FSRevs uses that information to calculate a possible range.

The estimate is shown only when the displayed range is no wider than 0.7 stars. A broad result such as 1.0–5.0 is hidden because it would not be useful. Even a single estimated value has an approximation sign: reviews may have been removed or changed between checks.

FSRevs does not present the middle of the range as an observed rating and never invents a confidence percentage. Use the saved review-count and rating changes as the main facts; treat this estimate as supporting context.

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

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
Visits to Google through FSRevs
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

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 Selected in a Review Flow	The customer chose Google from the review options shown in a Review Flow.
Review Flow Follow-up to Google	The customer opened the Google link shown after completing a Review Flow.
Custom Form Follow-up to Google	The customer opened the Google link shown after completing a Custom Form.
Direct Smart Link to Google	The customer opened a Smart Link that went directly to Google without starting a review request.

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 written feedback or that the customer posted publicly.

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	FSRevs sent the review request by email or text message.
Sent from a team member’s device	FSRevs prepared the request for sending from a team member’s phone or computer.
Self-started from a QR code or link	The customer started without a review request being sent first.
Other or unavailable	The available information does not show how the request began.

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.

The device-origin label identifies a handoff to a person’s app. FSRevs cannot verify whether the person sent or delivered that message, even when a later use of its request link is recorded.

Review Reminder Timing

Did Customers Reach Google Before or After the Reminder? appears when the report has a safe comparison to show. It includes Review Flow requests created during the selected range that:

Were sent through FSRevs
Had an email reminder scheduled
Later reached an included Google listing through FSRevs

Each eligible request is placed into one of two groups using its first recorded Google visit:

Timing	What it means
Before Any Reminder Email Was Sent	The customer reached Google before any reminder email was recorded as sent.
After the Reminder Email Was Sent	A reminder email was recorded as sent before the customer reached Google.

FSRevs counts a reminder as sent only when the send was recorded. For some older requests, the scheduled time was estimated from the reminder settings available when this reporting was introduced.

This comparison shows event order, not causation. It does not claim that a reminder caused a Google visit, and the section stays hidden when there is no valid comparison to present.

Read Team Contribution

Google Visits by Team Member uses Sent By attribution for system-origin requests in the selected request group. 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 requests in the matching date, Location, and Review Flow selection
Distinct requests that reached an included Google listing through today
The percentage of that sender’s requests that reached Google

Rows are ranked by requests that reached Google. The first row is marked Most Requests Reaching Google, 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 requests 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 requests. 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

Google reputation counts and ratings use saved observations. Connected Business Profile checks can supply listing totals as well as public listing monitoring. The reputation view reads saved history; connected Visibility can request Google performance data.

Reloading the reputation report does not force a fresh Google listing check. Check the displayed update date when comparing this report with the live Google listing.

Each saved checkpoint records the listing, Google’s review count and rating, and the observation time. The estimated range is calculated from those observations rather than collected from individual Google reviews.

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

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 record handoffs to Google. Google does not identify which visitors submitted a review, and some visitors may leave without writing one.

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.

Reminder Timing is not shown

The section appears only when at least one qualifying Review Flow request had an email reminder scheduled and later reached Google through FSRevs. It compares recorded event order and remains hidden when no safe comparison is available.

A sender’s percentage changed after selecting a Google Listing

The percentage is still based on all matching requests for that sender. The result count narrows to requests that reached the selected listing, so the percentage can decrease without removing the sender’s other requests.

A sender is missing from the ranking

Only system-origin requests 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 no matching requests from requests that started in the selected period but have 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.

Managing Your Links — Add and verify Google review listings
Smart Link Analytics — Analyze one Smart Link’s traffic and outcomes
Request Activity — Compare direct requests, public-link starts, and sender attribution
Team Performance — Explore completed Review Flow results linked to team members
Flow & Form Reports — Analyze one customer experience
Roles & Permissions — Understand Data access and location scope