Things to Know

• Ensure you are logged out of Salesforce on all open browsers before establishing the Salesforce connection.
• The integration does not create Campaigns, but can update them.
• The integration automatically adds Campaign Member Status values: Registered, Attended, and Attended On-demand.
• Clients can add custom fields to the Campaign and Campaign Member objects to store additional ON24 activity.
• The integration does not update existing Contacts or Leads; instead, it creates new leads if an existing contact or lead is not found, as per the defined mapping.
• With the create new leads feature, Company is a required registration field.
• If you have fuzzy match enabled, you will need to allow the integration to bypass that feature.  Instructions are available under the Set Up tab.
• Backfilling is not available
• You can connect the integration to a Salesforce sandbox for testing before switching to production.  Ensure field mappings are consistent between environments.
• The Salesforce Campaign ID must be entered in the Campaign Code field on the Overview page for each event.
• Click here to download a self-service integration flow chart if you'd like.

Configuration

The ON24 self-service integration allows clients to configure and enable synchronization between ON24 and Salesforce directly from the ON24 platform.

This setup supports creating new leads if a contact or unconverted lead cannot be found.  ON24 maps events to contacts, leads, campaigns, and campaign member records.

• Ensure you are logged out of Salesforce on all open browsers before establishing the Salesforce connection.
• Ensure that custom fields are added to the Salesforce Campaign Member object. These fields will capture ON24 engagement data.  Click on this link for the ON24 API Data Salesforce Self-Serve workbook with all the available fields.
• You will need to create a dedicated user with ON24 login access to authenticate the Salesforce connection.
• If you have fuzzy match enabled, you will need to either exclude the dedicated connection user or alter the fuzzy match to make it harder to match.

Salesforce OAuth Connection Setup

• Using the Standard Salesforce User License
• Using a System Admin (or custom Admin) License

Using the Standard Salesforce User License

Step 1: Create a Dedicated Salesforce User

Create a new dedicated Salesforce user with:

• User License: Salesforce
• Profile: Standard User 
• Note: Leave the Role set to <None Specified> to avoid hierarchy-related permission issues. 

Verify that the Marketing User checkbox is enabled for the user.

Step 2: Create Permission Set

This permission set is required in all scenarios and grants ON24 access to the necessary Salesforce objects and fields. 

1. Under System Permissions, enable the API Enabled and Approve Uninstalled Connected Apps permissions.
2. Click Save and then select Object Settings.

At a minimum, the following permissions must be enabled in the Object Settings:

• Leads: Modify All Records is required to create new leads
• Contacts: Read and View All Records 
• Campaigns: Read, Create, Update - verify all necessary fields are accessible to the integration user
• Campaign Members: Verify all necessary fields are accessible to the integration user

Step 3: Assign Permission Set to the User

1. Return to the newly created ON24 integration user
2. Scroll to Permission Set Assignments and add the permission set(s) created above
3. Save the user 

Using the System Administrator User License

Create a new Salesforce user with:

• User License: Salesforce
• Profile: System Administrator
• Note: Leave the Role set to <None Specified> to avoid hierarchy-related permission issues. 

Verify that the Marketing User checkbox is enabled for the user.

Setup Steps for the SFSC Connection

In your ON24 account, open the Integrations dashboard from Platform Tools, click on API Tokens, and select Provision a New API Access Token.  Note the Token Key and Token Secret. 

Once you have provisioned a token, click on the Integrations tab, scroll down to ON24 > Salesforce Sales Cloud, and click Configure.

Enter the ON24 API Key and Secret to establish the connection. 

Installing the Connected App

1. Set up the OAuth connection in ON24.
2. In Salesforce, go to Setup and search for Connected Apps in the Quick Find.
3. Select Connected Apps OAuth Usage.
4. Locate the connected app:
   • ON24 Marketplace (for ON24 integrations)
   • TIBCO Scribe® Online Connector for Salesforce (for Scribe integrations)

5. Under App Actions, click Load Actions, then Install.
6. When prompted, click Install again to confirm.

 

Toggle off the PKCE Extension

For the current integration configuration, Require Proof Key for Code Exchange (PKCE) should be toggled off to allow the authentication flow to complete successfully. This setting is required for compatibility with the integration's supported authentication method.

1. While still in Setup, search for OAuth and OpenID in the Quick Find.
2. Select OAuth and OpenID Connect Settings.

3. Locate Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows and verify the option is toggled to Off.

