Brainshark Feeder AppCloud User Guide

Version 2

    Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

     

    Brainshark Feeder Cloud Application

     

    For more Brainshark Cloud Application user guides, click here

     

    What does it do and why should I use it?

     

    The Brainshark Feeder Cloud Application allows you to import viewers of your Brainshark presentation into Eloqua contacts.

     

    This allows you to run campaigns to target the viewers of your Brainshark presentation based upon their viewing characteristics.

    These include viewing time, number of slides viewed and many other data points.

     

    A typical use case would be feeding viewers of a Brainshark presentation to Eloqua contacts and sending those users who have finished watching a presentation with a followup email and those who have not with a different email.

     

    What do I need to use this Cloud App?

     

    • A Brainshark Account (Sharkive) with:
      • Reporting API Access (check with Brainshark Support)
      • Click Path Tracking (check with Brainshark account manager)
      • A Brainshark user with reporting access to presentations
    • An Eloqua Cloud Connectors account (http://cloudconnectors.eloqua.com)
    • An Eloqua account (http://eloqua.com)

     

    Note: When creating your account on cloudconnectors.eloqua.com, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

     

    How to install and set up the Brainshark Feeder

     

    To use the Brainshark feeder, you will need to set up where data is to be stored in Eloqua, your presentation in Brainshark and configuring how data will be transferred within the Eloqua CloudConnector site. (https://cloudconnectors.eloqua.com )

     

    Eloqua Setup

     

    Create a Custom Data Object with properties matching to the following table (If you need a refresher on setting up Custom Data Objects, see this post: Custom Data Objects)

     

    Field Name Shown in ConnectorEloqua Custom Object Field NameEloqua Custom Data Object Field TypeEloqua Contact Field NameNote
    Email Address (Contact):Email AddressContact entity match field
    CompanyCompanyTextCompany
    Guestbook Custom Field 1Guestbook Custom Field 1Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 2Guestbook Custom Field 2Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 3Guestbook Custom Field 3Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 4Guestbook Custom Field 4Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 5Guestbook Custom Field 5Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 6Guestbook Custom Field 6Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 7Guestbook Custom Field 7Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 8Guestbook Custom Field 8Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 9Guestbook Custom Field 9Type determined by business processes(optional mapping)To move contact data according you business process
    Guestbook Custom Field 10Guestbook Custom Field 10Type determined by business processes(optional mapping)To move contact data according you business process
    Email Address (Custom Data Object):Email Address (Custom Data Object):Text(Email Address)Actual contact entity mapping done when the feeder runs.
    First NameFirst NameTextFirst Name
    Last NameLast NameTextLast Name
    Guestbook Phone FieldGuestbook Phone FieldTextBusiness Phone
    Guestbook Title FieldGuestbook Title FieldTextTitle
    Brainshark Integration Key 1Brainshark Integration Key 1Text(optional mapping)Brainshark customers use these to integrate with other systems
    Brainshark Integration Key 2Brainshark Integration Key 2Text(optional mapping)Brainshark customers use these to integrate with other systems
    Brainshark Integration Key 3Brainshark Integration Key 3Text(optional mapping)Brainshark customers use these to integrate with other systems
    Brainshark Integration Key 4Brainshark Integration Key 4Text(optional mapping)Brainshark customers use these to integrate with other systems
    Brainshark Integration Key 5Brainshark Integration Key 5Text(optional mapping)Brainshark customers use these to integrate with other systems
    Presentation ID FieldPresentation ID FieldText(not mapped)
    Brainshark Presentation TitleBrainshark Presentation TitleText(not mapped)
    URLURLText(not mapped)
    Percentage of Slides ViewedPercentage of Slides ViewedNumeric(not mapped)
    Date/Time ViewedDate/Time ViewedDate / Time(not mapped)
    Accessed from Mobile DeviceAccessed from Mobile DeviceText(not mapped)
    View Key FieldView KeyText(not mapped)(unique code)
    Slides ViewedSlides ViewedNumeric(not mapped)
    Tracking CodeTracking CodeText(not mapped)

     

    Note that it is very important that the data types be accurate. If the fields are mis-configured, no data will be imported.

     

    EloquaCDO.png

     

    The imported data will be mapped to a datacard that is associated to a contact with the matching Email Address, as specified on the mapping screen:

    View Key is the Unique Code Field.

     

    Next, create a contact group (E9) or shared list (E10) to receive all contacts associated with views - this will later be used during the setup process on the CloudConnectors.eloqua.com site.

     

    Brainshark Setup

     

    Identify desired videos and their numeric Presentation ID's (PIDS)

     

    BrainsharkSetup.png

    Brainshark presentations with Numeric PID

     

    These numeric PIDs will be later used to identify the presentations to be have contacts fed from.

    Note that presentation names can have duplicates and "z code" PIDS are not used in the feeder

     

    Generate a few views with PID and EM parameter for basic configuration testing.

     

    CloudConnectors.eloqua.com Setup

     

    To get started, go to Feeder > Brainshark Feeder within cloudconnectors.eloqua.com  Feeders do not require a Program Builder step
    as they just run on their own and feed data directly into the Eloqua system.

     

    BrainsharkMenuCC.png

    Next you’ll be asked to create a new Brainshark Feeder step, add your Eloqua credentials and specify the details of how often you would like the Feeder to run.

     

    BrainsharkEloquaCredentials.png

    On the next screen you'll be asked to configure the Brainshark Feeder.

    You will need to do the following steps:

     

    1. Fill in the following fields:
      1. Brainshark Company: the Brainshark login directory name (also called the Sharkive name.)
      2. Brainshark Contact Import Limit – enter 20000 (this large number is needed to handle the typically large amount of information the feeder can receive from Brainshark)
      3. Contact group for results – start typing any part of the name of group/shared list made in prior step
      4. Custom Data Object – Select CDO made in prior step from the drop down
    2. Click the Save button
    3. Choose presentations. Clicking in the Brainshark Presentations field will pop up a list of all available presentations. Start typing the numeric PID (or the Name) of the presentation you want and click on the highlighted item. Repeat until all the presentations you want to gather data for are selected
    4. Click the Save button

    BrainsharkFeederSetup.png

     

    Next, click on the Mappings tab to bring up this page:

    BrainsharkMapping.png

    On this page you should select the custom data object fields where you would like the associated data from the Brainshark views to be imported to.

     

    The labels on the left represent the fields that can be mapped from Brainshark, while the dropdown fields represent the valid fields in the CDO that can be mapped to.

     

    Tips:

    • It’s helpful to use the field names from the Feeder as the field names in the CDO.
    • View Key field from the feeder must be mapped to the View Key field in the CDO.
    • Ensure that the email address is mapped to both the contact (the first line in the mapping screen) and the data object (second line in the mappings screen)

     

    Testing the Feeder

     

    You can test the feeder by clicking on the test tab on the left menu from within your feeder step:

     

    TestingTab.png

     

    On this tab each option does the following:

    • Dry run – pass if any data is returned
    • Full run – pass if data is returned and CDO has appropriate values in it. (compare with Viewing Details by Presentation Report in Brainshark. Should match exactly) It’s helpful to have a report template configured in Brainshark with the same fields the Feeder is drawing
    • Enable – Run Feeder. Choose Once a Day and click Forever
    • Note that the Feeder will run immediately then once every 24 hours.  The time of day it runs can’t be set, but can be reset by using the Reset checkbox

    TestTab.png

    Example: Using the feeder data within Eloqua

     

    Create a filter with conditions referencing the CDO.

    • Reference the numeric PID to focus results on specific presentations
    • Percentage of Slides Viewed is expressed as a full number 80% = 80 (not .8)

    EloquaFilter.png

    Easily place in Campaigns or Program Building to check if a contact has viewed a presentation.

    EloquaCampaignCanvas.png

    Wrapping up:

     

    Beyond this single scenario there are other many uses for Brainshark data being fed into Eloqua. It makes Brainshark viewing data available anywhere you would use a filter or reference a custom data object. As an advanced processes, you could even use Brainshark guestbook forms to feed new leads into Eloqua and onward to your CRM.

     

    Feel free to leave any feedback or questions in the comments below.