Integration app FAQs

For more FAQs, see here.

Q. What Salesforce version is required to use the Integration app?

A. Any Salesforce version that comes with API access is supported. For more details, see Salesforce editions with API access.

Q. Can we revert to our native integration if issues arise?

A. The two integrations can run side-by-side.

Q. What are the minimum required SFDC OAuth scopes?

A. At a minimum, the following scopes are required:

  • Access and manage your data (api)
  • Full access (full)
  • Perform requests on your behalf at any time (refresh_token, offline_access)

The custom_permissions scope is recommended. Determining whether it is needed depends on your Salesforce configuration.

Q. I am having trouble creating a connection for the Integration app. Why won't it allow me to save the connection?

A. In the Default Field Mappings section (below the Connected App section), verify that you have mapped the ID fields.

Q. When I try to configure the Integration app, some Salesforce fields are missing. What can I do?

A. Verify the Salesforce permissions for the account used to authenticate the app. Determine whether the account has read-only access to specific Salesforce objects and their fields, because read-only fields are not visible to Eloqua's Integration app.

Q. Do I need to refresh the app to get the latest Salesforce updates?

A. The Integration app updates automatically. You do not need to refresh it.

Q. I do not see a configured action in any canvas. What can I do?

A. Verify that your configured action is enabled. Disabled actions are not displayed on any canvas.

Q. Does the Integration app require Salesforce's 18-character ID?

A. Yes, 15-character IDs are not supported. If your instance currently uses 15-character IDs, data will either need to be removed or the IDs updated.

Q. We use an internal SSO (Single Sign-On) service to login into Salesforce, and we run into the HTTP/302 error while trying to authenticate the SFDC App. What can we do to resolve it?

A. You will need to specify the configuration details of your SSO service in the Web App Setting section of the SFDC Connected App. Please contact your SFDC Admin for further help.

Q. What is the process for switching from 15- to 18-character IDs?

A. A check box on every external call (and within auto-sync settings) to use 15- or 18-character IDs must be changed to 18-character.

An image of the External Call window where you can specify 18-character IDs

If data is being sent from Salesforce into Eloqua custom objects or Eloqua's opportunity object, switching to 18-character IDs may be difficult. For custom object imports, you can optionally delete all data from the custom object, change the auto-sync to use 18-character IDs, then re-synchronize all data into the custom object. The Oracle Operations team must make any Eloqua opportunity object updates.

Q. Does the app support multiple Salesforce instances?

A. The app supports syncing data to any Salesforce instance and multiple instances simultaneously.

Q. Does the app support Salesforce's custom objects?


  • All Salesforce objects are supported bidirectionally.
  • All Eloqua objects are supported except for accounts in actions.

Q. What is the status of an app-based integration with SFDC?

A. A new Integration App is now generally available. The Controlled Availability Program has come to an end. No action is required from Controlled Availability Program participants.

Q. What are the differences between native integration and the new integration?

A. The new integration offers the following key benefits:

  • Faster outbound and inbound data flow. 
  • Easier to configure and use.
  • Supports multiple connections.

Q. Where can I access the new SFDC Integration App?

A. Please visit the Cloud Marketplace:

Q. Does the new integration leverage Oracle Integration Cloud Service (ICS)?

A. No.

Q. Does the App require the use of SFDC 18-char ID?

A. There is a checkbox on every external call (and within auto-sync settings) to use 15 or 18 character IDs. This must be changed to 18 characters. If data is being from SFDC into Eloqua custom objects or Eloqua's opportunity object, switching to 18 character IDs may be a bit more laborious. For custom object imports, the worst case is to delete all data from the custom object, change the auto-sync to use 18 character IDs, then re-sync all data into the custom object. Eloqua's opportunity object must be updated by the Oracle Ops Team.

Q. How is Lead conversion handled in imports?

A. Converted leads can be imported by using a filter.

Q. We are having trouble creating a Connection in Eloqua Production for the SFDC Integration App. It won’t allow me to save the connection.

A. Please get the ID fields been mapped (just below the connected app details).

Q. How does the App compare with the Native integration?

A. The Integration app includes:

  • All SFDC objects supported, bidirectionally.
  • All Eloqua objects supported with the exception of Accounts in Actions.
  • Closed-Loop Reporting is supported.
  • Configurable Import Frequency - min every 15 minutes.
  • Actions used in a Canvas.
  • Nomenclature changes:
    SFDC AppNative Integration
    ActionsInternal Events/External Calls

Q. How do I transition from the Native Integration to the new App?

A. Once the App is installed and the connection to Salesforce is configured, you need to add new Imports and Actions in the App that follow the same object and field mapping rules as defined in existing Native Integration Assets. In addition, you need to add any applicable Actions to a Campaign or Program Canvas.

Q. Can the Jordo's playbookbe applied to the new App?

A. No, the Jordo's playbook is applicable only in SFDC Native Integration. The "Email Address Change" workflow is on the Roadmap.

Q. If I re-install or update the App, will I lose configured assets?

A. When you update the App, all existing configurations will be preserved. If you re-install the App, you will need to configure the App from scratch.

Q. When I configure an import, for each field I would like to specify if it should be updated if the new value is not blank. This option is available in SFDC Native Integration, however, it is not in the new App. Was it overlooked?

A. The SFDC App is designed to follow field configuration rules as defined in the core Eloqua, where the default setting is set to “Update if new value is not blank”. Users can modify this setting as needed.

Learn more Integration app

Salesforce Integration app, SFDC, FAQ, 18-character ID, lead conversion, OAuth