Skip to main content
Sending Settings

A guide to your account sending settings.

Support Team avatar
Written by Support Team
Updated over a month ago

The settings screen lets you configure a wide range of features for your account. The Sending section covers many features related to your email delivery, like Tracking and Pruning.

Tracking

Track Opens

Your email opens are tracked by displaying a tracking pixel. This pixel is an image, so that is why the tracking mechanism will work only if an email client is correctly displaying images. As soon as an email is opened, the tracking pixel is displayed which in turn causes our system to register such event.

This is also the reason why plain text email opens cannot be tracked.

Track Clicks

When you insert a link you would like to track into your email, we rewrite it. Then every time someone clicks/opens/reacts to it, you will receive information about this event.
This way you can measure the engagement levels when you send mail to your users.

Track Clicks By Link

Although at first glance it looks similar to the previous description, it is a slightly different thing.

When you turn on this setting, we will be able to send you detailed reports on all kinds of reactions associated with the links that you put in your emails.

We will send you information about which link was clicked, how many times it has been clicked, by whom and we will also show you the date of the last interaction.

If you use the List-Unsubscribe Including a List-Unsubscribe header in your emails, it will help reduce complaints.

Return Bounces

This option allows you to receive non-delivery reports to the email address that you set up. What does it really mean?

If an email is not delivered (this can happen for various reasons), information about these non-deliveries will be sent to the address you have specified.

However, if you turn this option on but you do not enter an email address, all of the non-delivery reports will be forwarded to your account's default email address.

Tracking and pruning - Contact pruning

When Contact Pruning is enabled, contacts are automatically blocked after a specified number of emails are sent (and not opened) or within the specified time frame.

The Contact Pruning Tutorial has more information.

Advanced

This option will cause contacts to be stored when an email is submitted to the API. Storing the contacts builds your contact list, provides more metrics and gives access to the delivery optimization engine. Turn this option off if you prefer to maintain this information exclusively on your own systems.

Delivery optimization engine

Analyze delivery across our entire platform to help improve your email delivery. Personal data is limited to your contact's email address.

Custom headers

This setting is intended primarily for users who use SMTP API and HTTP API.

When you turn this setting on, you can add additional headers (to send and receive additional data) that are not set by default by us.

These kinds of headers are mainly used in integrations with other programs or scripts.

If you are interested in more information about custom headers, feel free to check out this article.

Auto-create text body

When enabled, Elastic Email will transform your HTML message into a plain text message, which is based on the content of your email, we will be able to deliver your mail properly also for users who do not support emails in HTML format.

We often recommend that you activate this setting if you are getting spam check results that include this error:

"Spam: Body: Message only has text/HTML MIME parts"

So consider this setting carefully as it may be of use to improve your delivery.

Template Scripting

When this is enabled, you can execute Javascript within double merge tags {{ }} in templates. There are more examples in the Template Scripting Tutorial.

Content transfer encoding type

As you probably know, the content you create (text, images, everything) is properly encoded, and then sent to the recipient.

We recommend Base64 due to the fact that most of the servers operate on this coding. However, it is worth remembering that in some cases, servers may prefer a different type of encoding content and in those cases, you have to set the appropriate type.

Supported Encoding Types:

None

Raw7Bit

Raw8Bit

Quoted-Printable

Base64

Uue

User Provided (whatever encoding you send us, we will preserve).

BCC email address(es)

Receive a copy of an email you send to a non-default email address. Every mail transaction you send will be also sent to those addresses. Addresses must be separated with a semi-colon β€œ;”.

Did this answer your question?