REDA ISV Monsoon 2026 · v1.411 1 Aug 2026

REDA One (ISV) — Monsoon 2026 (v1.411)

This release adds an Ads Connector that captures leads directly from Google and Meta ad campaigns and reports conversions back to those platforms, a Content-Plus document publisher for records, the REDA Admin Console for configuring and operating the app in one place, on-record lease-charge components, and a Parent Property Code that flows across the object model for grouping and reporting.

This is the ISV edition of REDA One. REDA ISV runs on your own Sales Cloud licence, so these features sit on the standard Salesforce Lead, Campaign and Opportunity objects — not on the custom objects the OEM edition uses. REDA One OEM and REDA One ISV are separate packages on deliberately separate version lines: the version number you see here will not match the OEM one, and that is expected.

Getting this version

Upgrade the REDA package in your org. To confirm you have it, open Setup → Installed Packages and check that the Version Number column next to REDA reads 1.411 or higher.

The Ads Connector needs real setup that the upgrade does not perform. It is the one feature here that will not work at all until an administrator configures it — a public Site, platform credentials, and a permission-set assignment. See the Ads Connector setup steps below.

What's new

Ads Connector — Google and Meta lead capture with closed-loop conversions

Capture leads directly from Google Lead Form and Meta Lead Ads into standard Salesforce Leads, and send closed-loop conversions back to the ad platform when a lead converts — so ad spend is measured against real pipeline instead of against form fills.

You connect one or more ad accounts. Incoming submissions are processed using their external identifiers and the available campaign, ad-account and click details. When a Lead is converted with a linked Opportunity and the other sending conditions are met, Google receives the conversion through Data Manager with the Opportunity Amount if provided. Meta receives a conversion event through the Conversions API with the available match keys; this connector does not send a monetary value to Meta. A Lead conversion does not itself prove a closed sale or realised revenue, and platform attribution or optimisation is not guaranteed.

A new Ad Account object holds one record per connected Google or Meta ad account — its platform, account or manager ID, conversion target, connection status and linked Campaign. These are managed by administrators.

Object	New fields	Purpose
Lead	Ad Platform, Ad Account, Ad Account Id, Ad Campaign Id, Ad Publisher Platform, Ad Unmapped Answers, Ext Lead Id	Attribution — which platform, account and campaign produced this lead. Ext Lead Id is the de-duplication key.
Opportunity	Conversion Sent, Conversion Sent Datetime	Whether the closed-loop conversion has been reported back to the ad platform, and when.

Access is split: the REDA - Master Data - Admin permission set manages Ad Accounts and the connect and conversion screens, while the end-user sets — REDA - Property Sales User, REDA - Property Leasing User and REDA - Property Acquisition User — get read access to Ad Accounts and to the Lead attribution fields.

Setting it up in your org

Create a public Site and grant it access to the inbound lead webhook. The ad platforms post lead data to your org without authenticating, so a public Site is required and its guest user needs access to the inbound lead-webhook Apex classes. This is per-org configuration and cannot be packaged.
Enter your Google and Meta credentials into the protected Ad Secret custom metadata. This is where the developer token and OAuth client details belong — a protected custom metadata type, never a field on a record or any other surface users can read.
Assign REDA - Master Data - Admin to whoever will connect ad accounts. Then connect each ad account and choose its conversion target.
Expose the new Lead and Opportunity fields. If you have customised those page layouts — most orgs have — the upgrade will not have placed the new fields on them, and if you use your own permission sets rather than the packaged ones, no field-level security has been granted either. Setup → Object Manager → Lead (then Opportunity) → Page Layouts → drag the fields in → Save, and grant field-level security on your own permission sets.

Full guides: Ads Connector overview, Ads Connector setup, Google lead connector, Meta lead connector, Closed-loop conversions and Ads Connector troubleshooting.

Conversion tracking lives on the Opportunity, not the Lead. In this connector, the conversion tracking fields are stored on the Opportunity linked to the converted Lead. Open that Opportunity to check the sending status. Access to a converted Lead depends on Salesforce permissions, including View and Edit Converted Leads; it is not universally read-only.

Content-Plus — publish and manage documents on a record

A document-management layer built on Salesforce Files. You can label and categorise the files attached to a record, control a Publish to Web public link, set the order documents appear in, and drive all of it from list and upload components placed on the record page. It suits property and listing media, and any record that needs a curated, publishable set of documents rather than an undifferentiated pile of attachments.

