Meta Ads is one of the data source cards on https://lengrowth.com/integrations. The page keeps the same company-first rule for this source as it does for Google Analytics, Search Console, and Google Ads. You must pick a company workspace before you can connect the account, and if there is no company yet, LenGrowth tells you to create one first. That company requirement is important because the connection is stored against a specific company rather than a global user profile.

The integration metadata describes Meta Ads as paid social spend, clicks, conversions, and top campaign efficiency. The backend usage text says it feeds founder reporting paid-media metrics and existing ads recommendation and task prioritization. That means the source is used to support the same reporting and recommendation workflow as the other ad integrations, but for Meta instead of Google. The app is not trying to become a separate ads manager. It is using real account data to improve the company’s reporting and next-step guidance.

The connection flow is OAuth-based. On the integrations page, the visible button label is Sign in with Facebook because the code detects Meta or Facebook as the provider for the OAuth flow. After authorization, the page lists the available ad accounts and asks you to select the one that belongs to the business. The selected source is shown as Selected ad account. That is the key moment in the setup because the Google or Facebook login alone does not choose the business account for you.

Before connecting, make sure the user has Admin or Advertiser access to the Meta Ad Account. The backend guidance says that access must be granted through Facebook Business Manager. That is the permission gate the code relies on. If the user cannot see the correct ad account during selection, the issue is usually that the Facebook login does not have enough access or is logged into the wrong business identity.

The page also makes a distinction between connection state and usability. The card can show whether the source is connected and whether a selected ad account is present. A healthy connection should display the selected account name or account ID and a sync summary. If the company changes ad accounts, the same card can be used to disconnect and reconnect, so the integration remains attached to the correct business source.

Meta Ads unlocks the same kind of output that Google Ads does, but for paid social. The usage metadata says the connection can support social ad performance metrics, lead-gen tracking, audience effectiveness analysis, and creative optimization tips. That is the best grounded summary of what the source is for. It gives LenGrowth a paid social signal that can be blended into reporting and task logic when the business is actively running ads.

The backend routes follow the same pattern you see on the page. Authorization starts at /integrations/meta-ads/auth, the account list comes from /integrations/meta-ads/accounts, the selected account is saved through /integrations/meta-ads/select-account, connection status is checked at /integrations/meta-ads, and disconnect uses the same base route. Those routes confirm the integration’s shape: OAuth, account selection, and company-level persistence.

The backend guidance also notes that setup typically takes a couple of minutes. The practical time is not the main issue though. The real issue is making sure the right account is selected. If the business uses more than one ad account, the wrong choice can make reporting look like it is missing or stale even though the connection is technically healthy. The selected account label in the UI helps avoid that problem by showing exactly what LenGrowth is currently using.

If setup fails, check the Facebook account, the Business Manager permissions, and whether the correct ad account is active. The guidance says to confirm that the ad account is not blocked by business policies or a restricted environment. It also recommends checking that the user is logged into the right Facebook account before starting the connection. Those are the concrete issues the integration code is designed around.

Use Meta Ads when the company’s growth work depends on paid social performance. If there are no active campaigns, the source will not add much value. If campaigns do exist, LenGrowth can use the account to ground reporting and recommendations in actual spend and conversion signals instead of generic assumptions. That is the practical reason this card exists on the integrations page.

The selected account label is the clearest signal that the current Facebook authorization is tied to the right advertiser. When a team works across more than one brand or more than one business manager, that confirmation helps prevent a silent mismatch between the connected source and the company being analyzed.

Related pages: