Track referral sources, lead generation, conversation rates, and more with native integration options.

Brandlive offers a number of outbound and inbound integration options to capture and utilize all of your attendee data. Outbound integrations offer the ability to send your Brandlive registration data to your Client Relationship Management platform for additional analytics while inbound integrations bring your third party registration data directly into your Brandlive project for seamless webinar access and detailed tracking.

Learn more about our registration gating options in our Registration Feature Overview article here

Video Overview

Supported Integrations

Note: Stripe integrations are configured within the “outbound” integration panel but, are enabled within the Registration settings of individual projects within Sitebuilder.

User Permissions

Integration configuration is restricted to Owners, Admins and Builders in a given channel. These users have full access to authenticate, configure, and enable integrations across their channel.

Additionally, Owners and Admins can specify Project Group access to configured integrations, limiting visibility of those integrations to only lower level users with access to the same Project Group.

Integration Mapping 

When adding a new integration, the first step is to select your desired CRM. Admins will then be directed through the correct authentication flow at the appropriate time. Once selected, an admin is presented with the following fields:

  • Name: A unique identifier for this integration within Brandlive. This name will be seen by all users in your channel with visibility of this integration

  • API Endpoint: This multi-choice option indicates how you will be passing leads through to your CRM. Create lead will create a new record if one does not exist, and skip if it does not. Typically CRMs do not allow duplicate records to be created. Create or update will create a new if one does not exist, or overwrite existing information if the record does exist.

  • Event Identification: This is a way to title your mapped fields when being passed through to your integrated CRM. This field is particularly useful if you want to collect registrations for multiple projects but distinguish between the two outside of creating additional integrations at the channel level. This is your CRM endpoint, specifically where you are sending the data.

  • Field Mapping: This two column section maps Brandlive registration questions through to the assigned CRM key. Users can select from channel specific & global registration questions and add up to 50 rows.

  • UTM Parameters: Similar to the registration field section, this maps parameter keys or hidden fields passed through the Brandlive URL through to the assigned CRM key. Users can add up to 50 rows. Simply list out your UTM query keys in the left column and the CRM field in the right column. A common use case for this feature is tracking the performance of your Project's Marketing Campaign. 

Once configured, the above fields can be edited or added to at any time.

Project Selection

Project Groups can also be specifically targeted to only allow certain projects to pass data to your integrated app(s). To do this, simply choose which group of projects you'd like to associate to your integration after configuring the field mapping form. This will allow custom integration instances for specific projects as you are not restricted in the number of Integration tiles you can create.

Screen_Shot_2022-11-30_at_5.01.24_PM.png

Authentication

The final step to adding a new integration is authenticating into your CRM. After selecting Project Group access, admins are taken out of the Brandlive platform into the tray configuration wizard to authenticate.

For the first integration with this CRM, users are prompted for their credentials, an API Endpoint domain, a Client ID, and a Client Secret. These fields may vary slightly from integration to integration.

For duplicate integrations of a given CRM, users can select from a stored list of existing credentials or add an additional destination.

Authentication will only occur once per CRM per channel.

Enabling & Disabling Integrations

Once an integration has been successfully configured, it can be toggled on or off for use at the project level.

Enabled integrations can be toggled on or off on a project by project basis for projects with access to that integration.

Disabled integrations (default state after authenticating) are visible, but not possible to enable at the project level.

Disabling an enabled integration will be a global toggle, meaning toggling an integration off at the channel level will do the same for all projects with that integration toggled on. Toggling the same integration back on will reapply the enabled state for the same projects.

Channel vs. Project Level Integrations

Integrations are configured at the channel level and will be available to project groups selected for the integration. If an integration is not available for your project, confirm the project is part of a group with access to the integration. In order to activate an integration (with the exception of Stripe) at the project-level once it has been configured for your channel you will need to navigate to the Project Details screen by clicking "Details" on the projectproject in which you would like to activate the integration in the "integrations" tab:

Screenshot_2022-12-12_at_10.46.21_AM.png

For projects with access to integrations, the integrations can be in one of three states:

  • Off and Disabled: These are integrations available to the project, but disabled at the channel level.

  • Off and Enabled: Default state, these are integrations that are available to the project, enabled at the channel level, but disabled at the project level.

  • On and Enabled: These are integrations that are available to the project, enabled at the channel level, and enabled at the project level.

Integrations must be enabled at the channel level in order to be enabled at the project level.

The configurations for an integration at the channel level should be considered the default or base settings for that integration. Field mapping can be overwritten or added to a specific project without changing the default channel level integrations.

How-To Articles 

 

 

 

Top