Meta (Facebook & Instagram) Lead Connector

Q: Does one connection cover both Facebook and Instagram?

Yes. You connect a Meta Page, and Lead Ads running under it on both Facebook and Instagram flow into REDA through the same connection. The lead record's Ad Publisher Platform field records which one each came from.

Q: Which button connects a Meta account?

One button — Connect Ad Account — on the Ad Account record. You choose Meta in the Advertising Platform field first; the same button handles both Meta and Google.

Q: What is the Page ID / Lead Webhook Key for Meta?

For Meta it's your Facebook Page ID. It's the routing key that tells REDA which connected org a given Page's leads belong to, which is why a Page can only be connected to one org at a time.

Admin 8 min read Updated July 2026

A prospect scrolling Facebook or Instagram taps your ad, fills in the instant form that opens over it, and never leaves the app — that's a Meta Lead Ad, and it's one of the fastest ways to capture interest. The Meta Lead Connector brings those submissions straight into REDA: connect a Meta Page once, and every Lead Ad running under it — on both Facebook and Instagram — arrives as a captured lead with the campaign, form, and platform details your reports need. This article is for the administrator who sets up the connection and the agents who work the leads. It covers what you need on the Meta side, how to connect and disconnect a Page in REDA, where the lead and its attribution land, and where to go for conversion reporting.

Getting there. Open the App Launcher (the grid icon at the top-left of any page) and choose the Ad Account tab. Each connected Meta Page is one Ad Account record; that record is where you connect, disconnect, and see the connection's status.
Access you'll need. Managing ad connections is administrator work. On OEM orgs, ask your administrator to assign the REDA - Ads Integration permission set, which grants the Ad Account tab, the record, and the Connect and Disconnect buttons. On ISV orgs there is no Ads permission set — assign REDA - Master Data - Admin instead, which grants the same Ad Account object access and tab. Agents who only work the leads need their normal read access to the lead record.

A note on wording for your edition. REDA ships in two editions, and the lead and campaign records are named differently in each. On OEM orgs the captured lead is an Inquiry and campaign attribution is a Promotion; on ISV orgs the captured lead is a standard Lead and campaign attribution is a Campaign. This article calls out the difference where it matters; everything else works the same in both.

Using REDA Sales Cloud edition? This article shows the Platform edition, where prospects are Inquiry records (the standard Salesforce Lead in Sales Cloud) and leasing promotions are Promotion records (a standard Campaign with the “Leasing Promotion” record type). Everything else — the fields, the steps and the behaviour — is the same unless noted. See REDA editions.

How it works

The connector links three things: your Meta Page, the Lead Ads running under it, and a REDA Ad Account record that ties them together. Once connected, the flow is hands-off:

A prospect submits your Lead Ad form. On Facebook or Instagram they open your ad's instant form and send their details to Meta.

Meta hands the lead to REDA's delivery service. Because the Page is connected, Meta forwards each new lead to REDA, which routes it to your org by the Page it came from.

REDA creates the lead record. A new lead — an Inquiry on OEM, a Lead on ISV — is created with the prospect's answers filled in.

Attribution is stamped on. The connector records which account, campaign, and lead form produced the lead, and whether it came from Facebook or Instagram, so marketing can trace it back to the ad that earned it.

The Page only needs to be connected once. From then on new leads flow in on their own, and you work them in REDA exactly like any other lead.

What REDA runs on your behalf. The Meta app, its review and approvals, and the secure sign-in that connects your Page are all built and operated by REDA — there is nothing to create or submit for review on the Meta developer side. Your part is a Meta Page with Lead Ads and the right to manage its leads, plus granting consent when you connect. Everything past that point is handled for you.

What you need on the Meta side

Before connecting, make sure the Meta side is ready. These are things you manage in Meta Business tools, not in REDA:

You'll need	Why
A Meta Page	The Facebook Page your Lead Ads run under. You connect the Page — not each ad — and its leads flow into REDA.
Your Facebook Page ID	The Page's identifier. It doubles as the routing key REDA uses to send that Page's leads to your org, so you'll record it on the Ad Account.
Lead Ads with an instant form	The Lead Ad and its instant form that collect the prospect's details. Their submissions are what flow into REDA — no Lead Ads, no leads.
The right to manage the Page's leads	Sign in to connect with a Meta user that can administer the Page and its leads, so the consent step can grant REDA access to receive them.

