To be clear, I'm using Vidyard with Eloqua and am working to better enable how my marketing and sales teams are leveraging the data captured and fed by Vidyard into Eloqua (and now SFDC). Familiar with Vidyard? Cool, keep reading... Not familiar? I've linked to a few Topliners posts at the bottom of this post that you can check out now or later.
So, let me set the stage for this post a bit more... You've purchased Vidyard. You've uploaded your video content and embedded it on your site, etc... You've configured the Eloqua Connector. You're starting to see the data flowing into Eloqua - Video Name, Video Attention Span, etc... - based on video view activity. That's where I was at - but I wanted to take it one step further and write the "video view" activity from Eloqua to SFDC - we do it for email, forms and web visits, so why not video views? Especially now that we so easily can!
Basically, we're adding the Vidyard Eloqua CDO members to a short program that fires a custom integration event to write the video view activity into the matched SFDC Lead/Contact Marketing Activity/Activity history table. If you already have Vidyard, the Eloqua CDO is all set - you just need to dig in to the Integration and Program Builder modules (two of my favorite oldies-but-goodies) to complete this setup:
Step 1: Integration - Go to Setup/Integration/Outbound/Internal Events/Custom/Custom Data Card Events
- Click on the gray drop-down arrow to the left of "Custom Data Card Events" and select "Create New Custom Event." Name your new event, for example, "Video View," and click Save.
- Your new Custom Data Card Event should appear in the left-hand frame - click on the gray drop-down arrow to the left of the event name and select "Create New External Call."
- The External Call Wizard will appear in the main frame:
1. External Call Details - complete your External Call Name, Description and other field options, selecting your Vidyard CDO (note that you'll be creating two calls (Leads/Contacts) - so for this example, we'll start with the Leads call). Click "Next" in the bottom right corner.
2. Next up is your Target Details - the Action defaults to "Create," which is what we want, so leave it there. Then you need to select the SFDC Entity to write the call to - this will be whichever Entity you're currently writing Eloqua Marketing Activities to - in our case, it's Marketing Activity (you may be writing to the native Activity History table). You can choose to configure the External Call Return Value fields or note - we currently do not (any feedback on why we should is welcome). Click "Next."
3. Field Mapping time - locate the CDO/Contact fields in the right column, then drag/drop them into the corresponding SFDC Activity fields in the left column (you can type the black text as shown below directly into Field Expression area). We're date stamping the CDO record in Eloqua (see how to do that in one of my responses to this post: Vidyard Cloud Connector Enhancement Suggestions. One more thing here - I requested my SFDC Administrator add a new Marketing Activity Type "Video View," which I hard-coded into Activity Type below - this gives us the ability to filter and report on it correctly in SFDC.
4. Event Mapping - Confirm your new External Call is listed and click "Next."
5. Testing - You can choose to test the call here or after you've completed the External Call Wizard. The screen shot below is from after the Wizard (from the External Call Details, click on "Options" in the top right corner). Either way you do it, go to "Search" and look up one of the Vidyard CDO fields - I used Video Name and searched on the name value I used to create my test record (note, your CDO member record needs to be mapped to an existing SFDC Lead because you're building/testing the Lead call now). Once you select the record, click "Prepare for Test," then once you confirm the data set has populated correctly for the test, click "Execute Test."
6. Finish (Now repeat the above steps starting at "Create New External Call" to create the Contacts version).
Step 2: Program Builder - Go to Setup/Program Builder/Create New Program
- Complete the Program Details, selecting the Vidyard CDO and naming your Default Member Type ""Data Cards." Select "Save" and then "Edit Program Flow" from the bottom right corner.
- The program is easy-peasy - just three steps:
- I always start with "000. Start - Add Members" (as a pass-through step).
2. Next, you'll trigger your new calls "100. Run Video View Integration Event," making sure to select the New Custom Event you created above as this step action.
3. Finally, you wrap it up with "XXX. Remove from Program" step action.
- One last thing here - we need to "feed" the program via your Vidyard CDO - you can do this from Program Builder or by going back to your CDO. As of the time I'm writing this article, I'm getting an error when trying to create it from Program Builder, so here's how to do it from your CDO:
- From the Data Card Set Details, select "Data Card Set" from the top blue menu bar and then "Data Card Services." Click on "Edit New Data," select "Add to Step in Program Builder," select your Program and Start Step within the Search area, Save and Close. Enable the "New Data" Services.
Step 3: Test, Test, Test
- I recommend identifying and testing your primary use cases (in all things) - in this case, I have three:
- Net New Lead - This use case failed as I cannot easily identify a method to recognize a net new lead within the CDO or Program Builder (based on allowing Data Cards to feed the program). I'm launching without supporting this case as currently, all native activity calls fail on net new leads because the call fires before the net new lead is assigned a SFDC ID. I suppose I could create a "wait" step in the program, say, for two hours, just long enough for the new lead to have been created and populate the SFDC Lead ID field, hmmm... Feedback on how we could best accomplish this is welcome.
- Existing Lead - BOOM! Testing the process through to SFDC, this is a snapshot of what that looks like - as you can see, you could create report filters based on Marketing Activity Name, Date, Detail, Type - it just depends on your needs. The one thing I'd like to see here, eventually, is the embedded video URL so Sales can click it to view the content exactly as they can to view emails, forms and web visits. I've already talked to Vidyard about this request - if/when it happens, I'll be sure to update this post.
3. Existing Contact - KABOOM!
So that's it, Topliners - happy programming!
Note: Current Topliners posts referencing Vidyard in the title: Using the Vidyard Cloud Component for Eloqua Landing Pages Vidyard Cloud Connector Enhancement Suggestions