The Google Analytics card on the integrations page is where LenGrowth connects website traffic data to a company workspace. You will find it on the Data Sources tab at https://lengrowth.com/integrations. The page only lets you connect a source after a company has been selected, so if you see the message that says you need to choose a company first, that is expected. If no company exists yet, the page shows a call to create one before any data source can be attached.

Google Analytics is used in LenGrowth as traffic and engagement context. The integration metadata in the backend describes it as traffic and engagement context from connected website analytics, and the usage copy says it extends the shared reporting and recommendation path. The important point is that LenGrowth does not present Google Analytics as a separate analytics product inside the app. It is part of the same reporting and recommendation flow that powers company workspaces, founder reporting, and task evidence.

The connect flow is intentionally simple. On the card you can open Google Analytics, then choose the connection action that is labeled Sign in with Google. That label matters because the backend uses Google OAuth rather than a manual API key field. Once the Google authorization is complete, LenGrowth asks you to select a property. The page labels that selection as Selected property, and the list comes from the Google Analytics account summaries returned by the account picker. In other words, the integration is not finished just because the Google account is connected. You still need to choose the exact property the company should read.

Before you start, make sure the Google account you use has the right access to the GA4 property. The backend guidance says you should have Editor or Administrator access to the property, and the property should already be actively receiving data from the site. That is important because LenGrowth can only report on real connected data. If the property is empty or the account lacks permission, the authorization step may succeed while the actual property selection later fails or returns no useful data.

The page and backend together show what LenGrowth expects after the connection is complete. The integration status can show the selected property, the connected email, and a sync health summary. The backend queues an initial sync after property selection, which means the first useful data does not appear instantly. You should expect a short delay while the initial refresh runs. The integrations page also makes it clear that sync health matters, not just the connected state. A connected property with stale data is not treated the same as a current property with a healthy sync.

Google Analytics is useful in LenGrowth for two main reasons. First, it gives founder reporting traffic metrics and engagement context. Second, it gives recommendations more confidence because the product can compare a company’s activity to real traffic behavior instead of guessing. The integration usage metadata explicitly says the connection unlocks traffic and engagement sections in the Founder Report and helps growth recommendations align with actual user behavior. That is the clearest way to describe the value of the integration without overstating it.

The backend routes reflect the same flow you see in the UI. The app starts authorization at /integrations/ga/auth, gets account summaries at /integrations/ga/accounts, stores the chosen property at /integrations/ga/select-property, checks connection state at /integrations/ga, and can run reports for the selected property. There is also a dedicated data route for analytics report requests. You do not need those routes during normal use, but they explain why the connection flow is structured around OAuth plus property selection rather than a single paste-in token field.

If the setup does not work, check the most common failure points first. The backend guidance says to confirm that the Google account has the correct permissions and to clear the browser cache if the authorization popup does not appear. In practice, the most common setup mistake is selecting the wrong property or using an account that can see the Google Analytics account but not the specific property the company needs. Another common problem is trying to connect before a company exists in LenGrowth. The integrations page prevents that because the connection always belongs to a company workspace.

When the connection is healthy, the integrations page will show the source as connected and display the selected property. The sync summary should then reflect the current state of the link rather than a warning. The practical effect is that traffic data can start feeding founder reporting and the recommendation flow. If you later need to change the property, you can return to the same card, disconnect the source, and reconnect with a different Google account or a different property under the same account.

Use Google Analytics when the company needs website traffic and engagement context, especially if the goal is to understand how actual visitors behave before LenGrowth suggests the next action. If you do not yet have a live GA4 property, this integration cannot invent that data for you. It needs a real property with real access, which is exactly why the setup flow asks for a Google login and then a property choice instead of a generic token.

Related pages: