Performance Metrics Dictionary

Views, search terms, calls, website clicks, direction requests, and booking interactions describe different behaviors.

Primary focus: performance metrics
Series: Chamko Marketing — Google Business Profile field guide

The specific problem

Views, search terms, calls, website clicks, direction requests, and booking interactions describe different behaviors. None should automatically be counted as a sale. Define each metric according to the current Google interface and do not combine unlike actions into a single lead total.

Diagnose the underlying facts

Search-term reports may be aggregated or incomplete. Use phrases as clues about customer language rather than exact search-volume evidence. Compare equivalent periods and annotate holidays, moves, campaigns, hour changes, and website updates.

Build a controlled workflow

Connect profile interactions to call logs, bookings, orders, and CRM records where possible. UTM parameters help identify web traffic but do not close all attribution gaps. A call click is not a connected call, and a connected call is not necessarily qualified.

Applied scenario

An optician sees website clicks rise but bookings remain flat; the team tests the mobile booking path before blaming traffic quality.

Action checklist

Check the actual operating facts for performance metrics before editing the public profile.
Assign an owner and retain a dated record for the performance-metrics workflow.
Use the current official workflow appropriate to performance metrics; do not substitute an unrelated appeal or edit path.
Test the customer journey for performance metrics from a normal Search or Maps session.
Reconcile performance metrics with the real operation and the relevant approved source record.
Schedule another performance metrics check after the next material operational change.

FAQs

Are views unique people?

Use Google’s actual definition. Do directions prove arrival.

No. Can months be compared?

Yes, but account for seasonality and changes.

Official Google references

The documents below are the primary platform references for performance metrics; check the account-specific controls before carrying out this workflow.

Scope note

This article about performance metrics describes a verification process; it cannot promise a Google decision, search position, or commercial outcome for a particular location.

For performance-metrics, define a fallback action for cases where the official interface does not offer the expected control, with a performance-metrics note saved before the next profile update.

An accurate performance metrics workflow avoids collecting personal information that is irrelevant to the decision, with a performance-metrics note saved before the next profile update.

Keep the performance-metrics procedure short enough that a busy location manager can follow it without improvising, with a performance-metrics note saved before the next profile update.

For performance metrics, record the person responsible for follow-up as well as the person who made the original edit, with a performance-metrics note saved before the next profile update.

The performance-metrics review should consider whether the website, phone system, and profile tell the same story, with a performance-metrics note saved before the next profile update.

When facts remain uncertain in performance metrics, pause a high-impact edit and request clarification rather than guessing, with a performance-metrics note saved before the next profile update.

For performance-metrics, verify the result after processing because a successful submission may not equal public publication, with a performance-metrics note saved before the next profile update.

The performance metrics owner should explain any genuine exception instead of silently copying another branch’s values, with a performance-metrics note saved before the next profile update.

Use the performance-metrics audit to identify a repeatable prevention rule, not only to close the current ticket, with a performance-metrics note saved before the next profile update.

For performance metrics, store evidence in a business-controlled place that remains available after staff turnover, with a performance-metrics note saved before the next profile update.

The performance-metrics checklist should be revisited whenever the business changes address, ownership, services, or operating model, with a performance-metrics note saved before the next profile update.

A useful performance metrics report describes the limitation of its data alongside the observation it records, with a performance-metrics note saved before the next profile update.

For performance-metrics, keep customer communication factual and avoid promising an outcome that the business cannot control, with a performance-metrics note saved before the next profile update.

The performance metrics process should separate urgent customer-impacting errors from lower-risk editorial improvements, with a performance-metrics note saved before the next profile update.

Close the performance-metrics task only after recording the public result and any remaining unresolved dependency, with a performance-metrics note saved before the next profile update.

For performance-metrics, the first review question is which real-world fact the profile is expected to represent, with a performance-metrics note saved before the next profile update.

The performance metrics owner should write down what evidence would disprove the current assumption, not only what supports it, with a performance-metrics note saved before the next profile update.

Before changing performance-metrics, compare the customer-facing display with one independent operational record, with a performance-metrics note saved before the next profile update.

A useful performance-metrics audit distinguishes an observed fact from a hypothesis about why Google displays it, with a performance-metrics note saved before the next profile update.

If a team member cannot explain the performance metrics decision, the internal handover notes need more context, with a performance-metrics note saved before the next profile update.

The performance-metrics workflow should identify who can approve an exception when the normal owner is unavailable, with a performance-metrics note saved before the next profile update.

For performance metrics, a dated screenshot can document what customers saw, but it does not establish the cause, with a performance-metrics note saved before the next profile update.

When reviewing performance-metrics, avoid using competitor behavior as a substitute for evidence about this business, with a performance-metrics note saved before the next profile update.