Salesforce Integration App User Guide

Oracle Eloqua-Salesforce App

User Guide

06-Sep-2024

2 of 102

Contents

Salesforce Integration app 4

Supported Salesforce objects 5

Getting started with the app 7

Installing the Salesforce Integration app 8

Configuring connections 10

Creating a connected app 11

Configuring a connection in the Salesforce Integration app 13

Modifying a connection 16

Configuring defaults for a connection 17

Viewing connection errors 19

Creating sample programs 20

Creating step actions 22

Creating campaign actions 27

Creating response actions 33

Copying Salesforce fields into Eloqua 38

Configuring test runs for actions 38

Adding test contacts 39

Running an action with a test payload 40

Excluding the test payload from daily reports 40

Creating imports 41

Scheduling an import 49

Deduplication types 50

Checking email address changes before imports 51

Migrating native Salesforce integration assets 53

3 of 102

Adding imports to a canvas 55

Creating campaign imports 58

Creating opportunity imports 62

Creating user imports 69

Creating marketing activity exports 75

Configuring notifications 83

Salesforce Integration app FAQs 85

Using the app in a program or campaign 93

Viewing report data 95

Viewing the global report dashboard 95

Viewing connection errors 97

Viewing imports and exports by target 97

Viewing report data for actions and imports 99

Action report data 100

Import report data 100

Report data for failed actions or imports 102

4 of 102

Salesforce Integration app

¤ Tip: If you are using the native Salesforce integration, you can migrate your

assets to the Salesforce Integration app.

The Salesforce Integration app creates an integration between Oracle Eloqua and

Salesforce to send data between the two platforms. Leverage the Salesforce

Integration app in your marketing cloud solution to:

Transfer the leads generated from marketing campaigns in Oracle Eloqua into Salesforce so

they are nurtured and synchronized as sales leads.

Use the app within a program or campaign canvas to create or update records in supported

Salesforce objects in real time. Typical use cases include lead creation, lead updates, and

contact updates.

Schedule imports from Salesforce to Oracle Eloqua for supported Salesforce objects.

You can use the app for various marketing qualification and lead generation use

cases. For example, you can configure a listener step to listen for contacts who

complete a form. Once the contact is added to the program canvas, you may want to

decide to create a lead for the contact. Depending on the next decision, you can

configure this app to either create a new lead or update an existing lead within Oracle

Eloqua.

You can manage user permissions on this app by following the instructions listed here.

5 of 102

-Example: A listener step could be configured to listen for contacts who

complete a form. Once the contact is added to the program canvas, you may

want to decide to create a lead for the contact, depending on the next decision,

you can configure this app to either create a new lead or update an existing lead

within Oracle Eloqua.

Supported Salesforce objects

The integration supports bi-directional data flow for all objects available via the

Salesforce API with the following caveats:

Objects that are read-only will not be available for use in actions.

Objects that are not readable will not be available for use in imports.

6 of 102

If required, you can restrict access to some Salesforce objects. For details, refer to the

Salesforce documentation.

ëNote: Any Salesforce version that comes with API access is supported. For

more details, see Salesforce editions with API access.

7 of 102

Getting started with the app

The steps below outline the recommended setup and configuration process for the

Salesforce Integration app.

1. Install the Salesforce Integration app. Once the app is installed, configuration settings for

connections, actions, imports, and notifications can be found in the apps list. Go to Settings

> Apps and click Configure to access the configuration settings.

2. Create a connected app in Salesforce.

Configure one or more connections. Each connection can have multiple connected apps but

only one can be active per connection.

¤ Tip: If you are using the native Salesforce integration, you can migrate your assets

to the Salesforce Integration app.

4. Create actions. Actions are data transactions between Oracle Eloqua and Salesforce.

Use step actions to create and update records to be used in a program or campaign.

Use campaign actions to send campaign updates from an Oracle Eloqua campaign object to a

custom object in Salesforce. One campaign update action can be active at a time.

Use response actions to send data to Salesforce based on response rules configured in your Oracle

Eloqua instance. When a response occurs, Oracle Eloqua records the response based on priority

and the response is sent to Salesforce.

5. Create and schedule imports to import data from Salesforce to Oracle Eloqua periodically.

The Salesforce Integration app executes imports every 15 minutes. If an import needs to be

performed off schedule, it can be executed on demand.

8 of 102

Use standard imports to import contact record data from Salesforce into Oracle Eloqua. The

following imports are recommended: get leads, get contacts, get accounts.

Use campaign imports to import custom object data from Salesforce into Oracle Eloqua

campaigns to allow for bi-directional updates between the two applications.

6. Export Eloqua-generated marketing activities to synchronize data with a Salesforce

connection

7. Setup email notifications to be alerted if there are problems with your imports or actions.

8. Review your reports. The Salesforce Integration app provides reporting on the records being

sent between Eloqua and Salesforce.

9. Use the app in a campaign or program to update or create contact records.

10. Put actions through a test run with pre-configured contacts.

11. Add imports to a canvas to run up to ten post processing actions.

Creating sample programs

Installing the Salesforce Integration app

Z Important: Because deleting or deactivating the installer user account will

impact installed apps, we recommend installing apps using a user account that is

not tied to a specific person. The user account must have customer

administrator rights.

To install the Salesforce Integration app:

9 of 102

1. Follow the URL provided.

https://cloudmarketplace.oracle.com/marketplace/app/AppSalesforce

ëNote: If you have IP allowlists enabled, add internal Eloqua IPs to your allowlist .

2. Log in with your Eloqua credentials, if required.

3. Click Accept and Install to add the app to your Apps list.

4. Click Sign In.

5. Confirm your credentials and click Accept to grant permission for the app to communicate

with Eloqua on your behalf.

The app is now installed and can be viewed in your Apps list (Settings > Apps,

under the Platform Extensions section). You can configure your app now or at a later

time.

You can return to the Apps list at any time and view the app description, modify the

configuration settings, reinstall, or uninstall it. You can also check its status and

dependencies.

q Warning: To modify configuration settings, navigate to Apps, select your

app, and click the Configure icon . Selecting the Reinstall icon will force

you to go through the entire configuration process again. The app will be

10 of 102

unavailable for all users during the reinstall. All existing assets, configurations

and history are preserved when you reinstall an app. Also, you can choose to

delete an app by clicking the Uninstall . In this case, all current assets,

configurations, and history are permanently deleted.

Configuring connections

You can configure one or more connections and modify connections on the app's

Connections tab.

Prerequisites

Install the Salesforce Integration app.

Salesforce connected app: Create a connected app in Salesforce so that you can get the

following values to enter when creating a connection:

Consumer key: Displayed in the Salesforce connected app after creation.

Consumer secret: Displayed in the Salesforce connected app

In this topic, you'll learn about:

Creating a connected app

Configuring a connection in the Salesforce Integration app

Modifying a connection

Configuring defaults for a connection

Viewing connection errors

Creating sample programs

11 of 102

Creating a connected app

The following instructions are based on Salesforce Classic. For Lightning Experience

and Classic details, see the Salesforce's connected app documentation.

To create a connected app in Salesforce:

1. Go to https://login.salesforce.com/ and log in to your Salesforce account.

2. From the profile drop-down list, select Setup.

3. In the App Setup section, select Create > Apps. The Apps page is displayed.

4. In the Connected Apps section, click New. The New Connected App page is displayed.

5. Enter the following required values and any optional values if needed:

Connected App Name: Enter a descriptive name such as Eloqua Integration.

API Name: You can accept the default value or enter a different name.

Contact Email: Enter the email address of the user who will manage the connected app.

6. In the API (Enable OAuth Settings) section, select Enable OAuth Settings. Additional

options are displayed. Keep the Require Secret for Web Server Flow option, which is

selected by default.

7. Enter your Oracle EloquaCallback URL, which depends on your Eloqua pod number:

Pod Callback URL

Pod 1 https://apps.p01.eloqua.com/eloqua/salesforce/callback

Pod 2 https://apps.p02.eloqua.com/eloqua/salesforce/callback

Pod 3 https://apps.p03.eloqua.com/eloqua/salesforce/callback

Pod 4 https://apps.p04.eloqua.com/eloqua/salesforce/callback

12 of 102

Pod Callback URL

Pod 6 https://apps.p06.eloqua.com/eloqua/salesforce/callback

Pod 7 https://apps.p07.eloqua.com/eloqua/salesforce/callback

Pod 8 https://apps.p08.eloqua.com/eloqua/salesforce/callback

8. In the Selected OAuth Scopes section, select the appropriate scopes or select all available

scopes.

Z Important: At the very least, the three Salesforce OAuth Scopes are required. See

the FAQ for more information.

9. Click Save.

10. Select Create > Apps.

ëNote: The actual Salesforce base URL should be used in the app configuration. The

app name is used for labeling and identification purposes only.

11. In the Connected Apps section, find your connected app in the list and click its name.

12. In the connected app's API (Enable OAuth Settings) section, record the Consumer Key and

Consumer Secret values.

@ Learn more: Salesforce connected app documentation

13 of 102

Configuring a connection in the Salesforce Integration app

To configure a connection:

1. Log in to Oracle Eloqua.

Click the settings icon .

3. In the Platform Extensions section, click Apps.

4. From the apps list, click Salesforce Integration for Eloqua. The Salesforce Integration for

Eloqua page is displayed.

Click the configure icon . The App Configuration for Salesforce Integration for Eloqua page

is displayed.

6. Click Connections.

7. Click Create Connection.

8. Enter a connection name and click Create Connection. The Add Connected App button

and default field mappings are displayed.

14 of 102

9. Click Add Connected App.

10. In the Add a Connected App section, enter the Consumer Key and Consumer Secret from

your Salesforce connected app.

11. Click Add App.

12. In the Default Field Mappings section, select the Oracle Eloqua fields to map to the

corresponding Salesforce Unique Identifier fields.

a. Leads: Select an Eloqua field to map to the lead ID field for Salesforce contacts. By default, it is

named SFDC Lead ID.

b. Accounts: Select an Eloqua field to map to the registry ID field for Salesforce accounts. By default,

it is named SFDC Accounts ID.

c. Contacts: Select an Eloqua field to map to the registry ID field for Salesforce contacts. By default, it

is named SFDC Contact ID.

15 of 102

13. Click Save Connection.

ëNote: Please verify the value of the SFDC refresh token policy. If it is set to expire

immediately, the App authentication will fail.

14. Click Close. The Connections page lists existing CRM connections and associated connected

apps.

15. Next to the new connected app, click Authenticate App. A Salesforce login dialog is

displayed.

¤ Tip: You can choose to have your data routed through a CipherCloud gateway. To

do so, configure the login dialog to point to the CipherCloud gateway. You may need

to adjust your CipherCloud firewall settings to allow calls from Oracle Eloqua servers.

16 of 102

16. Click the default user name or log in with a different user name. The Allow Access? dialog is

displayed.

17. Click Allow. If authentication succeeds, your connected app is ready to be used.

Modifying a connection

To modify an existing connection:

1. In the Salesforce Integration app, click the Connections tab.

Click the connection's menu icon and select any of the following options:

Add Action: Click to create an action and automatically associate it with the current connection.

Add Import: Click to create an import and automatically associate it with the current connection.

Add New Connected App: Add another connected app to the connection.

Configure Defaults: Create default imports, actions, and marketing activities if you did not

already do this as part of the connection set up.

Delete: You can delete connections if there are no associated actions or imports. A confirmation

dialog will list any dependencies. The dependent actions and imports need to be disabled and

deleted before deleting the connection.

Edit: Open the connection in Edit mode so that you can modify its field mappings or connected

app values. You cannot modify the callback URL.

Migrate Native Assets: You can migrate assets from your native integration to the Salesforce

Integration app.

17 of 102

3. If a connection has multiple credentials, you can select the radio button to set the default

credential. Only one credential per connection can be active at once. For example, one

connected may have production credentials while another connected app has credentials

linked to a sandbox or test environment.

Configuring defaults for a connection

Once you configure a connection, you can open the Create Defaults section to create

default actions, imports, and marketing activities using default mappings. You can

alternatively create actions, imports, and marketing activities by manually configuring

them.

ëNote: You can only configure defaults for an authenticated connection.

18 of 102

To configure default imports, actions, and marketing activities for a connection:

1. In the Salesforce Integration app, click the Connections tab.

Click the connection's menu icon and select Configure Defaults.

The Create Defaults page displays all the available imports, actions, and marketing activities

for your connection.

3. Select the default fields you want to create for this connection.

4. Click Create Defaults. The selected imports, actions, and marketing activities are created

with a name that includes the name of your connection. You need to enable imports before

19 of 102

you can use them. To do it, go to the Imports tab and click the import's menu icon .

After an import is done, you can use a feeder service to make updates on a canvas . Unlike

imports, actions and marketing activities are enabled by default and you can start using

them right away in a program or campaign.

ëNote: You will create duplicate actions, imports, and programs if you configure

the same defaults for the same connection more than once. The duplicate asset

names will include the connection name and either the words New Import or New

Action.

Viewing connection errors

The Status and Reporting screen displays errors associated with a current connection.

If you have multiple active connections, and a hidden connection reported an error,

the Salesforce Integration app will display a notification message at the top of the

Status and Reporting screen. To find out which hidden connections have errors, open

the connection drop-down.

Connections that have errors will have a warning icon beside them.

20 of 102

Creating sample programs

You can create sample programs from the Configure Defaults option. If you select this

option, the Salesforce Integration app will create the selected programs in a

predefined folder named System - SFDC App. The Salesforce Integration app will

create all assets required to support these programs, and these assets will include the

program name.

ëNote: The Salesforce Integration app will not create a new program (and

related assets) if the program already exists.

To create a sample program:

1. In the Salesforce Integration app, click the Connections tab.

Click the connection's menu icon and select Configure Defaults.

21 of 102

3. Select which sample programs should be created. You can create up to three different kinds

of programs:

ëNote: When you select any of the 3 sample programs, required assets are

automatically selected as well. For example, if you select the Create Unique sample

program, then Create Lead, Update Contact, and Update Lead are automatically

selected as well.

Create Unique: In this program, a new lead record is created in Salesforce only if there is no

contact or lead record with the same email address in Salesforce. If there is an existing contact

record, the contact record is updated with contact information as defined in the Update Contact

action.

Hybrid: In this program, a new lead is created in SFDC only if there is no unconverted lead record

with the same email address in SFDC. Existing unconverted lead records in SFDC are updated with

contact information as defined in the Update Contact action.

Point of Interest: A new lead record is created if there are no leads with the same email address in

Salesforce, but an Salesforce contact already exists. If there is an existing contact record, the

contact record is updated with contact information from Oracle Eloqua as defined in the Update

Contact action.

4. Click Create Defaults.

A status bar will display and indicate when the sample program's creation is complete.

22 of 102

Creating step actions

ëNote: This page outlines how to create step actions in the Salesforce

Integration app. Learn how to create campaign actions and response actions.

Actions are data transactions between Oracle Eloqua and Salesforce. The Step Actions

page is where you create the types of actions to be used in a program or campaign

when using the app. You can create two types of actions: Create and Update. Create

will create a new record in Salesforce, and Update will take an existing Oracle Eloqua

contact and update their information in Salesforce. You can put actions through a test

run with pre-configured contacts.

Good to know

Users can map the Salesforce URL field to the Eloqua Large Text and Text fields. Use the

Large Text field if the value in your URL field contains more than 100 characters. Mapping

the URL field to any other Eloqua field results in an error.

For the Account, Contact, and Lead Salesforce objects, you can split the Address field onto a

new line in Oracle Eloqua, and the split will remain at the same place once that address is

pushed to Salesforce and imported back into Eloqua. For example, if you split an address to

a new line after 80 characters, and that's pushed to Salesforce, the address will still be split

to a new line at 80 characters once it's imported back into Eloqua.

Prerequisites

23 of 102

Configured connection

To create a step action:

1. In the Salesforce Integration app, click Actions.

2. Click Add Action and select a connection for which you want to create a new action.

3. Complete the action details:

ëNote: Each action can map up to a maximum of 249 fields. See the Eloqua

Developer Help Center for more information.

Name: Enter a name for the action.

Action Type: Select an action type from the list to either create, update, or upsert contact records.

Note that:

The Upsert option creates a new campaign member in Salesforce if one doesn't exist, and updates an

existing Campaign Member if it exists. The Upsert action type only applies to campaign responses

managed by the user and not those managed by Oracle Eloqua. Users need to map the fields

themselves and update the status field for Eloqua contacts, as any change to the status of the contact

will not be pushed automatically by Eloqua. You can configure the Upsert action with Eloqua custom

objects.

24 of 102

Z Important: When you're using Upsert in an action step in the Campaign Canvas, the

Salesforce Integration app will retrieve the Campaign ID automatically. If you're using Upsert

action steps on the Program Canvas, you will need to provide the Campaign ID as one of the

mappings in the Salesforce Integration app itself.

You can map any Eloqua custom object field to a static Salesforce ID for the Update action type.

Object Mapping: To see available fields for mapping, select an Eloqua object and Salesforce

object. Top-level objects from your Salesforce instance are available in the Salesforce Object list.

If you select the Lead object from the Salesforce Object list for either a Create or Update action

type, the Trigger Assignment Rule option is displayed. If you select Yes, a default assignment

rule will be triggered in Salesforce upon lead creation when new Eloqua contacts are added. Only

select Yes if you are using lead assignment rules in Salesforce. Setting it to Yes will cause the

action to take longer to run and will increase your Salesforce API usage.

Update Salesforce Fields: For each set of fields, specify the Salesforce field that will be mapped to

Oracle Eloqua contacts. If you are updating contact records, the unique identifier is the first

mapping shown in this list. If you are creating records, this option is optional. Add more mappings

by clicking Add Field Mapping. Click the menu to delete the mapping, or switch the field

type to static text, static date, or dynamic date. You can also choose whether or not the Salesforce

Integration app should Allow Eloqua field blank values to be sent to Salesforce. By default, this

25 of 102

option is always unchecked, that is, the Salesforce Integration app will not send blank Eloqua fields

values to Salesforce by default.

(Optional) Update Eloqua Fields: For each set of fields, specify the Eloqua field that will be

mapped to Salesforce contacts. If you are creating contact records, the unique identifier is the first

mapping shown in this list. If it is a Create or Upsert action type, you can set the To Eloqua field to

None to avoid a callback to Eloqua. Please note that if you choose to avoid a callback to Eloqua,

the related Salesforce record ID will not be populated on an Eloqua object (for example, SFDC Lead

ID). In addition, you can add static text, static dates or dynamic dates to the same callback to

Eloqua. For example, it may be useful to pass the dynamic date on the Create Lead call to track the

exact time when the SFDC Lead ID was populated in Eloqua.

ëNote: After mapping a lead scoring model in an action, the other models will no longer

be available for mapping in that action. Users will need to create another action to map

another lead scoring model.

Add more mappings by clicking Add Field Mapping. Click the menu to delete the mapping

or switch a From Salesforce field type to static text, static date, or dynamic date.

Z Important: If you are mapping fields that have boolean picklist values,

Salesforce requires that your picklist values are represented as either

True/False or 1/0

If you select Advanced Mode from the menu, you can enter multiple objects to be sent to a

single Salesforce field: Eloqua Object, Date, or Dynamic Date. You can also type static text into

the box as needed. For contacts, you can use Advanced Mode to select a Contact and its fields. For

custom objects, the Advanced Mode allows you to select a custom object and its related Contact

fields.

26 of 102

In Advanced Mode, concatenated Eloqua values can be mapped to Salesforce fields of the

following types: reference, double, currency, text, string, ID type, and integer.

Import Rules: Specify data priority.

Data Priority: Select the priority of data to resolve conflicts on imports, such as Bulk API and CRM

Integration. If leads and contacts are being imported to Oracle Eloqua contacts, there may be situations

where a lead and contact with the same email address exist. Eloqua's data priority can be used to

instruct Eloqua which source, lead or contact, is higher priority. If the contact import is set to have a

higher priority than the lead import, the data imported from the contact will not be overwritten by the

27 of 102

lower priority lead data. Higher priority sources are never overwritten by lower priority sources. Data

priority needs to be specified as part of an action to ensure that higher priority sources are not

overwritten by lower priority sources from other imports.

4. Click Save.

Your action is created and can be used in a program or campaign.

Click the drop-down list to modify the action. You can edit, enable, disable, duplicate,

or view report data for the action. If an action is disabled, you can delete it. If you

attempt to delete an action that is used on a canvas, a warning message will display,

but it can be overwritten if desired.

Z Important: If an action is being used within a program or campaign and the

action is disabled, contacts will not be processed until the action is enabled. Once

the action has been re-enabled, the app will process all contacts.

Creating campaign actions

Actions are data transactions between Oracle Eloqua and Salesforce. The Campaign

Actions page is where you create actions to send data to Salesforce when campaigns

change status. These actions are used for sending newly created campaigns to

28 of 102

Salesforce, as well as sending updates to existing campaigns to Salesforce (provided

the Eloqua campaign has a Salesforce campaign ID).

¤ Tip: To sync your campaign with Salesforce, check the Sync with CRM box in

your campaign's advanced settings (open a campaign > Options > Campaign

Settings > Advanced). The CRM Campaign ID field populates after Oracle Eloqua

syncs with Salesforce for the first time. This field (CRM Id) is used as a unique

identifier for campaign actions. Map at least one more field in addition to the

CRM Id.

Campaigns in Salesforce may also be imported into Eloqua to allow for bi-directional

updates between the two applications. When a campaign action is enabled, any

campaign imports using different connections are automatically disabled.

Good to know

Users can map the Salesforce URL field to the Eloqua Large Text and Text fields. Use the

Large Text field if the value in your URL field contains more than 100 characters. Mapping

the URL field to any other Eloqua field results in an error.

29 of 102

Prerequisites

Configured connection

To create a campaign action:

1. In the Salesforce Integration app, click Campaigns.

2. On the Campaign Actions tab, click Add Campaign Action and select a connection for which

you want to create a new action.

3. Complete the action details:

ëNote: Each action can map up to a maximum of 249 fields. See the Eloqua

Developer Help Center for more information.

30 of 102

Action Name: Enter a name for the action.

Object Mapping: The Eloqua Object is set to Campaign and cannot be modified. To see available

fields, select a top-level object from the Salesforce Object list.

(Optional) Synchronize Campaign Member Status Values: If you select Campaign for the

Salesforce Object, the Synchronize Campaign Member Status Values option displays. Enable this

option if you want to synchronize Campaign Member status values to Salesforce Campaigns. The

synchronization will occur after updates are sent from an Eloqua Campaign object to a Campaign

Object in Salesforce. The Salesforce App will synchronize values defined under the "Display Name"

column on the "Campaign Member Status Values" screen in Eloqua as Salesforce Campaign

Member statuses, while removing any duplicate values.

Z Important: This feature is currently released under our Controlled Availability program.

To request access to this feature, please log in to My Oracle Support

