Oracle Eloqua limitations

Information about various aspects that you should take into consideration when working with the connector for Oracle Eloqua.

General considerations

The overall performance of the connector at the navigation level depends on the number of assets an instance has and may vary based on the asset branch you are navigating – emails, landing pages, forms, email templates, or landing page templates. This is because the endpoints that the connector uses to retrieve and display folders and assets (Retrieve a list of emails, Retrieve a list of landing pages, Retrieve a list of forms, etc.) do not support filtering by parent folder ID (called folderId in the Oracle Eloqua REST API). For example, the connector first has to retrieve all the emails in a list (using the Retrieve a list of emails endpoint) and only then filters the results by the appropriate parent folder ID to show you the right files at the right navigation level.

Certain API requests may sometimes lead to a timeout error. The reason for this is unknown; it could be related to the Rate Limit of the REST API, to the quantity of data retrieved and processed in a short amount of time (saturation), or perhaps to other instance-related causes.

Emails

The Oracle Eloqua Create an email REST API endpoint does not support emails of the ResponsiveHtmlContent type (namely, emails created with the Design Editor). This endpoint only supports emails created with the Source Editor (HTML emails); thus, the connector only supports this type of emails. In Oracle Eloqua, ResponsiveHtmlContent emails have the Design type.A screen shot which highlights an unsupported, Design-type email.

To avoid any potential issues during the upload process, make sure you follow the guidelines of how an HTML email should be created. Also, Oracle Eloqua does not support malformed HTML for emails. If a newly translated email contains malformed HTML, the upload process will be unsuccessful (filter issue).

Landing pages

The Oracle Eloqua Create a landing page REST API endpoint does not support landing pages of the ResponsiveHtmlContent type (namely, landing pages created with the Design Editor). This endpoint only supports landing pages created with the Source Editor (HTML landing pages); thus, the connector only supports this type of landing pages. In Oracle Eloqua, ResponsiveHtmlContent landing pages have the Design type.A screen shot which highlights an unsupported, Design-type landing page.

To avoid any potential issues during the upload process, make sure you follow the guidelines of how an HTML landing page should be created. Also, Oracle Eloqua does not support malformed HTML for landing pages. If a newly translated landing page contains malformed HTML, the upload process will be unsuccessful (filter issue).

Forms

The name of a form field (label) must have a maximum of 100 characters. If this condition is not met, the upload process will be unsuccessful.A screen shot which highlights two labels with more than 100 characters.

Email header and email footers

Only available upon customer request.