Skip to content
  • There are no suggestions because the search field is empty.

Install and Configure the Consensus Salesforce Professional App (Lightning) | Updated for V11.12

In this article we will review how to install and configure the Consensus Salesforce Professional app. This includes adding the Consensus component within your page layouts, configuring permission set groups, and setting up data sync.

Salesforce is a powerful tool that allows you and your teams to manage prospects and opportunities. The Consensus Salesforce Professional integration lets you bring Demo View data collected from Consensus directly into your Salesforce account — so you can see Demo views right within Salesforce and include that data in your reporting.

In this article, we'll cover:

What the Consensus Salesforce Professional App can do

Depending on your configuration options, the app:

  • Send Consensus engagement data into Activity Records/Tasks on the Salesforce Lead or Contact record
    • Activities are matched based on the email address associated with a Lead or Contact.
    • Tracks DemoBoard Invite events and Demo Watched events.
    • The aggregate of these activities also rolls up to the parent Account.wg 
  • If enabled, creates new Lead records for historical leads or demo recipients inside Consensus.
  • Loads analytics data into custom objects so you can build custom reports and dashboards based on Consensus engagement activity. Custom objects include:
    • Demos — all Consensus Demos
    • DemoBoards — all Consensus DemoBoards
    • Invitations — all invitations/recipients added to DemoBoards
    • Views — all individual views by DemoBoard recipients
    • Features — feature rankings selected during a Standard personalized demo view
    • Demo Association — a junction object between Demo and DemoBoard, used to support Consensus Playlists
  • Allows users to create and send custom DemoBoard links from within Salesforce to Leads or Contacts.
  • Shows up-to-date Consensus engagement analytics for Leads, Contacts, and Opportunities.
  • Associates DemoBoards with Accounts and Opportunities.
  • Generate Consensus data report in Salesforce that can be used for calculating ROI
  • And more!

Installation

To install the Consensus Salesforce Professional App:

  1. Log in to Salesforce as a System Administrator.
  2. Download the Consensus App from the Salesforce AppExchange here.
  3. Choose your install environment, the app displays options to install in Production or Sandbox during this step.
  4. We recommend installing the app for All Users.

Pre-Upgrade Instructions: Removing Legacy API Credentials Before Upgrading to v11.12.4

Before upgrading your Consensus managed package to version 11.12.4 (or later), if your org is currently using the legacy connection method (API Key/Secret), you must complete the following step first:

Step 1: Remove the old API Key and Secret

  1. Log in to your Salesforce org.
  2. Navigate to the Consensus Configuration page.
  3. Locate the existing API Key and API Secret fields.
  4. Clear/remove both values.
  5. Click Test Connection, an error response confirms the connection is broken.
  6. Refresh the page to confirm the change.

Why this matters:
The new version uses an OAuth-based connection flow. If the old API Key and Secret remain in place during the upgrade, the system will detect them as an existing connection and display a Reconnect button instead of Connect, but the underlying OAuth registration won't be properly established, causing the connection and data sync to fail.

If you proceed with the upgrade without clearing your API credentials first, you'll see the error message below when attempting to Reconnect:

After confirming removal, proceed with the upgrade as normal.

Once upgraded, you'll see a Connect button on the Configuration page. At that point:

  • Click Connect to register the client and complete the OAuth handshake.
  • Make sure you're logged into the correct Consensus org in your browser before clicking Connect, if you have an active session for a different org, the flow will attempt to authorize against that org instead.
  • If you don't have an active session on Consensus, you'll be prompted to log in.
  • After a successful connection, proceed with the Configuration below and manually re-run the data sync flow, as it will not resume automatically.

If the old API Key/Secret were not removed before upgrading: only Consensus has the access needed to remove the registered client created from the existing API connection. In this case, the resolution is either (a) granting Consensus access to remove the registered client, or (b) uninstalling and reinstalling the package

Note: Due to the existing issue where the APIs were not cleared prior to upgrading, our team will consider a change or patch on our end to better support customers in this scenario, such as adding an option to clear the API key and secret.

Configuration

Configure a Domain Name

If you already have a domain name configured for your Salesforce instance, you can skip this step.

  1. Click the Gear icon (Setup).
  2. Type "domain" into the Quick Find box in the top-left corner of any page.
  3. Select My Domain.
  4. Enter a domain name (must be unique across all Salesforce instances), click Check Availability, then click Register Domain once confirmed available.

When installation is complete, switch to the Consensus application.

Accessing the Configuration Page

In Classic mode:

  1. Click the 9-dots menu icon.
  2. Find and click the Consensus application tab.
  3. Open the Configuration tab.

You'll need the Consensus Admin Group permission set group (included in the managed package) assigned to yourself to access the Configuration page and start data import. See Permission Sets below.

 

Configuration Page

v12.4 and above (current)

