Eloqua Product Update: New Salesforce Integration App is Here
Make way for the new Salesforce Integration App – sharing data with Eloqua is better than ever
The new Salesforce Integration app is now generally available!
With the new Salesforce Integration app, you can share data between Salesforce and Eloqua with the best-in-class SFDC CRM Integration that will replace and outperform the existing integration in terms of speed to lead, scalability, reliability, user experience, and functionality. Using the new Salesforce Integration app, you will be using the best version for its performance, scale, and ease of use.
New Salesforce Integration App unites sales and marketing teams to drive revenue through the sharing of data
- Faster, both outbound (lead creation) and inbound (imports)
- Simplified user interface, easing setup and maintenance
- Better reporting options/error handling
- As of March 20, 2019, the Salesforce Integration App is now generally available!
- Cloud Marketplace SFDC App
- Eloqua Help Center: Salesforce Integration App
- Saleforce Configuration App Course
- For more information, check out the Eloqua Learning Subscription Page
FREQUENTLY ASKED QUESTIONS
|What is the status of an app-based integration with SFDC? ||A new Salesforce Integration App is now generally available. The Controlled Availability Program has come to an end. No action is required from Controlled Availability Program participants.|
What are the differences between native integration and the new integration?
The new integration offers the following key benefits:
|Where can I access the new SFDC Integration App?||Please visit the Cloud Marketplace: https://cloudmarketplace.oracle.com/marketplace/app/AppSalesforce|
|Does the new integration leverage Oracle Integration Cloud Service (ICS)?||No|
|Does the App require the use of SFDC 18-char ID?||Yes, we do require the use of the 18 character IDs. If the app is installed on an instance that is using 15 character IDs, it will not work properly.|
|What is a process for switching from 15 ID to 18 ID?|
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.
|How is Lead conversion handled in imports?||Converted leads can be imported by using a filter|
|What are the minimum SFDC OAuth Scopes required?|
At the very least the following 3 scopes are required:
|We are having trouble creating a Connection in Eloqua Production for the SFDC Integration App. It won’t allow me to save the connection. ||Please get the ID fields been mapped (just below the connected app details)|
|Does the App support multiple SFDC instances?||The app will support syncing data to any SFDC instance, as well as multiple instances simultaneously.|
|Does the app support SFDC Custom objects?||The integration allows any object in SFDC to be imported to Eloqua Accounts, Contacts, Custom Objects, and Campaigns.|
|When I try to configure the app, some SFDC fields are missing. What can I do?||Please verify the permissions of the SFDC account used to authenticate the App. If this account has read-only access to specific SFDC objects and their fields, these fields will not be visible to the App.|
|Do I need to refresh the App to get the latest SFDC updates?||No, the app updates automatically. You do not need to refresh it.|
|I do not see configured Action in any Canvas. What can I do?||Please check if your configured Action is enabled. Disabled Actions will not be displayed in any canvas.|
|How does the App compare with the Native integration?|
a. All SFDC objects supported, bidirectionally
b. All Eloqua objects supported with the exception of Accounts in Actions
c. Closed-Loop Reporting is supported
d. Configurable Import Frequency - min every 15 minutes
e. Actions used in a Canvas
f. Nomenclature changes:
|How do I transition from the Native Integration to the new App?||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.|
|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?||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.|
Can the Jordo's playbook be applied to the new App?
|No, the Jordo's playbook is applicable only in SFDC Native Integration. The "Email Address Change" workflow is on the Roadmap.|
|If I re-install or update the App, will I lose configured assets?||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.|
|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?||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.|
Group Product Manager, CX - Marketing: Eloqua