Google Business Profile is a Data Sources card on https://lengrowth.com/integrations. Like the rest of the integrations page, it attaches to a selected company workspace, so the user has to choose a company before the connection can proceed. If there is no company yet, LenGrowth asks the user to create one first. This is the same company-selection rule used across the other source cards, and it keeps local-business signals tied to the right workspace.

The backend usage metadata describes Google Business Profile as local review quality, profile completeness, and profile action signals. It says the source is used in founder reporting local-presence sections and existing task creation for local reputation and profile improvements. That is the most accurate way to frame the integration. It is meant for local or hybrid businesses that want LenGrowth to see their business listing as a working source of truth.

The connect form on the integrations page uses two visible fields: Location ID and Access token. The placeholder for the Location ID shows the expected structure as accounts/123/locations/456. That is an important clue because it tells the user that the app is expecting a specific business location resource, not a generic business name. The frontend API posts those values to /integrations/google-business-profile/connect.

Before connecting, the backend guidance says to use a Google Business Profile admin who can view the exact location LenGrowth should monitor. It also says to gather both the location ID and a valid access token before starting the connection. The integration is therefore built around location-specific access rather than a broad Google login. If the wrong location is used, LenGrowth will attach to the wrong business profile and the reporting will no longer match the company’s real local presence.

The backend guidance also tells the user where to find the source of truth: in the Google Business Profile account, locate the correct business location in the managed locations list, then use the connected admin tooling or API setup flow to retrieve the location resource ID and access token. Those are the real setup prerequisites. The app does not invent them. It expects the user to bring a valid location ID and token from the Google Business Profile side.

Once connected, the integrations page can show the selected location and sync state. The backend metadata says the connection unlocks local reporting for review quality, profile actions, and profile completeness. It also says local-presence tasks can stop waiting on profile access once LenGrowth can sync the right business listing. That means the integration is useful when a business wants to understand how its public listing is performing and what operational work may be needed to improve it.

The API route pattern is the same as the other manual-credential integrations. Setup uses /integrations/google-business-profile/connect, connection state uses /integrations/google-business-profile, and disconnect uses the same base route. The connect call also accepts optional metrics fields for website clicks, direction requests, phone calls, search views, and maps views. The current UI mainly asks for Location ID and Access token, but the backend record can store those profile-action metrics as part of the connection.

If setup fails, the backend guidance says to double-check that the location ID matches the exact location the company wants monitored. It also says to refresh the access token and reconnect if the token expired or was created for a different Google account. Those are the two real failure points. Because the integration is location-specific, a token that belongs to the wrong business or the wrong location will not help LenGrowth report on the right listing.

Use Google Business Profile when the company depends on local discovery, map visibility, reviews, or profile actions. If the company has no local presence, the integration is less useful. If the company does have a local or hybrid presence, the source gives LenGrowth a grounded way to connect local reputation and profile behavior to reporting and task creation.

The page is also helpful because it tells the user exactly which kind of credential belongs in the form. The location ID and access token pair is specific enough that the team can verify the source before saving it. That makes the setup less ambiguous for local businesses that manage more than one location or work with an agency that owns several Google accounts.

If the business operates multiple storefronts or offices, that explicit location ID is the safest way to avoid mixing one branch’s listing with another. LenGrowth only gets the right local story when the exact location resource matches the company it is supposed to represent.

That is why the location resource is part of setup, not an afterthought.

Related pages: