In this guide, you'll learn how to map data from Qualified to Eloqua and how to create Contacts straight from your Qualified chatbot or live sales conversation.
Before you can create Contacts, you’ll first need to connect to Eloqua. Once that’s complete, we can start setting up our Visitor fields and Contact Mapping.
Visitor fields are the fields in Qualified where you will store everything you wish to track and know about your website visitors. Visitor fields contain information you might gather through chatting/talking to a lead directly, information they might have given you explicitly through a lead form or bot, or other info that might be pulled from an external system, like Eloqua.
As this is a two way integration, Qualified will both pull information from Eloqua about your visitors as they come to the website as well as map this information back into Eloqua when it's collected by a bot or sales rep. If the visitor is unknown in Eloqua, Qualified will create the Contact based on the information collected in your visitor fields and the mapping specified.
For more information on this set up, check out our guide on Eloqua Contact Mapping.
Many implementations start by mapping a basic set of information to Eloqua for the purpose of Contact creation from Qualified. Let's start with the most basic fields in Eloqua, such as name, email and company. You’ll want to add these three fields to your Contact mapping area to ensure that this information is captured by your chatbot or sales team and included when creating the Contact in Eloqua.
To create your Contact mappings follow the steps below:
If you’d like, you can add a default value to the other non required Eloqua fields, such as [not provided] to be a filler if the visitor did not include this information about themselves as shown below.
You can map as much information into Eloqua as you’d like here, including hidden field data which we’ll go over in the next step.
It's a common practice to have some field values hard coded when creating Contacts. Meaning, you don't want your sales reps to set these values manually, but you want the system to set them based on your rules. The most common of these fields is a Source field. Setting a hard coded (or "hidden") value to this field will tell you that the Contact originated from a Qualified conversation on your website, and can be used later by marketing managers and sales managers for reporting purposes. To build this:
When a new Contact is created from Qualified, we’ll automatically send over the value set as the default value.
If you're using both the Salesforce and Eloqua integrations together within Qualified you might have questions about how they work together. One thing to note is that we'll first look at Eloqua and sync your visitor fields using the information in Eloqua. This will allow Qualified to look for an email address in Eloqua which might help us also identify who that person is in Salesforce (an existing Lead or Contact).
Once we've synced the information from Eloqua, Qualified can then push that visitor information into Salesforce.
How this works is:
By default, Qualified matches website visitors to Salesforce Lead and Contact records by email address. With strict record matching enabled, a visitor will be matched to a Salesforce record only if they first match a record in Eloqua. Their corresponding Salesforce record will be identified according to the fields configured within the Salesforce settings page and not by their email address.
In this guide we've gone over how to set up your visitor fields after connecting to Eloqua to both pull in information about your known visitors from your Eloqua campaigns as well as sync information back into Eloqua to create leads. We've also explained how Salesforce and Eloqua work together. To continue setting up your Eloqua integration, you'll want to next create unique experiences for your Eloqua visitors and new leads.