Skip to main content

Introduction

Google Business Profile (formerly Google My Business) is Google’s platform for managing how a local business appears across Google Search and Google Maps. It captures how customers discover and interact with a business listing — impressions on Maps and Search, calls, website visits, direction requests, bookings, food orders, and messages — as well as the star ratings and text reviews customers leave. The connector exposes two kinds of data through a single data source. Performance metrics (impressions, clicks, calls, and other actions) are read live from the Business Profile Performance API for the selected date range. Reviews (individual ratings, reviewer details, and owner replies, plus the location’s lifetime average rating and total review count) are synced from the My Business API into an Adriel-managed cache. One data source is created per business location. As a local-performance connector, impressions, actions, and review data are standardized so widgets can aggregate alongside other sources without additional configuration. To connect this data source, see How to connect Google Business Profile to Adriel.

Data refresh strategy

This connector combines two data modes with different refresh behavior. Performance data is fetched live; review data is cached and refreshed on a schedule.

Architecture data

Architecture covers the Account → Location hierarchy used to identify the business. Accounts and locations are listed from the My Business Account Management and Business Information APIs when the connection is established and when a business is selected. Each selected location becomes one Adriel data source.

Reports data

Reports data follows two paths depending on the metric:
  • Performance metrics (impressions, calls, website clicks, direction requests, bookings, food orders, menu clicks, conversations) are fetched on demand. Each dashboard load issues a live request to the Business Profile Performance API for the selected date range and daily granularity; these values are not cached. Daily rows are then aggregated in memory to the requested breakdown (day, week, month, or business).
  • Reviews are synced into an Adriel-managed cache and refreshed nightly at 3:00 AM UTC. New reviews are inserted and existing reviews are updated in place, keyed on the review ID (an UPSERT strategy), so edited reviews and newly added owner replies are reflected on the next refresh. After the initial full sync, refreshes fetch only recently updated reviews. The location’s lifetime average rating and total review count are read live from the reviews API at query time rather than from the cache.

Architecture levels

Account → Location An Account groups the locations a user manages. A Location is a single business listing (a storefront or service area) and is the reporting boundary in Adriel. Connecting a business provisions one Adriel data source per location selected.

Date range limits

The performance API is queried live per request, so wide daily ranges are capped to keep query sizes manageable: Ranges beyond these caps are truncated, and data outside the window may not appear. No monthly cap is documented for this connector.

Metrics

Google Business Profile is a schema-flexible source. The fields below are the standard fields Adriel exposes; the exact fields you can report on depend on your Google Business Profile data. Data type uses Adriel’s vocabulary; API Key in code style is the literal source field; italic marks a value Adriel derives.

Google Business Profile fields

Date Calculation

Breakdowns

Google Business Profile fields

General

Date

Limitations

Based on the current connector, Google Business Profile has:
  • Two data modes with different freshness — performance metrics are live but reviews refresh once nightly (3:00 AM UTC), so a review left during the day appears the following morning.
  • A 93-day cap on daily performance queries and a 1-year cap on weekly queries — wider ranges are truncated and data outside the window may not appear.
  • Live aggregate review metrics — average rating and total review count are read from the reviews API at query time (not from the review cache) and reflect the location’s lifetime totals, not the selected date range.
  • A cached review store of up to 50,000 rows per location — locations with more reviews than the cache limit may not surface every historical review.
  • Anonymous and reply fields may be empty — reviewer anonymity is recorded per review, and reply fields are empty when the owner has not responded.
  • One data source per location — reporting across multiple locations requires one data source per business.

API references

See also