support Contact Support | system status System Status
Page Contents

    Integrating Video Cloud with Oracle Eloqua

    This topic explains how to configure the Audience module for use with Oracle Eloqua.
     

    The Audience module allows Video Cloud to synchronize viewing data from Brightcove Players to Oracle Eloqua. Once in Oracle Eloqua, this data can be used for segmentation, campaign logic, reports, lead scoring, and personalizing communications. The Audience module integration with Oracle Eloqua consists of two main components:

    • A Brightcove Player plug-in to enable tracking of video views data
    • A synchronization process to send tracking data from Video Cloud to Oracle Eloqua

    Requirements

    To use the Audience module with Oracle Eloqua, you must:

    • Have a Professional or Enterprise Video Cloud account
    • Have the Audience module enabled for your account by submitting the required information in the initial splash screen that appears when you open the Audience module
    • Click through the service agreement the first time you use the module
    • Use the Advanced Embed (in-page) publishing code when publishing your player; Standard Embed (iframe) publishing code will not work as the plugin will be running inside of an iframe and therefore will be unable to access any parent page URL parameters and may not get the correct cookies
    • Have Oracle Eloqua 10 and credentials to login at: https://login.eloqua.com
    • The credential being used to login to Oracle Eloqua should be added to the Advanced Users - Marketing group and have the following permissions:
      • Consume API
      • Install Cloud Applications
      • Set-up Marketing Campaigns

    Features

    Some of the key features of the Video Cloud - Oracle Eloqua integration are:

    • Lead forms - Create Eloqua forms that will appear automatically as viewers watch videos. For information, see Creating Custom Lead Forms for Oracle Eloqua.
    • Data format - Video cloud viewing data is delivered to a custom data object (CDO) in Oracle Eloqua. The data that is replicated to Oracle Eloqua is as follows:
      • Video Name
      • Video ID
      • Account ID (Video Cloud)
      • Page URL (URL of the referring page)
      • Player ID (Video Cloud player)
      • % Watched
    • Data transfer - Viewing data is synced hourly and it can take 2-4 hours to appear in Oracle Eloqua.
    • Data retention - Data collected can optionally be retained in Video Cloud for up to 1 month.

    Setting up the connection

    Before configuring the integration with Eloqua, we recommend that you open a new browser window and manually log out of your Eloqua account. This will ensure that when you configure the integration, you will be prompted to login to your Eloqua account and you can confirm that you are using the correct account.

    Follow these steps to setup the connection between Video Cloud and Oracle Eloqua.

    1. Open the Audience module and click Data Connections in the left navigation.
    2. Click Add New Connection.
    3. Select Eloqua as the integration.
    4. (Optional) Enter a Connection Name.
      select eloqua
    5. Click Connect.
    6. Click Connect to Eloqua.
      connect to eloqua
    7. You will be prompted to sign in to Eloqua. Enter your Eloqua Company Name, Username and Password. Click Sign In.
      Eloqua login
    8. If the login is successful, you will prompted to install the Brightcove Video Connect for Eloqua app. Click Accept and Install.
      install app
    9. You will be prompted to enable Eloqua for the account. Click Enable.
      confirm account
    10. You will be prompted to allow Brightcove Video Connect for Eloqua to access your Eloqua account. Click Sign In.
      allow access to eloqua
    11. Confirm your company name and username and click Accept.
      allow access to eloqua
    12. You will be prompted to setup Eloqua. Click Setup Eloqua.
      setup eloqua

    Configuring the integration

    Once the Video Cloud to Oracle Eloqua connection has been made, you can configure the integration.

    connected options
    1. Check Sync video views to Eloqua as External Activities to sync views as external activities. External activities are another place to put information in Eloqua. Publishers may choose to do reporting or trigger things in Eloqua using external activities. For more information, see the Eloqua documentation.
    2. By default, the Connection Status will be Enabled. The Connection Status determines if Video Cloud video engagement data is sent to Oracle Eloqua.
      • Enabled - Data is collected and will be sent to Eloqua
      • Disabled - No data is collected (integration is disabled)
    3. By default, Track Data for Unknown Viewers will be Disabled. This setting determines if video engagement data is saved in Video Cloud when the viewer is unknown. Only data for known viewers is sent to Eloqua.
      • Enabled - Data for all viewers is collected and saved in Video Cloud
      • Disabled - Data for unknown viewers is not saved in Video Cloud
    4. Select a data retention policy. The data retention policy determines how long the viewing data and lead form data (if using an Audience lead form) will be retained in your Video Cloud account. Retaining data in Video Cloud allows you to recover from interrupted synchronizations. Also, Audience will continue to retry events that fail to sync (usually because the viewer isn't a known contact at the time they viewed a video) until the event ages past the data retention period. You should adjust the retention settings according to your privacy policy - it is not required to retain any user data in Video Cloud. Data will be deleted after the data retention period.
      data retention options

    To remove the integration with Oracle Eloqua, click Disconnect. The bottom of the page will list all Audience-enabled players and associated lead forms.

    The Audience module supports multiple connections to marketing platforms. Click Add New Connection to configure additional integrations.

    Verifying the integration

    When the integration is configured, test the integration to confirm that video view data is being sent to Eloqua. For information on verifying the integration, see the Eloqua Integration Testing Guide.

    Creating an Audience-enabled player

    Video engagement data will only be sent to Eloqua when you are using an Audience-enabled video player. For information on creating an Audience-enabled Brightcove Player, see Creating an Audience-enabled Player.

    Passing a tracking ID

    The Audience module supports the ability to pass a tracking ID value to Eloqua. The tracking ID might be used to track a campaign ID for example. The tracking ID can be appended to the URL that displays the Audience-enabled player or added to the player embed code.

    • Example: Appended to URL
      http://www.myurl.com/video.html?bctrackingid=12345
    • Example: Added to player embed code
      <video data-video-id="6033402539001" 
             data-account="1486906377" 
             data-player="default" 
             data-embed="default" 
             data-application-id 
             class="video-js"
             data-bc-trackingid="12345" 
             controls></video>
      <script src="//players.brightcove.net/1486906377/default_default/index.min.js"></script>

    Audience will then pass the value along to Eloqua as another field that is synced.

    Identifying viewers

    Audience-enabled players with an Eloqua integration will invoke Eloqua’s APIs to obtain the visitor ID, frequently referred to as the Eloqua GUID. This ID is captured in the Audience module’s viewing data and is used to synchronize viewing data to Eloqua.

    Eloqua uses its own set of cookies and when a Brightcove Player is configured with an Eloqua integration, Audience captures the GUID in the Eloqua cookie and communicates with Eloqua server-side, to try and figure out who the user is.

    The user's email address can also be passed and used to identify the viewer. For more information and an example, see How the Audience Module Identifies Viewers.


    Page last updated on 02 Sep 2020