Configuring Engage
Manage how your users can use Engage by configuring the Engage app.
Before you begin:
-
You must be a customer administrator to configuration the Engage app.
-
Some Engage settings do not apply to Sales Tools for Microsoft Outlook sends. See
To configure Engage:
- Log in to Oracle Eloqua.
- Click Settings
. - Click Apps in the Platform Extensions section.
- Select the Engage app.
- Click Configure
.Warning: Selecting the Reinstall option
for an app will force you to go through the entire installation process again. The app will be unavailable for all users during the reinstall. - Configure the settings as needed. Learn more.
- Click Save to save your settings.
Your configuration settings have been updated. You can modify them at any time.
Settings
Recipients
- Restrict the maximum number of recipients to: Specify the maximum number of recipients a single email can be sent to. The highest number you can enter for this field is 2,000.
- Enable recipient autocompletion: When enabled, Engage searches your Oracle Eloqua contacts as their names are entered in the recipient list in an email. This option is disabled by default.
- Enable contact send limit: Limit the number of sales emails that your reps can send to the same contact over a period of time. 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.
Tip: Send limits apply to both Engage and Oracle Eloqua Sales Tools for Microsoft Outlook. and apply to all sales users.
Email Settings
In the Email Settings section, you can standardize the sender display name and from address of all emails sent from Engage.
By default, Engage sends emails using the user’s first name, last name, and email address. Using the Email Settings, you can change these defaults and have all Engage emails sent with the same sender display name and from address.
Consider using these settings if you want to help the sales team with their email branding, and help your sender reputation. A best practice for a strong sender reputation is matching the from address to the return path. These settings allow you to do this.
The reply-to address for Engage emails is always the email address of the Engage user. For example, when John Smith sends an Engage email, John's email address is used when a contact replies to the email.
Note: These settings should match the values configured within the Email Defaults settings page. Only change these settings if you have access to these settings.
- Customize how emails are sent from Engage: Check this box to customize two fields: Sender display name and From address.
- Sender display name: All emails sent from Engage will display this sender name to recipients. For example, if you enter the value Company Name, recipients will see Company Name for the sender name when John Smith sends an Engage email. If you leave this value blank, Engage will continue to use the user’s information (for example, John Smith).
- From address: All emails sent from Engage will display this from address to recipients. For example, if you enter the value products@companyname.example.com, recipients will see products@companyname.example.com for the from address when John Smith sends an email.
Email Creation
- Allow use of blank templates: When enabled, Engage users can send a non-templated blank email. When disabled, Engage users can only use Engage templates created for them. This option is enabled by default. Review the considerations when enabling this feature.
- Allow creation of shared templates: When enabled, Engage users with appropriate permissions can save Engage emails and make them accessible to other users. This option is enabled by default. All users are able to save Engage emails for private use.
Content
- Allow images: When enabled, Engage users can insert images in emails. Images are stored in the Oracle Eloqua image library and require appropriate asset permissions. This option is enabled by default. Learn more about inserting images.
- Allow attachments: When enabled, Engage users can insert attachments in emails. Attachments are stored in Oracle Eloqua's File Storage library and require appropriate asset permissions. This option is enabled by default. Learn more about inserting attachments.
- Enable field merges: When enabled, Engage users can insert field merges in emails. Field merges are stored in Eloqua's File Storage library and require appropriate asset permissions. This option is enabled by default. Learn more about inserting field merges.
Text Formatting
- Enable font colors and font highlighting: When enabled, Engage users can modify the font color and highlight selected text. This option is enabled by default.
- Enable font and font size selection: When enabled, Engage users can modify the style and size of their text. This option is enabled by default.
Template Sorting
- Recently Modified (the default): When enabled, templates are sorted on the All and My tabs of Engage's Select a Template window according to the date when they were modified. Users can alternatively click the refine icon
and select Alphabetical. - Alphabetical: When enabled, templates are sorted alphabetically on the All and My tabs of the Select a Template window. Users can alternatively click the refine icon and select Recently Modified.
Allowed Domains
Identify which domains are allowed to host Sales Tools pages. For example, if you embed Sales Tools in an iframe hosted by your CRM, add the domain of the page hosting the iframe to your allowlist. You can allow a domain and its sub-domains using a wildcard (*). Learn more about Engage integration.
To avoid broken iframes, add your CRMs to the
- Salesforce: *.force.com, *.salesforce.com, *.my.salesforce.com, *.lightning.force.com, and *.visualforce.com
- Oracle CX Sales: *.oraclecloud.com
- Oracle CRM On Demand: *.crmondemand.com
- Microsoft Dynamics: *.dynamics.com
To learn more about embedding Engage in different CRMs, see Engage integration.
Considerations when allowing blank emails
You can enable your sales reps to create blank emails. Blank emails are non-templated emails. Here are some considerations to take into account about allowing blank emails:
-
Blank emails are not associated to an email group. So recipients cannot unsubscribe from these types of emails sent by your sales users.
-
Blank emails will not contain any headers or footers. So this means that unsubscribe links are not included in these emails.
-
In terms of reporting on blank emails in Insight, the emails appear in reports as Tracked Emails. You cannot report on the subject line of a blank email.
Tip: If you disable this feature, you can create a blank email template for sales which would give them control over their email but allows you to ensure headers, footers, and unsubscribe links are included.