Transactional opt-in is an account-wide feature that affects all event-driven emails. It ensures that critical emails reach their intended recipients by overriding many of the blocks that would result from a contact previously included in blocklists (Internal, global suppression, Robinson Lists) or flagged with spam-complaint. Use this to make certain, that your business-critical transactional emails (status updates, booking confirmations, invoices) reach their target.
Contacts not found on the blocklists are not affected.
This feature can be activated for you by Emarsys Support.
Functionality
The following table shows if emails launched to contacts who have opt-in equal to EMPTY or FALSE are sent or blocked:
With the activation of the transactional opt-in feature, no additional "transactional opt-in" contact field will be created in the Emarsys contact database. Instead, the logics described in the table below will be applied.
| Condition |
Batch emails | Transactional emails when the feature is not activated | Transactional emails (general email sending infrastructure) when the feature is activated |
Triggered Emails (dedicated email sending infrastructure) when the feature is activated |
|---|---|---|---|---|
| Contact is on the internal blocklist | Email blocked |
Email blocked |
Email sent |
Email sent |
| Contact is on the global suppression blocklist | Email blocked |
Email blocked |
Email sent |
Email sent |
| Contact is on the Robinson List (DACH countries/regions)1 | Email blocked |
Email blocked |
Email sent |
Email sent |
| Contact is on the spam complaints blocklist | Email blocked |
Email blocked |
Email sent |
Email sent |
| Contact is on the account triggered blocklist | Email blocked |
Email sent |
Email blocked |
Email blocked |
The following table shows if emails launched to contacts who have opt-in equal to EMPTY or FALSE include or do not include the indicated links and feature:
| Condition |
Batch emails | Transactional emails when the feature is not activated | Transactional emails (general email sending infrastructure) when the feature is activated |
Triggered Emails (dedicated email sending infrastructure) when the feature is activated |
|---|---|---|---|---|
| System online version enabled | Link generated |
Link generated |
Link generated |
Link not generated2 |
| System unsubscribe link enabled | Link generated |
Link generated |
Link generated |
Link not generated2 |
| List-unsubscribe in email header | Always included |
Always included |
Always included |
Not included |
Notes:
1 There is a feature to ignore the Robinson List, but this must be enabled by Emarsys Support.
2 You can get around this limitation by hard-coding the links in the email template that you use to create the mail stream.
Please note that the list-unsubscribe header will not be included in transactional emails if the transactional opt-in feature is enabled.
Triggered email blocklist
The triggered email blocklist is an internal blocklist within your account. You cannot add contacts to this blocklist. To do so, please contact Emarsys Support. Please also note that your account blocklist and the triggered email blocklist are not synchronized automatically.
Information about the difference between transactional and triggered emails can be found here.