A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 19C.

New features

Application API

Retrieve list of Visitors by GUIDs

Added a new endpoint that enables you to retrieve visitor data by visitor GUID, aka externalId. This endpoint differs from the existing Retrieve visitor data endpoint, because it is a POST request that can include up to 200 visitors per request. Learn more

Email endpoints – depth and search URL parameter changes

The Application API Email endpoints have been updated so that minimal depth will now return the subject property (the email's subject line). Additionally, using the search URL parameter with name when retrieving a list of emails, will return matches for name and subject. Learn more

Retrieve a list of emails – New supported terms with search URL parameter

We've added new supported terms with the search URL parameter for the Retrieve a list of emails endpoint. updatedByUserId to filter emails by the user ID who last updated the email asset. createdByUserId to filter emails by the user ID who created the email asset. contentSource to filter emails by content source by specifying content source by ID: editor=0, upload=1, and responsive=3. See the tutorial for more information about searching.

Bulk API

New Campaign Response Activity Fields

We've added two new activity fields related to campaign responses:

{{Activity.CampaignResponse.CreatedAt}} - The date and time the campaign response was created.

{{Activity.CampaignResponse.Field(MemberStatus)}} - The status of the campaign member.

These new fields enable retrieving campaign response fields with exported activities to analyze campaign response data. These activity fields are available for the Email Open, Email Clickthrough, Email Send, Page View, and Form Submit activity types.

Recent changes

Oracle modified its supported cipher suites used for Transport Layer Security (TLS) connections to Eloqua. This includes programmatic access to Eloqua via APIs. Learn more.

Application API

All API endpoints for emails and landing pages no longer allow creating and editing classic emails and landing pages. When attempting to create or edit a classic email or landing page, the following error will be returned:

'410 htmlContent type of StructuredHtmlContent (Classic editor) is no longer supported.'

For more information about the classic editor sunset, see the Email and Landing Page product notice.

Bulk API

• We've modified how Contacts are linked to Bulk API form submit activities, by setting the Contact that is mapped to the Visitor (if there is a Visitor record, linked to the form submit activity). For more information, see the product notice.

• Resolved an issue where a Bulk API sync action to globally subscribe a contact was resulting in the contact not appearing in Eloqua's Segment's UI when filtered by date criteria.

Platform notices

We have revised the dates of the sunsetting of some functionality of our Classic Form Design Editor. While originally we had communicated you would no longer be able to edit or create new forms with the Classic editor as of 19C (August 2019), we have adjusted the date to our 20A release (February 2020). Please review the updated Product Notice for further information and additional schedule changes.

Additional information

For additional information and examples, refer to the Oracle Eloqua Developer Changelog.

To learn more about recent and upcoming Oracle Eloqua release rollouts, including rollout dates, user-facing features, and product notices, visit the Oracle Eloqua Release Center.