Part 7: Eloqua SFDC integration enablement & activity writing
This is part seven of the Eloqua SFDC native integration guide. To begin this tutorial at the start please use this link.
Enabling SFDC Integration Programs
Your Eloqua database will contain three templated programs that are used in the SFDC Integration. Two of these programs will need to be enabled to complete a successful integration. Only one requires configuration before it is enabled (one of the two CRM Update programs).
Note: Form submissions and list uploads do not automatically modify Contact/Lead data within SFDC – the records MUST flow through the SFDC Update program in order to for data to be properly reflected in SFDC. This should be clearly explained to the client and a go-live date should be established for form/list upload cutover.
Description of Programs
- SYSTEM – CRM Email Opt Out Program: This program is used to globally unsubscribe from Eloqua any SFDC Lead or Contact that has the Email Opt Out flag checked in SFDC. This will ensure that email compliance is met, and that the communication preferences of a record are kept consistent across both systems. This program has standard logic and does not require configuration work. This program and associated feeder need to be enabled.
Only one of these next two programs needs to be enabled for the SFDC Integration. This decision should be recorded on the client’s SFDC Integration Decisions document and provided back to Eloqua.
- *SYSTEM – CRM Update (Create only unique leads): This is the primary integration program. All form submissions and list uploads that are to flow into SFDC must feed into this program. This program evaluates then executes the criteria for creating/updating leads, updating contacts and performing campaign associations. This program uses the following logic:
Has Lead ID on Eloqua Contact? | Has Contact ID on Eloqua Contact? | Action |
No | No | Create Lead, Associate Lead to Campaign |
Yes | No | Update Lead, Associate Lead to Campaign |
Yes | Yes | Update Lead and Contact, Associate Lead and Contact to Campaign |
No | Yes | Update Contact, Associate Contact to Campaign |
- *SYSTEM – CRM Update (Point of Interest): This is the primary integration program. All form submissions and list uploads that are to flow into SFDC must feed into this program. This program evaluates then executes the criteria for creating/updating leads, updating contacts and performing campaign associations. This program uses the following logic:
Has Lead ID on Eloqua Contact? | Has Contact ID on Eloqua Contact? | Action |
No | No | Create Lead, Associate Lead to Campaign |
Yes | No | Update Lead, Associate Lead to Campaign |
Yes | Yes | Update Lead and Contact, Associate Lead and Contact to Campaign |
No | Yes | Create Lead, Update Contact, Associate Lead and Contact to Campaign |
Configuring the SFDC Update Program
SYSTEM – CRM Update (Create only unique leads) OR SYSTEM – CRM Update (Point of Interest)
This change requires the creation of a NEW Integration Event, which should be done before configuring the SFDC Update Program.
Create ‘Stacked’ External Call
- Navigate to Settings > Setup > Integration.
- Click the Outbound tab.
- From the left column tree view, expand the Custom folder then expand Custom Contact Events.
- From the drop-down menu next to Custom Contact Events, select Create New Custom Event.
- Enter the Custom Event Name ‘Create Lead and Associate with Campaign’, then click Save.
- Click on the newly created Custom Contact Event in the left pane.
- From the Event Mapping screen, click ‘Add Existing External Call’ TWICE (you’ll need to add 2 existing calls).
- Select ‘Create Lead’ as the first External Call.
- Select ‘Associate Lead with Campaign’ as the second External Call.
- Click Save.
Configure SFDC Update Program
SYSTEM – CRM Update (Create only unique leads) OR SYSTEM – CRM Update (Point of Interest)
- Navigate to Settings > Setup > Program Builder.
- Create a new folder ‘SYSTEM’.
- From the left column tree view, expand the BP-CRM Integrations and Salesforce folders.
Note: The Foldering path outlined is present in new Eloqua platforms. Clients may rename these folders or the names of the actual programs. This will likely be the case with existing clients. You should familiarize yourself with the logic of each program to avoid confusion. - Locate the CRM Update program the client has selected. Copy the program to the SYSTEM folder and name it ‘SYSTEM 1.0 SFDC Update’.
- Click on the Program Name. The program flow will load in the right pane.
- For each of the following steps, click on the drop-down arrow next to the step name and select Edit Step Default Action to configure the settings:
- Update Lead in SFDC
- Create Lead in SFDC with Campaign Association
- Create Lead in SFDC with NO Campaign Association
- Update Contact in SFDC
- Update Campaign in Lead
- Update Campaign in Contact
- Configure the settings for each step as follows:
- The action can run at any time of day
- Select the Integration Action Type, then the action Run Integration Event
- Select the Custom Event. These Custom Events contain the field mapping from the Outbound External API Calls configured in Section 8.
- Click Save and Close in the bottom right corner.
- Once all Integration Events are mapped and verified, select Enable Program from the Program sub-menu.
- Click on Enable Program and Selected Feeders in the bottom right corner.
- Verify that the program is active by checking:
- The Program Icon is colored in the left tree view
- The workflow background is white.
Enabling the SYSTEM-CRM Email Out Program
- Copy the ‘SYSTEM-CRM Email Opt Out Program’ to the SYSTEM folder and name it ‘SYSTEM 2.0 SFDC Email Opt Out’ [copy the program feeders AND actions].
- Click on the Program Name in the left tree view.
- Once the program flow has loaded in the right pane, select Enable Program from the Program sub-menu. The Enable Program Feeders window opens.
- Check the box next to the displayed feeder.
- Click on Enable Program and Selected Feeders in the bottom right corner.
- Verify that the programs are active by checking:
- The Program Icon is colored in the left tree view
- The workflow background is white.
Part 3: Configuring outbound Eloqua SFDC auto synchs
This is part three of the Eloqua SFDC native integration guide. To begin this tutorial at the start please use this link. Configuring Auto Synchs The fields to be mapped from SFDC to Eloqua are recorded within the SFDC Integration Field Mapping spreadsheet, in the...
Part 2: Preparing to use the native Eloqua SFDC integration
This is part two of the Eloqua SFDC native integration guide. To begin this tutorial at the start please use this link. In this part of my hands on how to you will learn everything you need to set up your inbound data using autosynchs on the Eloqua / SFDC native...
Part 1: Integrating Eloqua & SFDC using the native integration
The Eloqua SFDC Native integration connector At the production of this guide, Oracle has said that they will stop supporting the native Eloqua SFDC integration connector. Fear not - because I am here to help you. Personally I think the new Eloqua SFDC integration...
Eloqua Service: Migrating from the native Salesforce Integration to the SFDC App
Before we start, this post does have a sales pitch attached to it. My colleagues and I at P8ypus have put together an off the shelf Eloqua Salesforce integration migration product, for more information and to begin your migration process please visit the website...