Jessica Collier
posted this on Jan 18 10:04
UPDATED May 25, 2011
LiveBall can easily and reliably share data with Eloqua’s marketing automation platform (e9 or e10). No custom code or developer integration is required. Once integrated, LiveBall’s powerful pages and forms will seamlessly feed behavioral and form-fed data into Eloqua.
In order for LiveBall to pass data to Eloqua, you need to:
Eloqua provides user-tracking scripts that must be placed on web pages in order to track visitor behavior within Eloqua. This is no different in LiveBall than it is for any of your other web pages. There are a couple of things you should be aware of:
The javascript that Eloqua supplies for use on your website looks something like this:
<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript' SRC='/elqNow/elqCfg.js'></SCRIPT>
<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript' SRC='/elqNow/elqImg.js'></SCRIPT>
To use that script on an external site like LiveBall, you need to make sure that the path to the scripts is complete, like this:
<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript' SRC='http://www.yoursite.com/elqNow/elqCfg.js'></SCRIPT>
<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript' SRC='http://www.yoursite.com/elqNow/elqImg.js'></SCRIPT>
Your version of the script above should be copied into LiveBall as a global script ( Libraries / Global Scripts / + script ). Name it ‘Eloqua Campaign’ and save the global script into an ‘Eloqua’ category for easy reference. Once you have this script saved into your global script library, you can place it in your LiveBall campaigns:
You are now tracking visitors in Eloqua for every page within the campaign. Repeat 1-3 above for each campaign that you would like to report visitor behavior to Eloqua.
The script setup above tracks visitor behaviors. In order to pass form and behavioral data, you need one additional script block on any LiveBall page that includes a form from which you would like to pass data into Eloqua. Let’s setup that script:
TIP: This script is supplied by Eloqua, and like the ones supplied above, you may need to change the relative path to your ‘elqNow’ directory to the full path beginning with ‘http://’. The path should be the same as the path in the other script you setup earlier.
You will also need to change the function initPage to match the code below. This enables seamless, worry-free linking of the user’s Eloqua cookie to their form data (converting them from anonymous to known in Eloqua and mating any previously collected behavioral data to their newly submitted form or click-through data).
The form-page script you’re expecting from Eloqua should look something like this once you’ve made the edits:
<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript'><!--//
var elqPPS = '70';
//--></SCRIPT>
<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript' SRC='http://www.yoursite.com/elqNow/elqScr.js'></SCRIPT>
<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript'><!--//
window.onload = initPage;
function initPage(){
liveballData("elqCustomerGUID", GetElqCustomerGUID());
}
//--></SCRIPT>
Once you have visitor tracking enabled using the instructions above, you’re ready to setup data passing to Eloqua. First, let’s make sure your Eloqua instance is ready to accept data.
Eloqua requires four specialized, data fields to be passed into the system. The values in these fields identify your Eloqua instance and provide other critical data. These fields will be included in all of your data exports.
Once you’ve added all of your data and core fields to your export format, you have four more special ones to add. These get added the same way — using steps 4-6 immediately above — but you have some special defaults to set (for three of them):
Your LiveBall export format is now ready. Now we can create the actual form post.
Now that all the setup is complete, in order to pass form data into Eloqua, you need to do a couple of things to each form page within LiveBall. Within the ‘page editor’ of the form page in LiveBall:
Each time you submit a form, the Eloqua export will happen automatically. During testing, if you entered an email address for the ‘peek’ during export setup (see above), you’ll get a text email showing you the data fields and values LiveBall sent and the status of the Eloqua acceptance of that data. You may leave that ‘peek’ address in place as long as you like.
When everything is properly configured, LiveBall will surface the Eloqua GUID (unique user cookie identifier) in the ‘view collected data’ function within LiveBall ‘preview’. If you don’t see a long number in the elqCustomerGUID field, you’re not receiving the cookie and should review your integration step by step to find the problem.