Product Notice: Support for Native Salesforce Integration Ending Feb 1, 2021
View to see a recap of Eloqua's App-based integration with Salesforce, recent enhancements, and recommendations on the migration process planning and execution.
Effective February 1, 2021, Oracle will no longer support the Oracle Eloqua native Salesforce integration. Note: This does not impact the Salesforce Integration app that was introduced in Feb. 2019 with the Eloqua 19A release and Eloqua continues to support customers using Salesforce.com CRM.
In light of the arrival of the new Salesforce Integration app (released in Feb. 2019), Oracle announced the end of support for the ‘native’ Eloqua integration for Salesforce.com CRM on Feb. 1, 2021. It is recommended that you start to evaluate your current native integration setup and configuration and map it to the Salesforce integration app.
The Salesforce integration app includes numerous enhancements and benefits, including:
- Incredibly fast lead flow, using Program Canvas
- A simplified user interface, easing setup, and maintenance
- Frequent inbound updates from Salesforce.com to Eloqua
- Works with multiple Salesforce.com CRM instances
- An expanded set of objects, including:
- Bi-directional support of Salesforce.com Leads, Contacts, Accounts, Opportunities, Custom Objects, and more
- Eloqua Opportunities – used for Eloqua's Closed-Loop Reporting
- Bi-directional support of Eloqua Custom Objects
- And new features in future releases to ease administration, introduce new capabilities, and more – watch the Eloqua Release Center for updates.
- Now: Start evaluating your current native integration setup and determine an action plan to move to the Salesforce Integration app
- Feb. 1, 2021: Oracle Eloqua ceases support of the native Salesforce.com integration
The Oracle Eloqua Product Team has hosted several webinars to prepare for the native Salesforce.com integration and the new app-based integration. All sessions have been recorded for on-demand viewing if you were not able to attend:
- 1st Session: February 19, 2020 - Watch Here
- 2nd Session: May 22, 2020 - Watch Here
- 3rd Session: November 19, 2020 - Watch Here
- 4th Session: July 20, 2021 - Watch Here
Customers should evaluate their Salesforce.com integration configuration and map it to the new integration app. Some elements will map closely, while others may need to be adjusted based on new approaches in the integration of related elements such as Program Builder (native integration) and Program Canvas (new integration). Please see the Eloqua Help Center for details on configuring the Oracle Eloqua Salesforce.com Integration app.
In addition, the OracleU Eloqua/SFDC Integration App Intro course has been made generally available and does not require an Oracle University subscription, thus it's free to watch! This course provides an overview of the new Salesforce Integration App, demonstrates how to configure and use the application, and explores a common case for use.
- Oracle Eloqua Help Center
- Oracle Cloud Marketplace Listing
- On-Demand Video: CRM Integrations and Extensibility (features the new Salesforce Integration App!)
- New Free Oracle University Course: The Eloqua/SFDC Integration App Intro course is now absolutely free and available to everyone here.
Q: Where can I find the new Salesforce integration app?
A: The new integration app can be found here. The Marketplace listing contains screenshots, links to documentation, general information about the integration, and a button to install the app in Eloqua.
Q: Is there documentation for the new integration app?
A: Yes! Documentation can be found here.
Q: When is Oracle Eloqua Salesforce.com's native integration support ending? Can I still use it?
A: Support will end on February 01, 2021. After it ends, all active native Salesforce.com integrations will continue to work, however, Oracle Eloqua Support will no longer accept related inquiries or requests.
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 installation of the App be done when the native one is still running? Can we connect the new App with Sandbox and continue using the native App with production, so that we can migrate to the new App with no downtime?
A: Yes, it can.
Q: Are there any prerequisites I need to be aware of?
A: The new Oracle Eloqua Salesforce.com Integration App requires Salesforce 18-character record IDs. If the app is installed on an instance that is using 15-character IDs, it will not work properly. Please refer to the Topliners page for more details about updating Salesforce record IDs in Eloqua.
Q: How is the new integration more secure?
A: The new integration uses OAuth 2.0 authentication method, which includes a one-time authentication process on the Salesforce app that uniquely identifies the App and does not store the username or password on the Eloqua site.
Q: Can existing CRM configuration be migrated automatically?
A: Some existing CRM configurations can be migrated through a simple sequence of steps in the new App. Please refer to the documentation above for more details.
Q: Does the new integration have auto-syncs like the old integration, importing data from Salesforce.com into Oracle Eloqua? Do you have the same ability to filter the new inbound syncs the same way you can with auto-syncs?
A: Yes. Auto-syncs (native integration) are named Imports in the integration app. Once created and enabled, imports run every 15 minutes automatically. In addition, the filter can be tested without running the import.
Q: Does the new integration have internal events and external calls for lead creation?
A: Yes. Internal events/external calls (native integration) are combined and named Actions in the integration app.
Q: Can the new integration app be used within Program Builder?
A: Program Builder (native integration) cannot be used with the new integration app. Program Canvas replaces Program Builder and delivers faster CRM update workflow evaluation.
Q: Can a form submit put a contact into Program Canvas instead of Program Builder?
A: Yes. The form processing step “Add to Program” is used to add contacts who submit a form directly to any listener step on a Program Canvas program.
Q: Is there a way to allow the App to be used only by customer admins?
A: The app catalog has security controls in place to control access to select users/groups. Actions placed on a Canvas are available to any user that has access to the Canvas. We are evaluating adding security controls to govern access to action placement on a Canvas.
Q: Does the new App allow us to test as we do with the current native App (currently, we can push one record at a time while testing)?
A: Yes, this functionality is available.
Q: Will the reporting of error be much easier for debugging use? The old reporting was very static and cumbersome for debugging.
A: Full error responses are included in the Integration App. We believe this is better in many ways compared to Native Integration, and we will continue to make improvements as we received feedback.