Ads Connector: Setup & Enablement

Q: Does connecting an account need the REDA_Router remote site?

No — connecting is a browser redirect. Only Disconnect Ad Account calls the router, so the REDA_Router remote site must be active for disconnects to succeed.

Admin Setup walkthrough 9 min read Updated July 2026

This is the one-time, per-org setup an administrator does to switch the REDA Ads Connector on. It covers installing the package, giving the right people access, putting the Ad Account tab and its fields in front of them, exposing the attribution and conversion fields on your lead records, and loading the small set of platform settings the connector needs. Work through it in order — later steps assume the earlier ones are done. For what the connector actually does once it's on, see REDA Ads Connector: Overview.

Which edition are you on? Setup is nearly identical across editions, but two things differ: your lead records are Inquiries on REDA One (OEM) or standard Leads on REDA on Sales Cloud (ISV), and the permission set described in Step 2 ships only on OEM (on ISV the same access comes from REDA - Master Data - Admin). Each step below calls out the edition difference where it matters.

This is the Salesforce side. There's a Google/Meta side too. This article covers what your administrator sets up inside Salesforce. Separately, your Google Ads or Meta marketing admin makes sure the ad side is ready to send leads — a live Google Lead Form or a Meta Page running Lead Ads, and granting access during Connect. Those platform-side steps are in Google Lead Connector and Meta Lead Connector. You never register an app or handle a secret on either platform — REDA operates the shared connection service.

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.

Before you begin

You need System Administrator access (or an equivalent profile) to install packages and edit Setup.
You'll be working in Salesforce Setup throughout — permission sets, tabs, page layouts, remote site settings, and custom metadata.
Authentication is handled entirely by REDA and by the self-service Connect flow. You never register apps with Google or Meta, and you never handle app credentials or secrets. When an administrator clicks Connect Ad Account, they sign in to your own Google or Meta account and grant access; REDA provisions the connection behind the scenes. Those steps are noted so you know what to expect and what not to touch.

Step 1 — Install the package

Install the edition-appropriate REDA managed package into your org. The connector's objects, tab, buttons, remote site settings, and automation all arrive with the package — you're enabling and exposing them in the steps that follow, not building them.

Which edition am I installing? Install the package your org is licensed for — REDA One (OEM) or REDA on Sales Cloud (ISV). Your REDA contact supplies the install link, and for the ISV package an install password as well. If you are not sure which edition you have, check where captured leads land: an Inquiry record means OEM, the standard Lead object means ISV.

Step 2 — Grant access to the connector

Decide who manages ad connections. Two personas matter:

Ad administrators — the people who create Ad Account records and run Connect Ad Account / Disconnect Ad Account / Select Conversion Target. They need full access to the connector.
Lead workers — everyone who only views and works the captured leads. They need normal read access to your lead records (Inquiry or Lead); they don't need anything connector-specific, because the attribution fields are populated for them automatically.

On REDA One (OEM): assign the packaged permission set to your ad administrators.

Permission set	API name	What it grants
REDA - Ads Integration	`REDA_Ads_Integration`	Create/read/edit/delete on the Ad Account object, the three Ad Account buttons and their pages, the Ad Account tab, and read access to the ad-related fields.

The ad fields are granted read-only — and two things aren't in the permission set at all. By design, the permission set grants the ad fields as read-only, because the connector writes them itself in the background. That has two consequences you must handle manually:

The Advertising Platform picklist is required when an admin creates an Ad Account, but it isn't individually granted for editing by the permission set. Make sure your ad administrators can edit it through their profile or a supporting permission set.
The Inquiry conversion fields — Is Converted, Conversion Sent, Conversion Sent Datetime, and Conversion Last Value — are not in the permission set. They rely on your admins' existing Inquiry access. Confirm your ad administrators can see (and, for Is Converted, set) these on the Inquiry.

On REDA on Sales Cloud (ISV): there is no separate Ads permission set, and none is needed — the access is already part of REDA - Master Data - Admin, which grants create, read, edit and delete on the Ad Account object and turns the Ad Account tab on. Assign that set to your ad administrators. Your end users do not need it: REDA - Property Sales User, REDA - Property Leasing User and REDA - Property Acquisition User already carry read access to Ad Account records. As on OEM, confirm before go-live that your ad administrators can edit Advertising Platform and can run all three Ad Account buttons.

Step 3 — Add the Ad Account tab

Make the Ad Account tab visible so administrators can find and manage Ad Account records. On OEM the REDA_Ads_Integration permission set already makes the tab visible to anyone it's assigned to; on ISV, REDA - Master Data - Admin does the same. Optionally add the tab to the app your ad administrators use day to day so it's one click away.

Step 4 — Put the fields and buttons on the Ad Account layout

Open the Ad Account page layout (or Lightning record page) and surface the fields an administrator uses to set up and connect an account:

Field	Why it's on the layout
Advertising Platform	Required. Google or Meta — decides which platform Connect signs into.
Ad Account ID	The Google customer account ID or Meta ad-account id.
Manager / Business ID	The Google manager account or Meta business id, where applicable.
Page ID / Lead Webhook Key	For Meta, the Facebook Page ID; for Google, the shared lead key.
Webhook Base URL (Site)	The base address leads are delivered to.
Conversion Target	Where conversions are reported (Google conversion action, or Meta dataset/pixel).
Conversion Token (Meta CAPI)	Meta only — the token used to send conversions to Meta.
Active and Connected Date	Read-only status set by Connect/Disconnect — useful to display.
Promotion (OEM) / Campaign (ISV)	The campaign this account attributes its leads to.

Then add the three buttons to the layout so administrators can run the connection lifecycle from the record:

Connect Ad Account — authorizes the account with Google or Meta.

Select Conversion Target — picks where conversions are reported.