If you're not sure of your Page ID or whether your ads are set up as Lead Ads, your Meta Business administrator or media agency can confirm both.

One Page, one org. A Meta Page can deliver its leads to only one REDA org at a time — the Page ID is the routing key that decides where they go. If a Page is already connected somewhere else, you'll need to disconnect it there before connecting it here (see Moving a Page to another org).

Setting up the Meta side (in Meta Business)

These steps happen in your Meta Business tools — the work your marketing admin does on your own Page and Business Portfolio so leads are ready to flow. You never create a Meta app, submit anything for App Review, or handle an app secret: REDA operates the shared connection service and its Meta app on your behalf. Your part is getting the Page ready and granting access.

Confirm your Page and admin role. In business.facebook.com → Business Settings, confirm you're an admin of the Business Portfolio that owns the Page you advertise from, and note the numeric Page ID (Accounts → Pages → your Page). Instagram lead ads are delivered through the connected Facebook Page — there's nothing separate to set up for Instagram.

⭐ Grant REDA lead access in Lead Access Manager — the single most important Meta step. In Business Settings → Integrations → Lead Access, select your Page and, under CRMs, grant lead access to the REDA connector. Also confirm page-level lead access for the user who'll run Connect. If you skip this, Meta accepts your leads but never delivers them — the test tool shows them stuck in "Pending" and nothing reaches REDA.

Create and publish your Lead (Instant) Form. In Meta Ads Manager (or Page → Publishing Tools → Instant Forms), build your instant form using standard question types where you can (email, phone, name) so they map straight to your lead fields; extra questions are preserved on the captured lead for reference. Publish it and attach it to a live ad or campaign.

Grant the REDA app access during Connect. When your admin clicks Connect Ad Account in Salesforce, a Meta sign-in opens; log in as a Page admin and authorize the REDA app to receive the Page's leads. One Page connects to one org. Everything the sign-in relies on is operated by REDA.

What you do vs. what REDA handles. You keep a Page running Lead Ads, grant REDA lead access in Lead Access Manager, publish your instant form, and authorize the Page during Connect. REDA operates the shared connection service, its Meta app and reviews, the secure sign-in, and all the credentials behind it — there is nothing to create or submit on the Meta developer side and no secret for you to manage.

Golden rule: no Lead Access, no leads. If everything else looks right but leads aren't arriving — or Meta's test tool shows them stuck on "Pending" — come back to Lead Access Manager first. It's the most common cause.

Connecting a Meta Ad Account

Connecting is done once per Page, from a single Ad Account record. There is one connect button, shared by Meta and Google — you tell REDA which provider this record is for by setting the Advertising Platform field.

Create an Ad Account record. On the Ad Account tab, create a new record and give it a recognizable name (for example, "Meta — Downtown Leasing").

Set Advertising Platform to Meta. This is the one required field, and it tells REDA to run the Meta connect flow. Also fill in the Ad Account ID with your Meta ad-account id, and the Manager / Business ID if your Page sits under a Meta Business.

Set the routing details. Put your Facebook Page ID in the Page ID / Lead Webhook Key field — for Meta this is the routing key — and fill in the Webhook Base URL (Site). Your administrator provides the base URL; the Page ID comes from Meta.

Click Connect Ad Account. A new window opens and hands off to REDA's secure connect flow, then to Meta to sign in and grant consent for the Page. When it returns, the Ad Account shows Active and a Connected Date, and a protected connection token is stored on the record for you.

Leave the managed fields alone. The Connection Token and Token Expiry fields are set for you by the connect flow and hold encrypted credentials. Never edit or clear them by hand — doing so breaks the connection. If a connection ever needs resetting, use Disconnect Ad Account and connect again.

Disconnecting and moving a Page to another org

To end a connection, open the Ad Account and click Disconnect Ad Account. For Meta, disconnecting does two things that matter: it releases the Page's routing so the Page can be connected to a different org, and it stops that Page's leads from flowing into this org. REDA then clears the stored token and sets Active to false.