To enable it: assign the new REDA - Content Plus - User permission set, which grants the Content-Plus components and file fields, then add the Content-Plus component to the record pages that should carry it. Full guide: Content management.

REDA Admin Console — one place to run the app

A consolidated console for configuring and operating REDA: App Settings and a Scheduled Jobs manager — where you schedule, reschedule and monitor the recurring background jobs — now sit together in one screen instead of being scattered.

Access is gated by the REDA Admin Console Access custom permission, which is granted through REDA - Master Data - Admin. Users without it see an access-denied screen rather than a partially working console.

To enable it: assign REDA - Master Data - Admin — or the REDA Admin Console Access custom permission on its own — to your administrators. The console tab is set to admin visibility by default. Full guides: Admin Console, App settings and Scheduled jobs.

Lease-charge management components

New on-record components let you review and manage an Opportunity's lease charges — recurring charges, one-time charges and promotion charges — directly on the record, plus a New Terms & Charges action to add them in context rather than navigating away.

To enable them: the components ship with the package; add them to the Opportunity record page where you want them. Full guides: Lease charges, Recurring invoicing and Charge codes.

What's improved

Parent Property Code across the object model

A Parent Property Code field now flows across the object model — Property, Booking, Case, Inspection, Opportunity, Ticket, Work Order and their related records — giving a consistent property-hierarchy code to group and report on. A Region Code was added on the ownership, commission and portfolio records, and a Floor Plan Image URL on Property.

These are deliberately not on any page layout. They are system and reporting fields, populated by automation and used for grouping, reporting and integration — not typed in by hand on a record. Their absence from your layouts is by design, not an oversight, and they are fully available in reports and list views without any layout change.

Field-level security for Parent Property Code was added in the package to REDA Master Data Admin (edit) and REDA - Master Data - Read Only (read) for the records where it had been missing — Case, Ticket and Opportunity Contact Role.

If you do want one of these codes visible on a particular object's record page, an administrator can add it: Setup → Object Manager → the object → Page Layouts → drag the field into a section → Save, granting the field on your own permission sets if you use your own. Full guide: Regions and property hierarchy.

Recurring invoicing and scheduled-job refinements

A set of under-the-hood improvements to recurring invoice and charge generation, inflation adjustment, resident-portal user provisioning, recurring calendar-slot exceptions, and property leasing search. These are automatic on upgrade with no new configuration for existing setups. Full guides: Recurring invoicing and Scheduled jobs.

How to check the upgrade actually worked

Check	How	What you should see
The version installed	Setup → Installed Packages	REDA at 1.411 or higher.
The Admin Console opens	Open the REDA Admin Console as a user with REDA - Master Data - Admin	App Settings and Scheduled Jobs, not an access-denied screen.
Lead attribution fields are visible	Open a Lead as an ordinary Sales user, not as an admin	The Ad Platform and Ad Campaign attribution fields on the layout.
Lead capture is wired up	Submit a test lead through your connected Google or Meta form	A Lead created with its Ad Account and Ext Lead Id populated.
Conversions report back	Convert that test Lead and open the resulting Opportunity	Conversion Sent ticked, with a Conversion Sent Datetime.

Frequently asked questions

REDA One ships as two separate packages — OEM and ISV — on deliberately separate version lines. The OEM edition embeds Salesforce Platform licences for customers who are not otherwise on Salesforce; the ISV edition runs on your own Sales Cloud licence. They version independently, so the numbers are not meant to match.

Google and Meta post lead data to your org without authenticating, so there has to be a public endpoint for them to post to. That is a per-org configuration which cannot be included in a managed package — you create the Site and grant its guest user access to the inbound lead-webhook Apex classes.

Open the created Opportunity: this connector stores its conversion tracking there. Check Conversion Sent and Conversion Sent Datetime, then see Ads Connector troubleshooting. The local indicators do not by themselves prove final attribution by the advertising platform.

No — it is intentional. Parent Property Code, Region Code and Floor Plan Image URL are system and reporting fields, populated by automation. They work in reports and list views without appearing on a layout. Add one to a layout yourself if you want it visible on a particular object.

Only if those layouts are untouched package defaults and your users are on the packaged permission sets. A managed upgrade never places a field on a layout you have customised, and never grants field-level security on your own permission sets or profiles. Both are administrator steps.