Global email defaults

Email defaults are set up when your organization first purchased Oracle Eloqua. Some of these settings can be set on an email by email basis, and typically you should not have to change the default settings. For more information on individual email settings you can change, see Email settings.

Note: Many of the global email default settings are read-only. If you need to make changes, contact your Customer Success Manager or contact My Oracle Support  and create a service request.

To view global email defaults, navigate to Assets An image of the Assets icon, which is represented by a black pencil. > Email Setup > Email Defaults.

Global email default settings

  • Send to Specified Domains Only: Read-only. This is selected if there are no domains being used that are not managed by Oracle Eloqua.

  • Live Send: Read-only.

    • Edit Allowed Email Domains: Available if Send to Specified Domains Only is selected. Click to manage Allowed Email Domains.
  • Enable Tracing: Read-only. This is only enabled if a batch investigation is happening in order to trace individual batch steps. You can always check past batch emails and upcoming ones in the email batch control area. Learn more.
  • Brand Email Domains: Read-only. Depending on the Branding & Deliverability package you purchased, you may have one or more branded email sub-domains. Contact your Customer Success Manager for more information. Each sub-domain is leveraged for bounceback handling and reporting in Oracle Eloqua. These sub-domains may also be used as microsites to host Oracle Eloqua landing pages and forms. See Microsites for more information.
  • External Tracking: If you are using an external web analytics system (like Google Analytics), you can send Oracle Eloqua email tracking information to that system. You can manage the configurations by clicking Advanced Options. See Adding third-party tracking to your emails for more information.
    • Enable Domains for External Tracking: Click to configure domain settings for external tracking. When in use Oracle Eloqua will not append external tracking parameters to any domains except domains explicitly on this external tracking list. If this is enabled, you can add domains and sub-domains to the allowlist. You can use an asterisks (*) to represent sub-domains. For example, *.example.com would include the sub-domains your.example.com and my.example.com.

      Important: 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.

  • Use Approvals Workflow: Read-only. If your organization purchased the campaign approvals add-on, this indicates whether the approval workflow is required when sending emails. Some users might be able to bypass the approvals workflow. For more information, see Campaign approvals.
  • Add List-Unsubscribe header to outbound campaign emails (default): Enabling this option adds a list-unsubscribe and list-unsubscribe-post header to all outbound campaign emails.
  • Default Email Encoding Language: Shows the default encoding used for emails. Users can override this on an email by email basis using the email settings. If you are using a double-byte language in the email (such as Chinese) or may translate the content in future, this should be set to Unicode (UTF-8).
  • Default Sender Display Name: The default display name for the email sender. You can change this default and users can override this on an email by email basis using the email settings.
  • Default From Address: The default address for the sender. This must be a valid email address. For deliverability purposes, it is recommended that this email address has the same sub-domain as the bounceback address. You can change this default address and users can override this on an email by email basis using the email settings.
  • Default Reply-To Address: The default address for email replies. If you don't provide a reply-to address, replies are sent to the from address. The email address must be valid and should not use the same sub-domain as the bounceback address. You can change this default address and users can override this on an email by email basis using the email settings.
  • HTTP X-Frame-Options Header: This option is used to determine if a browser is allowed to render a page in an iframe, frame, and so on.
    • None: No restrictions. That is, a browser would allow a client's pages that has no header to be included within iframes, frames, and so on.
    • SameOrigin: Allows a client page to be displayed in iframes, frames, and so on if these have the same origin as the page.
    • Deny: Prevents client pages from being displayed in iframes, frames, and so on.
  • HTTP Referrer-Policy Header: This option is used to determine how a referrer header is implemented on landing pages. The default selection is that a referrer header is not added. A referrer header allows a server to identify referring pages that people are visiting from. This is also a security protocol for prevention of tracking, stealing information, and leaking sensitive information.
    • no-referrer: The referrer header will be omitted. Sent requests do not include any referrer information.
    • no-referrer-when-downgrade: Send the origin, path, and query string in Referrer when the protocol security level stays the same or improves (HTTP -> HTTP, HTTP -> HTTPS, HTTPS -> HTTPS). Don’t send referrer information from (HTTPS -> HTTP).
    • origin: Send only the origin in the Referrer header. The origin is the scheme (protocol), host name, and port of the URL.
    • origin-when-cross-origin: For cross origin requests (HTTPS -> HTTP), send only origin. For the same origin requests send origin, path, and query string.
    • same-origin: Send the origin, path, query string for same-origin requests. (HTTP -> HTTP) and (HTTPS -> HTTPS).
    • strict-origin: Send only origin for same-origin requests (HTTPS -> HTTPS). Don’t send the Referrer header to less secure destinations (HTTPS -> HTTP).
    • strict-origin-when-cross-origin: Send origin, path, and query string when performing a same-origin request. For cross-origin requests, send the origin only. Don’t send the Referrer header to less secure destinations (HTTPS -> HTTP).
    • unsafe-url: Send the origin, path, and query string when performing any request, regardless of security.
    • none: If no referrer policy is set, the browser’s default policy will be used. The default policy is strict-origin-when-cross-origin.
  • Store Device Metrics: Read-only and enabled by default. If enabled, Oracle Eloqua will record device metrics.
  • Intermediate Unsubscribe Page: A landing page to present to contacts after clicking an unsubscribe system action link. An intermediate unsubscribe page helps prevent email scanning tools from unsubscribing contacts unintentionally. Only after confirming the unsubscribe using the landing page will Eloqua unsubscribe the contact.

    This feature is disabled by default. To enable it, select a page. Only landing pages created using the template provided can be selected.

  • Bounceback Configuration: Read-only. The email address that captures bounceback responses.

    When an email cannot be delivered because of a hard or soft bounce, the bounce response message is sent to this address. You can use the Bounceback History with Messaging report to view the bounce details. Depending on your Branding & Deliverability package, you may have multiple bounceback addresses. The bounceback address should use the sub-domains configured above. If you have multiple bounceback address, users can override the default address on an email by email basis using the email settings.

    Learn more from this knowledge base article on how to change or set up a bounceback address.

Learn more

Emails

Email settings

Knowledge Base: How to Change or Set Up a Bounceback Address