In this article, you'll learn how to map data from Qualified to Eloqua and how to create Eloqua 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 or talking to a lead directly, information they might have given you explicitly through a lead form or bot, or other details 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 setup, check out our article on Eloqua Contact Mapping.
Mapping Basic Data to Eloqua
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.
Keep in mind that Eloqua requires an email for a contact to be created, so this information must be included.
To create your contact mappings follow the steps below:
- Navigate to Settings > Eloqua > Contact Mapping within Qualified.
- Select the ‘+’ symbol to map a field to Eloqua .
- Select the corresponding Qualified Visitor Field that you’d like to that information to live in within Qualified in the second column as shown 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.
Mapping Hidden Field Data to Eloqua
It's a common practice to have some field values hardcoded when creating contacts. This is worthwhile when 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 hardcoded (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:
- Add a new Contact Mapping to Eloqua, such as to the Source field.
- Create a new hidden field to correspond in Qualified.
- Set Qualified.com as the “Default value.”
When a new Contact is created from Qualified, we’ll automatically send over the value set as the default value.
Salesforce & Eloqua
If you're using our Salesforce and Eloqua integrations, 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 allows Qualified to look for an email address in Eloqua which, in turn, might help us also identify who that person is within Salesforce (an existing lead or contact).
Once we've synced the information from Eloqua, Qualified can push that visitor's information into Salesforce.
How this works is:
- When someone lands on the website, we try to identify who the person is and gather info about the person and the company they work for by reading the Eloqua cookie.
- Qualified will then pull information in (in real-time) from all of the apps you've connected (including Eloqua, Salesforce, Clearbit, and 6sense) into your visitor fields.
- If any information is conflicting, you determine the rank order of what system should take precedence using prefills in your visitor field area as shown below. (This is typically Salesforce > Eloqua.) When syncing back into Salesforce, we'll always use Salesforce as your source of truth.
- We serve up the experience you've created specifically for your Eloqua leads and contacts.
Strict Record Matching
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.
Note: Because all Salesforce records must be identified via Eloqua, Qualified will not create leads directly in Salesforce when this setting is enabled.
In this article, 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.