Once the Connect App is installed and the PKCE is toggled off, the connected app setup is complete. 

Mapping the Integration

Step 1: Choose if New Leads are Created 

• The Create New Leads checkbox is selected by default, allowing the integration to create new Leads.
• If you do not want the integration to create new leads, uncheck the checkbox and select Next. If leads are not created by the Integration, click here for your next step. 

Note: If a Lead and/or Campaign Member is not created at the time of registration, no action will occur when that registrant later attends the event.

Step 2: Creating Leads

If you checked Create New Leads, you’ll need to define the mapping between ON24 registration fields and Salesforce Lead fields.

Fields are separated into Text Fields (including Picklists), Number Fields, Date/Time Fields, and Boolean Fields. ON24 will display the Lead fields in a drop-down list applicable to the field type.

Note: Company, Last Name, and Email are required registration fields to create new leads (required by Salesforce).

Step 3: Salesforce Campaign Member Field Mapping – Registrant Data

Set up mapping for ON24 registration data (e.g., custom fields, UTMs, Opt-in Marketing) to Salesforce Campaign Member fields.

Fields are separated into Text Fields (including Picklists), Number Fields, Date/Time Fields, and Boolean Fields.

ON24 will display the Campaign Member fields as drop-down lists based on the field type.

Step 4: Salesforce Campaign Member Field Mapping – Attendee Data

Set up mapping for ON24 engagement data (e.g., polls, content downloads) to Salesforce Campaign Member fields.

Fields are separated into Text Fields (including Picklists), Number Fields, Date/Time Fields, and Boolean Fields.

ON24 will display the Campaign Member fields as drop-down lists based on the field type.

Note: The integration does not support multiple picklist fields.

Step 5: Salesforce Campaign Field Mapping

Set up mapping for the Event analytics to the Campaign fields.

Fields are separated into Text Fields (including Picklists), Number Fields, Date/Time Fields, and Boolean Fields.

ON24 will display Campaign fields as drop-down lists based on field type.

Step 6: Choose if Custom Object Records are Created

Specify the Salesforce lookup fields for your custom object. The integration combines the Contact / Lead ID or Email and the ON24 Event User ID to uniquely identify each record, helping ensure duplicate records are not created.

• Contact field:  Contact ID or Email
• Lead field:  Lead ID or Email
• Event User ID field:  eventuserid

Step 7: Salesforce Custom Object Field Mapping – Registrant Data

Set up mapping for ON24 registration data (e.g., custom fields, UTMs, Opt-in Marketing) to Salesforce Custom Object fields.

Fields are separated into Text Fields (including Picklists), Number Fields, Date/Time Fields, and Boolean Fields.

ON24 will display the Custom Object fields as drop-down lists based on the field type.

Step 8: Salesforce Custom Object Field Mapping – Attendee Data

Set up mapping for ON24 engagement data (e.g., polls, content downloads) to Salesforce Custom Object fields.

Fields are separated into Text Fields (including Picklists), Number Fields, Date/Time Fields, and Boolean Fields.

ON24 will display the Custom Object fields as drop-down lists based on the field type.

Note: The integration does not support multiple picklist fields.

Step 9: Enabling the Integration

Once enabled, the integration will display as active. You can update authentication or mapping at any time using the Configure button. To deactivate, use the Disconnect button. 

Step 10: Campaign ID Requirements to Ensure a Successful Data Synchronization

Timing

Scheduled Timing

Scheduled timing is when the data passes from ON24 to your end system.  The integration is scheduled to run every hour, syncing the last 24 hours of activity.  After the first activation, it will push the last 30 days of activity. 

Note: Scheduled timing is different from Availability Timing.

Availability Timing

Availability Timing refers to when data is available in the data warehouse for the integration platforms to collect.

Timing may fluctuate on heavy traffic days.

• Registrant - 15 minutes
• Attended Live - 30 minutes to 2 hours after the event ended
• Attended On-demand - 4 to 12 hours

Data is processed and made available in a defined order based on business relevance. 

• Registrant data is prioritized and becomes available first. Attendee data will be provided once event activity has been fully completed and reporting is finalized.
• Within attendee data, live event information is prioritized ahead of on-demand activity due to its immediate relevance. On-demand data is processed after live data and appears once all reporting is complete.

This prioritization ensures that the most relevant and time-sensitive information is available first, while maintaining consistent, reliable reporting across all datasets.

Note: Availability timing is different from Scheduled timing.