The Configuration page now uses an OAuth flow instead of manual key/secret entry.

  1. Go to the Configuration page in the Consensus managed package.
  2. Select the Configuration Mode. Choose Consensus Customer unless you are an internal Consensus employee.
  3. Click Connect.

  4. Log in to the Consensus org you want to connect to Salesforce. (You must be an Admin)
    • If you're already logged in to that org in the same browser, you'll be taken straight to the approval screen.
  5. Approve the client registration. This creates a new client record in Consensus with its own API key and secret, you don't need to generate or paste these yourself.
  6. Once approved, the connection is established and the Configuration page will show a connected/success state.



For v12.2 and below:

  1. Select the Configuration Mode. Choose Consensus Customer unless you are an internal Consensus employee.
  2. Add your Consensus API key and secret. You can find these values in Consensus under Integration > API Credentials.
  3. Enter your admin email address (this can be you as the SFDC admin, or a dedicated integration user). This email must also belong to a Consensus Admin user.
  4. Click Test to verify the API connection. Consensus displays a success message once it's communicating with the API properly.


Data Sync Settings

The Configuration page now separates sync timing into two distinct settings, plus two additional controls:

Setting Description Min Max Default
Time interval for recent Data Sync How often the near-real-time sync batches (RecentDemosUpdateBatch, RecentDemoBoards) run 10 min 240 min 10 min
Time interval for full Data Sync How often the full daily sync batches run 1 day 7 days 1 day (once/day)
Sync DemoBoard data from Optional date picker. If blank, all data syncs during the daily sync. If a date is set, only DemoBoard data created after that date is synced. Useful for orgs with a large volume of historical Consensus data. — — Blank
Enable Task Creation Toggle. When on, Activity Task records are created in Salesforce for Consensus engagement. When off, no Tasks are created. — — On

Note: The recent-sync scheduled job (RecentDemosUpdateBatch) will only begin running on its configured interval after a successful full sync has been completed at least once via the Run Data Update button below.

Schedulers

Select which of the following schedulers to enable, then click Run Data Update. You must run this manually at least once to begin the scheduled Apex jobs — otherwise data will not flow into Salesforce.

  • Scheduler# 1— creates new Leads for any Public Link Qualified Lead from Consensus.
  • Scheduler# 2 — creates new Leads for DemoBoard recipients that don't yet exist in Salesforce.
  • Scheduler# 3 — Creates new Contacts for Opportunity synced DemoBoards (the Contact will only be created if an Opp was synced to the DemoBoard initially).
  • Scheduler# 4 — adds a "Demoboard_Recipient" Contact Role to the Opportunity when a new Contact is created via Scheduler 3.
  • Scheduler# 5 — updates existing Contact/Lead DemoBoard analytics by matching on email address only (does not create new records). This is the most commonly used scheduler and the minimum required to get data flowing from Consensus into Salesforce.
  • Scheduler# ^ (create Leads and Recipients) — uploads historical Consensus data by creating new Leads for DemoBoard recipients and Consensus Qualified Leads.

 

Run Data Update runs the schedulers you've selected, in this order:

  1. Fetch demos in batches of 500 and save/update them in Salesforce.
  2. Fetch DemoBoard recipients in batches of 100 and save/update them in Salesforce.
  3. Fetch leads in batches of 150 and save/update them in Salesforce.

Existing records are only updated if there's a change, they are never recreated.

Run Permission Update runs a separate scheduler that keeps user permissions on the Consensus Users Info tab current. It runs automatically once every 24 hours and does not affect data synchronization.

 

Advanced Options

Salesforce triggers on Account, Contact, Opportunity, Lead, DemoBoard, Invitation, Feature, View, Error Log, and Batch Error can be individually disabled from Configuration > Advanced Options, either org-wide or scoped to a list of up to 5 specific user IDs.

⚠️ Changing these options may impact the Consensus data synchronization process. Don't disable triggers without first consulting Consensus — the Account, Contact, Opportunity, and Lead triggers are currently deprecated and safe to leave disabled with no effect, but disabling other triggers (e.g., DemoBoard, Invitation) can cause data to fall out of sync between Consensus and Salesforce.

Permission Set Groups

As of v11.12, Consensus recommends assigning Permission Set Groups rather than individual permission sets, since each group bundles the correct custom-object and standard-object permissions together for a given user type.

Permission Set Groups:

Group Contains Use for
Consensus User Group Consensus Users + Consensus Users (Standard) Standard end users
Consensus Admin Group Admin Consensus + Admin Consensus (Standard) Salesforce/Consensus admins
Consensus Integration Group Integration Consensus + Admin Consensus (Standard) A dedicated Salesforce integration user/profile

Step-by-step: Admins

  1. Find the Consensus Admin Group permission set group.
  2. Assign it to the necessary admin users, this allows the user to make changes within the Configuration page.