(https://support.oracle.com) and create a service request.

(Optional) Synchronize Campaign Member Status Responded Flag: If you select Campaign for

the Salesforce Object, users can select the Synchronize Campaign Member Status Responded Flag.

Enable this option if you want to set the Campaign Member Status Responded value to true for all

Campaign Member Status Values synced from Eloqua. The synchronization will occur after

updates are sent from an Eloqua Campaign object to a Campaign Object in Salesforce. Note that

the Salesforce App will not sync the “Responded” column setting set in the Eloqua response rules.

In addition, the Salesforce App will not alter the value of any Salesforce Campaign Member Status

Values did not originate from Eloqua.

Z Important: This feature is currently released under our Controlled Availability program.

To request access to this feature, please log in to My Oracle Support

(https://support.oracle.com) and create a service request.

31 of 102

Update Salesforce Fields: The unique identifiers are automatically determined by the Eloqua and

Salesforce objects in the object mapping section. The Eloqua unique identifier is CRM Id. You must

add at least one additional mapping by clicking Add Field Mapping. For each set of fields, specify

the Salesforce field that will be mapped to Eloqua contacts. Click the menu to delete the

mapping, or switch the field type to static text, static date, or dynamic date.

Update Eloqua Fields: The unique identifiers are automatically determined by the Eloqua and

Salesforce Objects in Object Mapping. The Eloqua unique identifier is CRM Id. Add more mappings

by clicking Add Import Field Mapping. For each set of fields, specify the Eloqua field that will be

mapped to Salesforce contacts. Click the menu to delete the mapping or use Advanced

Mode to switch a From Eloqua field type to static text, static date, or dynamic date.

Z Important: If you are mapping fields that have boolean picklist values,

Salesforce requires that your picklist values are represented as either

True/False or 1/0

If you select Advanced Mode from the menu, you can enter multiple objects to be sent to a

single Salesforce field: Eloqua Object, Date, or Dynamic Date. You can also type static text into

the box as needed. For contacts, you can use Advanced Mode to select a Contact and its fields. For

custom objects, the Advanced Mode allows you to select a custom object and its related Contact

fields.

32 of 102

In Advanced Mode, concatenated Eloqua values can be mapped to Salesforce fields of the

following types: reference, double, currency, text, string, ID type, and integer.

4. Click Create Campaign Action and then click Close to return to the Campaign Actions page.

To modify an action, click its menu and choose and option. You can edit, enable or

disable, duplicate, or view report data for the action. Only one campaign action can be

33 of 102

enabled at a given time. Enabling a new action will disable an existing one. You can

delete disabled actions.

Creating response actions

Actions are data transactions between Eloqua and Salesforce. The Campaigns >

Response Actions tab is where you create actions to send data to Salesforce based on

response rules configured in your Oracle Eloqua instance. When a response occurs,

Oracle Eloqua records the response based on priority and the response is sent to a

Salesforce custom object.

Z Important: Avoid uploading contact activities that are older than 30 days.

These contact activities will not be sent to the Salesforce Integration app.

Good to know

Users can map the Salesforce URL field to the Eloqua Large Text and Text fields. Use the

Large Text field if the value in your URL field contains more than 100 characters. Mapping

the URL field to any other Eloqua field results in an error.

34 of 102

Contacts must have a Response ID for campaign response actions. If a contact is missing the

Response ID, Eloqua alerts you with an error message.

For the Account, Contact, and Lead Salesforce objects, you can split the Address field onto a

new line in Oracle Eloqua, and the split will remain at the same place once that address is

pushed to Salesforce and imported back into Eloqua. For example, if you split an address to

a new line after 80 characters, and that's pushed to Salesforce, the address will still be split

to a new line at 80 characters once it's imported back into Eloqua.

For the Campaign Member Salesforce Object, the Response Action queries Salesforce for an

existing Campaign Member ID for the given CRM Campaign ID and Lead ID or Contact ID. If

the returned Campaign Member ID is not blank, the app initiates an "Update" call to

Salesforce using this Campaign Member ID. Otherwise, it initiates a "Create" call to

Salesforce.

Z Important: This feature is currently released under our Controlled Availability

program. To request access to this feature, please log in to My Oracle Support

(https://support.oracle.com) and create a service request.

You can associate both Contact ID and Lead ID in the same Response Action call for

reporting purposes. If both Contact ID and Lead ID are present on an Eloqua Contact, the

Salesforce App will automatically generate two separate calls to Salesforce, associate both

Salesforce Contact and Lead to the Salesforce Campaign.

Z Important: This feature is currently released under our Controlled Availability

program. To request access to this feature, please log in to My Oracle Support

(https://support.oracle.com) and create a service request.

35 of 102

Prerequisites

A configured connection

A campaign object or a custom object in Salesforce for Eloqua campaigns

A response rule configured in your Oracle Eloqua instance

To create a response action:

1. In the Salesforce Integration app, click Campaigns.

2. Click the Response Actions tab.

3. Click Add Response Action and select a connection for which you want to create a new

action. The Create Response Action page is displayed.

4. Complete the response action details:

ëNote: Each action can map up to a maximum of 249 fields. See the Eloqua

Developer Help Center for more information.

Action Name: Enter a name for the action.

36 of 102

Campaign Response: The Eloqua object is set to CampaignResponse and cannot be modified.

Salesforce Object: Select a top-level object from the list, such as Campaign Member.

If you've selected Campaign Member for the Salesforce Object, the following mappings are set by

the Salesforce Integration app and cannot be modified: Status in the CampaignResponse section,

Contact ID and Lead ID in the Contact section, as well as Campaign ID in the Campaign section.

Update Salesforce Fields: The Eloqua unique identifier is Integration Return Value. The

Salesforce unique identifier is determined by the Salesforce Object selected in Object Mapping. For

example, if you select Campaign, the unique identifier is Campaign ID. Add more mappings by

clicking Add Field Mapping. For each set of fields, specify the Salesforce field that will be mapped

to Eloqua contacts. Click the menu icon to delete the mapping, or use Advanced Mode to

switch the field type to static text, static date, or dynamic date.

If you select Advanced Mode from the menu, you can enter multiple objects to be sent to a

single Salesforce field: Eloqua Object, Date, or Dynamic Date. You can also type static text into

the box as needed. For contacts, you can use Advanced Mode to select a Contact and its fields. For

custom objects, the Advanced Mode allows you to select a custom object and its related Contact

fields.

37 of 102

In Advanced Mode, concatenated Eloqua values can be mapped to Salesforce fields of the

following types: reference, double, currency, text, string, ID type, and integer.

5. (Optional) Click +Add Related Object, select an object from the list, and click Add Related

Object.

6. Click Save Response Action and click Close to be returned to the Response Actions page.

To modify the action, click the menu to display the options. You can edit, enable or

disable, duplicate, or view report data for the action. Only one campaign response

action can be enabled at a given time. Enabling a new action will disable an existing

one. You can delete disabled actions.

38 of 102

Copying Salesforce fields into Eloqua

With the Salesforce Integration app, Oracle Eloqua users can copy individual

Salesforce object fields into a standard Oracle Eloqua object or an Oracle Eloqua

custom object. The fields are then available in an action to transfer data from the

Oracle Eloqua object to the Salesforce object.

To copy Salesforce fields into an Oracle Eloqua object or custom object:

1. In the Salesforce Integration app, click Actions.

2. Click on an action.

3. Click Copy Salesforce Fields.

The Copy Salesforce Fields page opens. The Display Name column lists the Salesforce fields

which are not currently available in the Oracle Eloqua object source and so can be copied

into the object source.

4. Check the boxes of the fields you want to copy.

5. Click Copy.

A status bar displays the copying status. Once the copying is complete, you can retry any

failed actions.

Configuring test runs for actions

When using the Salesforce Integration app, you can run any action, including a custom

object action, with a configured test payload immediately without needing to wait until

39 of 102

the action is triggered on a canvas. This allows you to test the action for errors using

test contacts selected by you. The test action results will be included in the action daily

report, but you can also choose to exclude these results.

In this topic, you'll learn about:

1. Adding test contacts

2. Running an Action with a test payload

3. Excluding the test payload from daily reports

Adding test contacts

Before you're able to run a test action, you'll need to configure the test payload.

To add a contact to a test payload:

1. In the Salesforce Integration app, navigate to the Actions tab.

2. Click on an action.

3. Under Test Configuration, type in a name or email address to search for a contact.

4. Click on the contact to add them.

5. Click Save Action.

40 of 102

Running an action with a test payload

Once you've configured the test payload for an action, you can now use the test

payload to run the action.

To run a test action:

1. In the Salesforce Integration app, navigate to the Actions tab.

Click beside an Action and select Run Action.

You will see the action run's status in the status bar at the top of the dialog.

Excluding the test payload from daily reports

If you don't want to mix the data from your test action with other action runs, exclude

the test payload from daily reports.

To exclude the test payload from daily reports:

1. In the Salesforce Integration app, navigate to the Actions tab.

2. Locate the action for which you want to view daily report data, click the list, and select View

Reports.

41 of 102

3. Click Hide Runs With Test Contacts.

Creating imports

Imports are data transactions from Salesforce into Oracle Eloqua. The Salesforce

Integration app executes imports every 15 minutes. After an import has been

scheduled, an import schedule does not display because imports are executed so

often. If an import needs to be performed off schedule, it can be executed on demand.

An import may fail due to various reasons such as connection or data related issues.

Some of these issues will cause an entire import to fail. You can setup email

notifications to alert you when import errors occur.

The following imports are recommended:

Leads

Contacts

Accounts

Opportunities

42 of 102

When viewing your imports, disabled imports are dimmed to indicate their status.

There are several indicators in your list of imports to help you quickly get an overview

of their status.