This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 19 Nov 2021 | Created initial document. |
Oracle Eloqua Cloud App enhancements (including enhancements for the Salesforce App) for POD 1, 2, and 7 customers will arrive on Dec 10th, 2021. These enhancements were previously expected to have been available as part of the Eloqua 21D update which arrives on Nov 19th, 2021 for POD 1, 2, and 7 customers. No other changes are expected with the timing of the other elements of the 21D update, and no additional maintenance windows are required as the Eloqua Cloud Apps enhancements can be enabled without additional downtime.***There are no changes to the release dates or inclusions for POD 3, 4 and 6 - this change only impacts 1, 2, and 7.*** Learn more about Oracle Eloqua release dates.
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at omcdocumentation_ca@oracle.com.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Salesforce.com Integration App - Campaign Response Action Update |
||||||
Salesforce.com Integration App - Excluding Multiple Email Send Types |
||||||
The following reports are now available for customers who leverage the SMS add-on for Oracle Eloqua:
Contact-level reports:
-
Review SMS activity for a contact using the contact record’s Activity Log and Recent Activity tabs
Operational reports:
- Review recent SMS activities using the SMS operational reports available from the SMS message
- Review recent SMS activities for all SMS messages associated to a campaign using the SMS Statistics operational report
Insight (OBIEE) usage reports:
- SMS Usage Overview reports to track sends and deliveries by day, month, quarter, year•
- SMS Activity subject area to build custom SMS reports for your analytics needs
Use this comprehensive reporting on native SMS campaigns to demonstrate your results and optimize your cross channel campaign orchestration.
Steps to Enable
SMS is available as an add-on capability for Oracle Eloqua. Please contact your account manager for additional information and pricing.
Oracle Maxymiser Integration App
An Oracle Maxymiser Integration app is now generally available. It was previously part of our controlled availability program.
Using this app, you can send attributes from Oracle Eloqua contacts to Maxymiser to be used for personalizing web pages. This data flow is performed via an Eloqua campaign step, allowing a connected journey and consistent experience from email to website.
This results in better educated and supported buyers and higher velocity in the sales cycle.
Steps to Enable
Oracle Maxymiser is required to use this feature.
Key Resources
Salesforce.com Integration App - Campaign Response Action Update
This change has been made to the Salesforce.com Integration app to prevent errors on Campaign Response Action Update:
- The Response Action now queries Salesforce for an existing Campaign Member ID for the given CRM Campaign ID and Lead ID/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.
This helps prevent data sync errors and provides more flexible integration workflows.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
Key Resources
Salesforce.com Integration App - Excluding Multiple Email Send Types
When creating a marketing activity, you can now include or exclude multiple email send types.
This provides more granular control over volume of email-related marketing activities.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Salesforce.com Integration App - Improved User Experience
Changes have been made to the Salesforce.com Integration app to provide an improved user experience:
- You can now configure the Upsert action with Eloqua custom objects.
- You can now set up notifications to receive email notifications when scheduled syncs (imports or activities) are stopped by the app due to too many consecutive failures.
- Marketing activities reports are now updated even if there are no records to synchronize.
- Test Configurations are now available for custom object actions.
These enhancements provide better visibility into marketing activities sync status and time savings.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Salesforce.com Integration App - Native Integration Parity
Changes have been made to the Salesforce.com Integration app to provide parity with the Salesforce native integration:
- You can now synchronize Campaign Member statuses on Campaign Actions.(CA)
- You can now synchronize any two Salesforce field values into an existing Eloqua picklist.(CA)
- You can now set the update rule by field in an import.
- You can now define the Update type of Bounceback Marketing Activities if you choose Salesforce Lead or Contact object.
- The requirement that forces the field from Salesforce to be mapped to the Eloqua source object in an action that creates records in Salesforce has been removed.
- You can now associate both Contact ID and Lead ID in the same Response Action call for reporting purposes.(CA)
These enhancements enable an easier migration from the Salesforce Native Integration to the Salesforce Integration app.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
Several of the above features are part of our Controlled Availability (CA) program.
Key Resources
Modifying Campaign Start and End Date
When importing Campaigns the Start Date and End Date will no longer be updated if the Campaign is in Active, Scheduled, or Completed status. Start Date and End Date will only be updated if the Campaign is in Draft status.
This helps prevent accidental date changes from impacting Active, Scheduled, or Completed campaigns.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Contact Lead Scoring History Deletion
Oracle Eloqua now deletes lead scoring histories for deleted contacts and history records for deleted models.
This increases stability and performance.
Steps to Enable
You don't need to do anything to enable this feature.
Oracle Eloqua now offers SMS for native multi-channel orchestration. You can create SMS messages and send them to your contacts from within Eloqua.
Allowing for SMS-specific and cross-channel campaign orchestration, Eloqua's new native SMS offering helps you unify your messaging. Connect your customer experience across channels to drive more engagement with greater efficiency.
Steps to Enable
SMS is available as an add-on capability for Oracle Eloqua. Please contact your account manager for additional information and pricing.
Key Resources
Chrome 94 and Firefox 92 are the A (Best Choice) browsers for Oracle Eloqua.
These browsers are tested against a comprehensive new feature and regression test suite to provide a good experience with all functionality.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For a complete list, please see Supported Environments.
We have updated the Bulk API limits. Every Oracle Eloqua instance has the following soft limits by Bulk API sync type:
| Bulk API Sync Type | Limit |
|---|---|
| Export | 2000 per hour |
| Import | 2000 per hour |
| Sync Action | 4000 per hour |
There are many variables to sync processing. Minimal impact due to volume is expected if syncs are within these limits and following best practices
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Reminder of best practices
- Reusing definitions - A Bulk API definition can be reused as long as there is not an active sync using that definition
- Retrieving data – Always use the/syncs/<id> endpoint
- Checking a sync’s status – Avoid polling and use the callbackUrl parameter
- Exporting activities – Use filters to ensure fewer than 5M records, export one Activity Type at a time, and make multiple export requests sequentially
Key Resources