Back to integrations
Integration guide

Meta Ads integration guide

Connect Meta campaign spend to lead source performance for better source accountability.

Safe setup rule

RevenueLancer shows only masked credential status in the browser. Keep tokens, secrets, and passwords in secure server-side settings.

What this integration does

  • Fetches Meta campaign spend from a connected ad account.
  • Stores spend against mapped RevenueLancer lead sources.
  • Helps owners compare ad spend with lead activity and outcomes.

Credentials required

  • Meta access token
  • Meta ad account ID
  • Mapped campaign IDs for source reporting

Where to get credentials

  • Create a Meta app or use an approved business integration.
  • Generate an access token with ads read permissions.
  • Copy the ad account ID from Meta Business settings or Ads Manager.
  • Copy campaign IDs from Ads Manager for campaign mapping.

How to connect

  • Open RevenueLancer integrations and choose Meta Ads.
  • Save the ad account ID and access token.
  • Enable the integration.
  • Map campaign IDs to RevenueLancer lead sources before syncing.

How to test

  • Save credentials and keep the integration enabled.
  • Run manual sync from the integration page.
  • Review safe event summaries, last sync time, and last error.
  • Confirm mapped sources receive spend entries.

Common errors

  • Token expired or revoked: generate a valid Meta access token and save it again.
  • Ad account not found: confirm the ad account ID and business permissions.
  • No mapped campaigns: map campaign IDs before expecting spend rows.
  • Insufficient permissions: confirm the token has ads read access.