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 |
|---|---|---|---|
| 29 APR 2022 | Created initial document. |
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 |
|
||
Custom Contact Views for Oracle Eloqua Sales Tools for Microsoft Outlook Add-in |
||||||
A new metric, Auto Click, is added to the Email Clickthrough Subject Area. You can use this metric to view the number of click-throughs detected as being auto-clicked by scanning or privacy tools. These click-throughs are not included in the Total Clickthroughs metric or any associated click-through rates. Auto Click metrics will only be captured after the 22B update.
Oracle Eloqua uses this new metric to calculate Total Clickthroughs more accurately by excluding click-throughs that are detected to be automatically clicked by scanning or privacy tools. This helps you make decisions based on click-through behaviors where a contact clicked a tracked link in an email.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Updates to Oracle CX Apps for Eloqua are now scheduled as monthly maintenance, and do not require any platform downtime. View the 2022 Oracle CX Apps Release Dates.
Infinity Action Center App Updates
The Oracle Infinity Action Center app has been updated to allow matching on hashed ID email address and phone number fields on the page.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
- This feature is currently released under our Controlled Availability program. To request access to this feature, please log in to My Oracle Support and create a service request. Note that access to this feature is not guaranteed and will be evaluated based on customer needs.
-
Oracle Infinity Action Center and Oracle Infinity Streams are required to use this feature. Please contact your account manager for more information.
Key Resources
With the Oracle Commerce app, you can register Oracle Eloqua contacts as shoppers in your Commerce instance as well as grant them promotions.
By having Commerce actions available in Eloqua, you can use them as you're building campaigns to drive increased conversion.
Steps to Enable
Oracle Commerce is required to use this feature. Please contact your account manager for more information.
Key Resources
New SMS Decision Steps on Campaign Canvas
Two new decision steps for SMS will be available when you design campaigns using the Campaign Canvas:
- Replied to SMS: Evaluates incoming reply keywords and messages
- Sent SMS: Evaluates send of a message to contacts
These new decision steps provide you with more flexibility in your SMS-specific and cross-channel campaign orchestration. They empower you to better leverage SMS activity data on the campaign canvas. Together with the existing Clicked SMS step, these decision blocks give you more granular control over the actions you take based on SMS data.
Steps to Enable
- SMS is available as an add-on capability for Oracle Eloqua. Please contact your account manager for additional information and pricing.
- No additional steps are required for customers that are already enabled for SMS.
Key Resources
Custom Contact Views for Oracle Eloqua Sales Tools for Microsoft Outlook Add-in
As an Oracle Eloqua administrator, you can now create custom contact views for your sales reps who use the Oracle Eloqua Sales Tools for Microsoft Outlook.
- Administrators create and share contact views with sales rep using existing Eloqua contact view management and access settings.
- When sales reps with the Manage Contacts action permission create new Eloqua contacts using the add-in, they can now choose the contact view to use.
This enhancement helps sales reps create complete contact records, so that you can better ensure the quality of contact data in your organization's database. It also provides sales reps choice of which contact view to use.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
-
This enhancement is expected to be delivered as part of our 22.05 CX Apps release.
- Only sales reps with Manage Contacts action permission can create contacts. Consider your own use cases and data management practices before enabling contact creation for your reps.
Key Resources
Role Information
- Eloqua administrator follows existing flow to create contact fields and contact views.
- Administrator grants Manage Contacts permissions to Group or User to manage the access to these views.
If you are an Eloqua administrator, you will be able to limit the number of sales emails that your reps can send to the same contact over a period of time.
Eloqua will look back the specified number of days to determine if the send limit is being exceeded. For example, if you enable the option today, with the number of days set to 7 and the send limit set to 1, Eloqua will look back at the last 7 days to determine if there has been 1 email sent out to a given contact from Engage. If no email has been sent out over the last 7 days, the sales rep will be able to send one email to that contact.
These limits can help you prevent contact fatigue and unsubscribes, which also helps maintain your domain's reputation.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
-
This enhancement is expected to be delivered as part of our 22.05 CX Apps release.
- After the Engage app update is available for your environment, you can request access to this Controlled Availability feature. Log in to My Oracle Support and create a service request.
Tips And Considerations
- Send limits apply to both Engage and Oracle Eloqua Sales Tools for Microsoft Outlook.
Key Resources
Role Information
This feature is intended for Eloqua users with client administrator rights
As of the 22B update, Oracle Eloqua will limit the number of lead scoring models that you can have active. Support for multiple active lead score models is included in the Standard and Enterprise editions or as an add-on to the Basic package.
Lead scoring helps your marketing and sales teams identify where a prospect is in the buying process and the right follow-up.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The default limits per editions are as follows:
- Enterprise: 30
- Standard: 15
- Basic: 1
Limits are per edition, per instance. For example, if you have two Eloqua instances with the Standard edition, each instance would be limited to 15 lead scoring models.
If you are an existing customer who has more than the limit for your edition, then your current number of active lead scoring models will be used as the cap instead of the default edition limit.
Key Resources
If you have SMS enabled in your Oracle Eloqua environment, you will see the following enhancements:
- You can choose to apply phone number validation on the Contact Fields Mobile Phone and Business Phone. Validation is available in the Contact user interface and on form fields.
- When designing forms, you can add form processing steps to manage SMS preferences, such as phone number opt-in and opt-out, subscribe contacts globally, and unsubscribe contacts globally.
- You can manage invalid keyword response messages from the SMS Setup page. You can create one response messages for each code, to be sent for invalid incoming keywords.
Allowing for SMS-specific and cross-channel campaign orchestration, Eloqua's 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.
- No additional steps are required for customers that are already enabled for SMS.
Key Resources
Audience Split Decision Step on Contact Program Canvas
Audience Split is a new decision step on the Contact Program Canvas. This step splits the audience into two groups. The decision is a percentage-based routing to either a Yes or No path.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Tip: The Audience Split decision step is also available on the Campaign Canvas as of the 22A update.
Key Resources
Oracle Eloqua has the following improvements in data export security:
- Data Export will now honor Contact Security based on the Eloqua user that creates the export.
- The Eloqua user that creates the export will now be added to the Data Export area.
This is a security improvement that prevents users from exporting contacts that they don't have access to view.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- If you are using Contact Security, confirm the User that created any contact export has access to all required labels.
- For exports before 22B, the user who created the export can be confirmed in the Audit Log area.
Key Resources
- Exporting Contacts or Accounts
- Contact Security
- Auditing in Oracle Eloqua
- Eloqua Product Notice: Data Export Will Honor Contact Security [May 2022]
Chrome 100 and Firefox 98 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.
Automated Certificate Management
Oracle Eloqua is moving toward securing all customer-branded domains with Eloqua-owed DV SAN certificates. This will include automatic renewal of the certificates prior to their expiration.
Please note that the option is grayed-out until you've enabled the automation. Please see steps to enable below.
With the ongoing changes from browsers and ISPs (internet service providers), it’s becoming increasing important to secure all domains to properly support content rendering and deliverability.
Eloqua highly recommends that you enable the automated certificate management feature to ensure that all your domains are secured and automatically renewed prior to expiry to prevent any downtime related to content rendering.
If you are a new customer, you can quickly secure branded domains without having to purchase an SSL certificate. For existing customers, Eloqua will start securing all actively used branded domains.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
- This is a Controlled Availability feature that will be rolled out over time. PODs 6 and 7 will have this feature available in the 22B update. We plan to make it available for other PODs in the months following the 22B update.
- There is no additional cost for this feature, however you may be required to work with your IT team to make changes to your existing domain configuration.
- You can check if this feature is enabled for your site by checking the certificate management screen. When it is available in your environment, you can request access to this Controlled Availability feature by logging into My Oracle Support and creating a service request (SR).
Key Resources
The Oracle Eloqua Bulk API has the following updates:
- Bulk API form submit activity exports will now check the Visitor link to Contacts by first checking the Contact ID set upon form submission.
- Import definitions now include an updateRuleByField parameter, which specifies how Eloqua should handle updating records by field. If you do not specify an updateRuleByField, or leave a field out of updateRuleByField, then the rule type defaults to the rule set with updateRule.
This behavior is being changed to be consistent with how the Application API and Insight link Contact information to form submissions.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Key Resources
CDO App API Endpoints Search Limits
With the 22B update, Custom Data Objects (CDOs) with more than one million records are being updated to accept only one search request at a time using Application API 1.0 and 2.0 endpoints in certain conditions. Requests will be limited when searching using only non-indexed fields or not including an indexing field without a leading wildcard.
This enhancement improves system stability and performance for all Oracle Eloqua customers.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Only the following two endpoints are impacted:
- Application API 1.0: Retrieve a list of custom object data: GET /api/REST/1.0/data/customObject/{id}
- Application API 2.0: Retrieve a list of custom object data: GET /api/REST/2.0/data/customObject/{parentId}/instances
Tips And Considerations
Considerations:
-
Limit will be per user and per custom object.
-
If the limit is exceeded, Oracle Eloqua will respond with a 429 Too Many Requests error.
Tips:
- Do not use leading wildcard searches. To produce the most efficient search, use the wildcard character (*) after the value whenever possible.
- Use unique values when searching for custom object records using custom fields. If you plan to heavily search for custom object records by a custom field, then this custom field should be set to a unique code, email, or display name. In this case, an index will be added to the custom field.
- Maintain a low custom object record volume. Keep the number of records as low as possible in custom objects. For example, you can regularly delete unneeded custom object records.
Key Resources
-
Retrieve a List of Custom Object Data (Application API 1.0)
-
Retrieve a List of Custom Object Data (Application API 2.0)
-
Product Notice: Eloqua Retrieve a List of CDO App API Endpoints Search Limits [May 2022]