Email channel configurations

The Administration/Configurations/Channels tab in Meiro Business Explorer enables businesses to configure channels for running campaigns. This guide provides a step-by-step tutorial on configuring the Email channel in Meiro Business Explorer.

Prerequisites for Emails
To work with emails, ensure that the following prerequisites are met:

Configure the Email channel in the Administration/Configurations/Channel tab.
Activate the emails endpoint in the Meiro Events (ME) system to collect email events such as email openings, link clicks, and unsubscribes.
Meiro Events API connection must be set in the Administration/Configurations/Settings tab.
Channels/Emails tabs must be enabled by the administrator for your user role.
Profile stitching rules for all newly created events must be set by the analyst.

SMTP account settings

SMTP is the standard protocol used for sending email messages over the Internet. To enable email delivery, you need to specify the SMTP account settings. The SMTP account information, including the server name, port, and credentials, can typically be obtained from the email service provider.

Server name	the address of the SMTP server that will be used to send email messages.
Port number	he specific port on which the SMTP server listens for incoming connections. The most commonly used port for SMTP is port 587, but other options are available, such as port 465 or port 25.
Username and password	the login credentials required to authenticate with the SMTP server. These are typically the same as the credentials used to access the email account that you're using to send email.

Remember: different email service providers may have slightly different processes for obtaining this information, so it's best to consult the documentation for the specific email service provider being used, e.g., on Gmail, Microsoft Outlook, Zoho Mail.

By default, the connection type is STARTTLS, which means that the CDP uses this protocol to encrypt the connection. STARTTLS is a security protocol used to encrypt the connection between the CDP and the SMTP server. This helps to ensure the privacy and security of the email messages being sent.

Configuration of email stitching category

At the next stage, you need to select the stitching category related to emails, keep in mind it cannot be changed later on. If there is no suitable stitching category yet, proceed with creating it first through the 'add stitching category' button.

Available SMTP Integrations

This section presents a selection of SMTP providers suitable for email communication, including Mailjet, MessageBird, Brevo, MailerSend, Infobip, Mailgun, SendGrid, and Omnivery.

Verified Senders

In the "Verified Senders" section, you need to configure the email addresses that will be available for use as sender and reply addresses in your email campaigns. When creating an email, you can select from a list of email addresses you have previously verified in the configuration section. If you have marked a default email address, it will automatically fill in the email creation form.

To add a new email address to your list of verified senders, fill in the email address in the designated field and click the 'add address' button. Every email address you add must be verified by following a link sent to that email address.

Remember: you can remove an email address from the list of verified senders if it is not currently being used in any email campaign. Additionally, at least one email address must be configured in the "Verified Senders" section.

Setting Stitching Rule

To enable the inclusion of email events in the profile identity graph, the analyst must establish a stitching rule for the Meiro Email Message ID attribute and associate all pertinent email events with it.

Enabling emails bounce rate

Email bounces are typically obtained by email service providers and can be accessed via their REST API. In order to collect email bounce rates, it is necessary to establish a MI workspace that can extract the bounce information from the email service provider. ~~Once the workspace is set up, the customer events can be constructed based on the extracted email bounces data.~~

The payload should include the unique message ID and email address as mandatory fields, while other optional fields like campaign ID, bounce type, reason, and subject can also be included. The message ID serves as a unique identifier for each email message and is generated on our end before sending out the email. The example of payload:

{
  "id": "7ac8ba56-9d43-4a9e-8057-1b3e73890e80",
  "email": "example@meiro.io",
  "campaign": {
    "id": "7dac66f2-0300-495b-bb4e-72d7fa883f81",
    "name": "Abandoned Basket"
  },
  "bounce_type": "soft_bounce",
  "reason": "spam",
  "subject": "You forgot to park your shopping cart",
  "utm_parameters": {
    "campaign": "abandoned_basket",
    "content": "",
    "medium": "email",
    "source": "",
    "term": ""
  }
}

~~After constructing the customer events, they should be sent to CDP via the~~e events loader. This ensures that the email bounce data is properly captured and available for analysis.