Step-by-step: End users

  1. Find the Consensus User Group permission set group.
  2. Assign it to the necessary end users. This allows users to interact with the Consensus component and use CRM Sync.

Step-by-step: Dedicated Integration User

  1. Remove the "Consensus Admin Group" so we can switch to API only profile
  2. Switch the integration user's profile from System Admin to the Minimum Access - API Only Integrations profile.
  3. Find the Consensus Integration Group permission set group.
  4. Assign it to the dedicated Integration User after configuring the integration, once all jobs have been processed and scheduled.

Managing Consensus User Info

Only a Salesforce Administrator with the Admin Consensus permission set assigned can access this page. This table is used when a Salesforce email differs from Consensus email and when users are seeing the error message: "Access denied, Please contact your Administrator" when trying to select an Account/Opp from the CRM Sync dropdown

  1. Open the Consensus Users Info tab.
  2. Add New record
  3. Input the Consensus email and Salesforce email address
  4. Save
  5. Press Run Permission Update within Configuration tab

Adding the Consensus Component to Page Layouts

The Consensus Salesforce App package includes a custom component that lets your Consensus users authenticate with Consensus, view Demolytics for the record they're on, create DemoBoards, and send them via Salesforce email. As of v11.6+, the component includes data tables for DemoBoards and Demo Views, plus high-level stat cards showing Consensus's overall impact on that record.

Recommendation: implement the component wherever it's most beneficial and accessible for your sales team, typically on Opportunity, Account, Contact, and Lead objects.

Steps

  1. Open the record page layout you want to edit (e.g., Opportunity), click the Gear icon in the top-right, and select Edit Page.
  2. Add a new tab: go to the Tabs section, click Add Tab, choose Custom from the dropdown, and enter "Consensus" as the Custom Label. Click Done.
  3. Drag the custom component createDemoBoard from the Custom-Managed area onto the new tab. Choose which table views and stat cards to enable.
  4. Click Save.
  5. Repeat for other Lead, Account, Contact, or Opportunity page layouts where you want the component to appear.

Setting up CRM Sync

Once the component is added, we recommend setting up CRM Sync, which lets users select an Account and/or Opportunity to associate with a DemoBoard live from within Consensus.

Version note: If you're on v11.10 or later, CRM Sync uses the updated OAuth 2.0 authorization flow and does not require a Salesforce Site. See Connecting Consensus to Salesforce – OAuth 2.0 Method (Version 11.10+ Required).

Auto-matching: When Auto-matching CRM is enabled, Consensus automatically suggests the best-fit Opportunity each time a recipient is added to a DemoBoard, based on matching contacts by email, then filtering by account (if selected), primary contact status, opportunity stage/probability, and most recent created date.

Creating a DemoBoard

You can create a DemoBoard for any Lead, Account, Contact, or Opportunity from the Consensus component.

  1. Open the record and click Create DemoBoard.
  2. If launching from an Opportunity or Account, you'll be prompted to select related Contacts to import as recipients — select the contacts you want, then click Import.
  3. The Consensus "Snap" interface opens in an embedded window. If not already logged in, sign in with your Consensus credentials or SSO (using your existing Consensus SSO setup — no separate Salesforce-specific SSO connected app is required).
  4. Choose Demos — select one or more demos to include, or record/upload new video content.
  5. Add DemoBoard info and recipients — name the DemoBoard, confirm the associated Account/Opportunity (pre-filled if launched from those records, or selectable if CRM Sync is enabled), and confirm recipients (pre-populated from imported Contacts, or added manually).
  6. Choose additional options — add other Consensus users for notifications/access, and enable DemoBoard expiration, two-factor authentication, or mark it as a test.
  7. Choose your link type and create — select Thumbnail or Button link, customize appearance, then insert.
  8. Send via Salesforce email — a new email opens with the Consensus default template, pre-addressed to your recipients and pre-associated with the correct Account/Opportunity. Customize as needed and click Send.

Uninstallation

Before uninstalling the package, remove the Consensus component from all Lead, Contact, Account, and Opportunity page layouts.

  1. Remove the Consensus component — delete the "Consensus" tab (or the individual component) from each page layout where it was added.
  2. Deactivate the Flows (optional cleanup). All Consensus-packaged Flow automations are deprecated as of v11.12 due to a Salesforce managed-package limitation that keeps them installed as active. They have no functional effect and no measurable performance impact while active, so this step is a cleanup step rather than a functional requirement:
    • Go to Setup, search "Flows" in the sidebar, and select Flows under Process Automation.
    • Filter for the Consensus-packaged flows, open each one, and click Deactivate.
  3. Uninstall the package — in Setup, type "install" into Quick Find and open Installed Packages. Click Uninstall next to the Consensus package, review the notes, check the confirmation box, and click Uninstall. You'll receive an email once uninstallation completes successfully.

Uninstalled packages appear under Uninstalled Packages, where you can permanently delete them or leave them for historical reference.