The button fails safe — if the release can't complete, the account stays connected rather than ending up in a half-disconnected state, and you're shown a LOG-#### support reference you can quote to support. Disconnecting is always safe to retry. Because a Page routes to just one org at a time, this release step is exactly what you use when you need to move a Page: disconnect it where it lives now, then connect it in the new org.

Turning capture on

One org-wide switch governs whether Meta leads are ingested at all: Meta Lead Ads Enabled. It must be on for submissions to flow in, and it acts as a master pause — turn it off and REDA stops accepting Meta leads across every connected Page without you having to disconnect anything. Your administrator controls it; if leads aren't arriving even though a Page shows Active, this switch is the first thing to check.

Where the lead and its attribution land

Each Lead Ad submission becomes one lead record — an Inquiry on OEM orgs, a standard Lead on ISV orgs — with the prospect's answers filled in and a set of attribution fields stamped on so you can trace the lead back to the ad that produced it:

Field	What it tells you
Ad Platform	The source — `Meta`.
Ad Publisher Platform	Which surface it came from — `facebook` or `instagram`.
Ad Account	A link to the Ad Account record that produced the lead.
Ad Campaign Id	The Meta campaign the ad belonged to.
Ad Form Id	The instant form that was submitted.
Web fbclid	The Meta click ID — the key that lets a later conversion be matched back to this click.
Ext Lead Id	Meta's own ID for the lead. REDA uses it to avoid creating the same lead twice.
Ad Unmapped Answers	Any custom-question answers from your form that don't have a dedicated field, kept together for reference.

These fields are not on your page layout yet. A managed-package upgrade never places a field on a layout you own, so the connector can populate Ad Platform, Ad Account, Ad Campaign Id, Ad Form Id and Ext Lead Id on a record where you cannot see any of them. Verified on a captured lead: every one of them held a value while only Web gclid appeared on the layout. Add the ones you want visible — Setup → Object Manager → the lead object → Page Layouts → drag them into a section — before concluding the attribution did not arrive.

Campaign attribution. On OEM orgs, if the Ad Account has a Promotion set, that Promotion is stamped onto the new Inquiry so it rolls up to the right leasing promotion. On ISV orgs, the Ad Account carries a Campaign instead, and the connector links the new Lead to that Campaign as a member. Either way, the lead is tied to the marketing effort that earned it.

These fields are read-only for agents. The attribution fields are written by the connector and shown to your team for reference — they're not meant to be edited by hand. Agents work the lead itself (contacting the prospect, qualifying, converting) exactly as they would any other lead.

Reporting conversions back to Meta

Capturing the lead is half the loop; the other half is telling Meta when that lead turns into business, so Meta can optimize toward the ads that actually produce customers. That closed-loop step — sending the conversion back through Meta's Conversions API (CAPI), matched by the Web fbclid captured here — is covered on its own page, along with the Dataset (Pixel) ID and conversion token it needs.

See Closed-loop Conversions & Conversion Target for the full walkthrough.

Where to go next

Ads Connector Overview — how the whole connector fits together, across Meta and Google.
Ads Connector Setup — the one-time admin setup: permission set, page-layout fields, and delivery settings.
Google Lead Connector — the same capture path for Google Lead Forms.
Closed-loop Conversions & Conversion Target — send conversions back to Meta when a lead becomes business.
Ads Connector Troubleshooting — for "Page already connected", missing leads, and connection failures.

Frequently asked questions

Yes. You connect a Meta Page, and Lead Ads running under it on both Facebook and Instagram flow into REDA through the same connection. The lead record's Ad Publisher Platform field records which one each came from.

One button — Connect Ad Account — on the Ad Account record. You choose Meta in the Advertising Platform field first; the same button handles both Meta and Google.

For Meta it's your Facebook Page ID. It's the routing key that tells REDA which connected org a given Page's leads belong to, which is why a Page can only be connected to one org at a time.

The Page is still connected to another REDA org. Disconnect it there first — Disconnect Ad Account releases the Page so it can be connected elsewhere — then connect it here. See Ads Connector Troubleshooting.

Was this article helpful?