Google Ads is one of the Data Sources cards on https://lengrowth.com/integrations. It connects to a specific company workspace, so the integrations page first asks you to select a company. If there is no company yet, the page tells you to create one before continuing. That behavior is the same for every source on the page, and it matters because the connection is not just a general account link. It is tied to one company profile in LenGrowth.

The backend describes Google Ads as paid spend, clicks, conversions, and top campaign efficiency. The usage metadata says it is used in founder reporting paid-media metrics and existing ads recommendation and task prioritization. The most accurate way to think about the integration is that it gives LenGrowth a live paid-media signal to work with. It is not a stand-alone advertising console inside the app. Instead, it feeds the reporting and recommendation layers that already exist for the company workspace.

The setup flow is OAuth-based. On the card you connect by signing in with Google, then LenGrowth lists the accessible ad accounts and asks you to select the right one. The selected source is labeled Selected ad account in the interface. That selected account is stored for the company, which means the integration is company-specific and account-specific. If a user manages more than one Ads account, they need to pick the exact Customer ID that belongs to the business they are working on.

Before starting, confirm that the Google account you use has Standard or Admin access to the Google Ads account. The backend guidance also notes that if the user is working through a Manager account, they need to know the exact Customer ID. That is a practical setup check, not a generic permission warning. If the account cannot see the target Ads account, the select step may not show the correct option, even if the Google login itself succeeds.

Once the connection is complete, LenGrowth can show the selected ad account and sync status on the card. The integration metadata says the connection unlocks paid media reporting including ROAS, CPA, and campaign efficiency, and it also unlocks ad spend optimization tasks and budget allocation alerts. That is the key value of the integration. It lets the app use actual ad-account signals when it is deciding what the company should do next. If the source is disconnected, the app should not pretend it has live paid-media data.

The route structure matches the UI flow. Authorization starts at /integrations/google-ads/auth, account listing happens at /integrations/google-ads/accounts, the selected account is saved through /integrations/google-ads/select-account, connection state is checked at /integrations/google-ads, and disconnect uses the same base route. The page also uses the same Google sign-in label as other Google-based sources, which is why the button text is Sign in with Google instead of a generic Connect button.

If the setup fails, the first thing to verify is that the Ads account is active and not suspended. The backend guidance also recommends confirming that the user has sufficient access. That is the most common real-world problem. Another common issue is selecting the wrong ad account when more than one is available under the same login. Because LenGrowth stores the selected account name and Customer ID, the company should match the account that actually runs the business campaigns.

Google Ads is especially useful when LenGrowth needs paid-media context for a company that is actively spending. If the business does not run ads, the source will not provide useful data. If the company does run ads, the integration helps reporting stay closer to real spend and performance instead of relying on a manual summary. The backend usage metadata makes that same point by tying the source to paid media metrics and recommendation priorities.

After the account is connected, a healthy integration should show the selected ad account in the integrations card and a current sync summary instead of a disconnected state. If the company later changes ad accounts, the same card can be used to disconnect and reconnect. The company selection at the top of the page ensures the source is always tied to the right workspace rather than to an ambiguous global account.

That workspace-first design keeps reporting stable if the same user manages multiple businesses. The source always belongs to one company profile, so the company list and the selected ad account stay visible together while the user decides whether the connection is correct.

It also makes it easier to tell the difference between a correct Google login and a correct company source. The login only proves the user has access to Google; the selected account proves LenGrowth is looking at the right advertiser for the company workspace.

Related pages: