Eloqua Jobs (at Event Level)

This topic describes the pre-built jobs for integration with the Eloqua marketing platform, accessible from the Connectors page, which you access from Plan > Configure > Connectors in an event. (See that topic for a full explanation of connectors.)

These jobs are provided in Certain as working examples for more advanced integrations. They use the field mappings from the Eloqua plugin for your account, as configured by your system administrator in Account Settings > Implementation > Plugins.

The Connectors Guide (including Eloqua Jobs) is a PDF document describing and illustrating the Connectors pages and these jobs.

Note: There is a second Connectors page at the account level, Account Settings > Implementation > Connectors, for Administrators to run account-level jobs, such as importing contacts into the account as profiles, which are not described in this topic. (They can also run the event-level jobs described below, in a selected event, from the same page.)

Play (icon) Videos: All Certain University videos about Eloqua

Eloqua Jobs

Any fields described for a job below are those that are specific to that particular job. All jobs have a set of standard fields, which are described in the Plan > Configure > Connectors help topic.

These are the jobs available on Plan > Configure > Connectors if you select Eloqua as the target Application.
(For that to be available, Eloqua must be selected under the Integration  Module heading on Plan > Configure > Options > Functional Areas Needed by This Event.)

  1. Import Eloqua Contacts as Registrations

  2. Update Eloqua Contact List

  3. Create or Update Contacts in Eloqua

  4. Upload Engagement Metrics to Eloqua

  5. Upload Interest Metrics to Eloqua

  6. Create Eloqua Activity upon Session Status Change

  7. Create Eloqua Activity upon Reg Status Change

  8. Create Eloqua Activity upon Agenda Item Status Change

1. Import Eloqua Contacts as Registrations

Specify Eloqua Search Criteria to identify contacts in Eloqua and import those leads into Certain as registrations and profile records.

If a Certain profile does not exist for a lead (based on email address or Eloqua ID), then a new profile is created.
If a Certain profile does already exist for a lead (based on email address or Eloqua ID), then the registration is associated with that profile.

Job-Specific Fields

Play (icon) Video: Add Contacts as Registrations (2 min.)

2. Update Eloqua Contact List

Specify an Eloqua Contact List Name, for the job to add leads into that list upon the change of the specified Registration Status in Certain (from Invited to Pre-Registered, for example).

What unique identifiers are used to trigger a campaign in Eloqua?

When a contact is imported from Eloqua, the Eloqua ID is placed in the Certain External Profile ID field, and the Source of Profile is set to Eloqua.

For the Update Eloqua Contact List job to work, both of those fields must be populated correctly. Therefore, all of those records must have:

a) originated from Eloqua, via the Import Eloqua Contacts as Registrations job (see above), or

b) originated from Eloqua, via the Import Eloqua Contacts as Profiles job (see Account Settings > Implementation > Connectors), or

c) been used to create Eloqua Contacts, via the Create or Update Contacts in Eloqua job described next, or

d) been used to update Eloqua Contacts, via the Create or Update Contacts in Eloqua job described next.

Play (icon) Video: Update Eloqua Contacts List (1 min.)

3. Create or Update Contacts in Eloqua

Select one or more Registration Statuses, for the job to create new Eloqua contacts and update existing ones (matched on email address) from event registrations of that status.

The job does the following three things:

A) Creates new contacts in Eloqua for any registrations where:

1. External Profile ID is blank, or Source of Profile is Eloqua, Import, or blank, and

2. Registration Status is one of the ones entered, and

3. there is no Eloqua contact with the same email address.

B) Updates an existing Eloqua contact where:

1. External Profile ID is blank, or Source of Profile is Import, and

2. Registration Status is one of the ones entered, and

3. the Eloqua lead has the same email address.

Note that any blank fields in Certain do not affect the equivalent fields in Eloqua, since blank fields are not sent to Eloqua.

C) Updates the profile in Certain, setting its External Profile ID to the Eloqua ID, and its Source of Profile to Eloqua.

Play (icon) Video: Create or Update Contacts in Eloqua (1 min.)

4. Upload Engagement Metrics to Eloqua

Upload numbers and ratings of attendees' sessions and appointments from Certain to Eloqua, where they inform behavioral scoring.

See the PDF document, Interest and Engagement Metrics with Certain and Eloqua, for full details.

Note: This job creates a custom object in your instance of Eloqua, EventName_CertainEngagementMetrics, and uploads the statistics listed below to it

Some of the statistics require one or more of the following modules to be enabled for the event (in Plan > Configure > Options), as noted against each metric:

Engagement Metric

Modules Required

1. Number of Sessions Registered

Agenda Module, or
Speaker and Session Management

2. Number of Sessions Attended

Agenda Module, or
Speaker and Session Management

3. Average Session Rating

Event Views and/or Certain Mobile

4. Number of SSA Appointments

SSA (Self-Scheduled Appointments)

5. Number of Matched Appointments

Appointment Matching

6. Number of Appointments Scheduled

(= total, i.e. both Matched and SSA)

Appointment Matching and/or SSA

7. Number of Appointments Attended

(= total, i.e. both Matched and SSA)

Appointment Matching and/or SSA

8. Average Appointment Rating Received

(Appointment Matching and/or SSA)
and (Mobile or Event Views)

9. Average Appointment Rating Given

(Appointment Matching and/or SSA)
and (Mobile or Event Views)

5. Upload Interest Metrics to Eloqua

Upload interest-based scores per account-level tag assigned to agenda items or sessions for which the attendee is registered in the event, using the numbers of points assigned to those agenda items or sessions.

You specify whether to include agenda items (or sessions if Speaker and Session Management is enabled for the event) with an  Agenda/Session Status of Registered and/or Attended.

See the PDF document, Interest and Engagement Metrics with Certain and Eloqua, for full details.

Information Sent

This job creates a custom object in your instance of Eloqua, EventName_CertainInterestPoints, (or updates that object if it already exists), and sends the following information to it for all registrations in the event that meet the registration criteria listed below:

 

For each registration, it sends one row of data, where the first column is the registrant’s email address (used to identify the contact in Eloqua), followed by one column for each tag assigned to sessions for which that person registered, where the number in that column is the aggregate number of points for that tag.

For example, if I have set up tags for “Mobile”, “Cloud Computing”, and “Big Data”, the metrics uploaded could look like this:

 

Email Address Mobile Cloud Computing Big Data
jcitizen@mycompany.com 15 10 5
jdoe@mycompany.com 15 5 5
another@majororg.com 5 25 30

 

Registration Criteria

Information is sent for registrations that meet the following criteria:

  • Registration is marked as Complete

  • Registration is Active (not deleted)

  • Registration has an Accepted or Pending registration status (it is not cancelled or denied)

  • Agenda Item or Session status is Registered and/or Attended, depending on which you selected when submitting the job.

 

Example of an Interest Metrics Job

6. Create Eloqua Activity upon Session Status Change

(Note: Applicable only when Speaker and Session Management is enabled for the event.)

Select one or more Sessions, and one or more Session Status(es).

Enter a Campaign ID,which must already exist in Eloqua. (Caution: not validated here, so accuracy is important.)

The job generates an external activity in Eloqua, in that campaign, when an attendee's registration for one of those sessions changes to one of those statuses.

Caution: The contact must already exist in Eloqua; the job does not add new contacts.

Note: Creates Eloqua activities only for changes of status, not for new records.

Play (icon) Video: Create Eloqua Activity upon Session Status Change (2 min.)

7. Create Eloqua Activity upon Registration Status Change

Select one or more Registration Status(es).

Enter a Campaign ID,which must already exist in Eloqua. (Caution: not validated here, so accuracy is important.)

The job generates an external activity in  Eloqua, in that Campaign, when an attendee's registration for the event changes to one of those statuses.

Caution: The contact must already exist in Eloqua; the job does not add new contacts.

Note: Creates Eloqua activities only for changes of status, not for new records.

Play (icon) Video: Create Eloqua Activity upon Registration Status Change (2 min.)

8. Create Eloqua Activity upon Agenda Item Status Change

Select one or more Agenda Items, and one or more Agenda Item Status(es).

Enter a Campaign ID,which must already exist in Eloqua. (Caution: not validated here, so accuracy is important.)

The job generates an external activity in Eloqua, in that campaign, when an attendee's registration for one of those agenda items changes to one of those statuses.

Caution: The contact must already exist in Eloqua; the job does not add new contacts.

Note: Creates Eloqua activities only for changes of status, not for new records.

 


Envelope Any comments about this Help topic?

© 2020 Certain, Inc.