Skip to content
Merulan

Meta lead ads setup

What an operator supplies to connect the Meta lead ads Source, and the verification the provider requires.

Connecting Meta lead ads opens a Nango Connect session in the operator browser. Nango holds the credential, and Merulan holds a handle to it. An operator who holds the material below connects in one pass.

Prerequisites

Meta lead ads refuses the connection until every item holds.

  • A Meta business account with a Page whose lead forms a Pipeline reads.
  • A Page role that may approve a connected application.

Credentials

Meta lead ads stores the credential under the brokered custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. The Connect session returns a connection handle, and Merulan stores the handle rather than the token.

Scopes

Meta lead ads requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • leads_retrieval
  • pages_show_list

Meta grants lead retrieval per Page, so a Page left out of the grant returns no lead.

Verification

Broker-registered application governs the Meta lead ads connection. Meta reviews the application behind lead retrieval and grants advanced access before any live Page returns a lead.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.