Disconnect Ad Account — ends the connection and frees the account.

An Ad Account record page in Salesforce showing the Connect Ad Account, Select Conversion Target and Disconnect Ad Account buttons, with the setup fields on the layout below - Advertising Platform Google, Ad Account ID, the Connection section with Active ticked and a Connected Date, Lead Routing with the Page ID and Webhook Base URL, and the Conversions section - credential values blurred for publication.

In Salesforce, an Ad Account record page showing the three action buttons in the highlights panel — Connect Ad Account, Select Conversion Target, and Disconnect Ad Account — with the setup fields (Advertising Platform, Ad Account ID, Page ID / Lead Webhook Key, Webhook Base URL) visible on the layout below.

Don't expose the connection token for editing. The Ad Account holds an encrypted connection token that Connect sets and manages. Keep it off editable layouts — it should never be typed, pasted, or hand-edited.

Step 5 — Expose attribution and conversion fields on your lead record

So your team can see where a lead came from — and so conversions can be reported — add the connector's fields to your lead record's page layout. On REDA One (OEM) that's the Inquiry layout; on REDA on Sales Cloud (ISV) it's the standard Lead layout.

Attribution fields (both editions) — add these as read-only; the connector fills them in:

Ad Account, Ad Account Id, Ad Campaign Id, Ad Form Id
Ad Platform, Ad Publisher Platform
Web gclid, Web fbclid
Ext Lead Id, Ad Unmapped Answers

Edition	Add these conversion fields	To which record
REDA One (OEM)	Is Converted, Conversion Sent, Conversion Sent Datetime, Conversion Last Value	The Inquiry layout (the closed loop is driven from the Inquiry).
REDA on Sales Cloud (ISV)	Conversion Sent, Conversion Sent Datetime	The Opportunity layout (the value comes from the standard Opportunity Amount).

Why conversion fields aren't in the permission set (OEM). The OEM permission set covers the attribution fields but not the conversion fields, so your admins see and set them through their existing Inquiry access — that's expected, and it's why Step 2 asks you to confirm that access.

Step 6 — Confirm the router remote site (for Disconnect)

The Disconnect Ad Account action needs one specific remote site to reach REDA's routing service and release the connection. Connecting doesn't need it (Connect is a browser redirect), but disconnecting does.

Remote Site Setting name	Needed for
`REDA_Router`	Disconnect Ad Account — releasing the connection on REDA's side.

If Disconnect fails, check this first. Without an active REDA_Router remote site, Disconnect can't reach the router and will fail safe (the account stays connected). If a disconnect returns a support reference, confirm this remote site exists and is active, then retry.

Step 7 — Confirm the connector's remote sites

The package ships five remote site settings the connector uses. Confirm all five are present and active in Setup → Remote Site Settings:

Name	Used for
`REDA_Router`	Disconnect (releasing the connection).
`Meta_Graph_API`	Talking to Meta.
`Google_OAuth`	Google sign-in.
`Google_Ads_API`	Google Ads operations.
`Data_Manager_API`	Reporting Google conversions.

Step 8 — Turn on the platform switches

The connector has a master on/off switch per platform, stored in the Data Service Setup custom metadata. Lead capture only runs for a platform when its switch is on, so this is also your kill-switch if you ever need to pause intake.

Switch	Turn on to
Google Lead Form Enabled	Capture Google lead-form submissions.
Meta Lead Ads Enabled	Capture Meta (Facebook & Instagram) lead submissions.

Enable only what you use. Turn on just the platform(s) you advertise on. To pause intake for a platform later — during testing, or if something looks wrong — switch it off here; existing leads are untouched and capture resumes when you switch it back on.

Step 9 — Verify the setup

The Ad Account tab is visible to your ad administrators, and they can create a record.

On an Ad Account record, all three buttons appear and the layout shows the setup fields.

Your lead record's layout (Inquiry or Lead) shows the attribution fields, and the conversion fields are on the right record for your edition.

All five remote sites are active, and the platform switch for each platform you use is on.

With those confirmed, you're ready to connect your first account. Follow Google Lead Connector or Meta Lead Connector to bring leads in, then Closed-loop Conversions & Conversion Target to report outcomes back.

Where to go next

REDA Ads Connector: Overview — what the connector does and how the pieces fit.
Google Lead Connector — connect a Google account and start capturing leads.
Meta Lead Connector — connect a Facebook Page and capture Meta/Instagram leads.
Closed-loop Conversions & Conversion Target — report won leads back to Google and Meta.
Ads Connector: Troubleshooting — diagnose leads or conversions that don't arrive.
Web Inquiries and Capturing Inquiries — how inbound leads reach REDA more broadly.

Frequently asked questions

The administrators who create Ad Account records and run Connect, Disconnect, and Select Conversion Target. People who only view captured leads just need normal read access to your Inquiry or Lead records. On ISV orgs there is no Ads permission set: assign REDA - Master Data - Admin instead.

The permission set grants the ad fields read-only, and the Inquiry conversion fields aren't in it at all. Grant edit access to the Advertising Platform picklist and confirm Inquiry conversion-field access through the admin's profile or a supporting permission set.

No. Authentication is handled entirely by REDA and by the self-service Connect flow. You never register apps or handle app credentials or secrets — when you click Connect Ad Account, you sign in to your own Google or Meta account and grant access, and REDA provisions the connection behind the scenes.

No — connecting is a browser redirect. Only Disconnect Ad Account calls the router, so the REDA_Router remote site must be active for disconnects to succeed.

Mostly the same. Leads land on standard Leads (not Inquiries), conversion fields go on the Opportunity, and there is no dedicated Ads permission set — assign REDA - Master Data - Admin instead, which already grants the Ad Account object and tab.

Was this article helpful?