How to configure the SMTP server in Resonance CDP Email Settings?

Introduction #

Resonance included a marketing automation platform that helps users with high-level integration with their audience which involves personalization of emails, creating landing pages, creating workflows for improving customer experiences, and also has the ability to track audience marketing activities.

It has a built-in CRM and also has the ability to sync third-party CRM’s leads such as Salesforce, HubSpot or any other of your choice. You can also design workflow according to the leads generated at a certain score threshold and perform the activity of filling the form or sending an email with the link.

Prerequisites #

  1. A working Resonance CDP setup. For any user in Resonance has their own Resonance CDP for Marketing Automation. Your user and password for access to Resonance CDP is equal to access to de app.
  2. An SMTP service provider like Mailchimp, Amazon SES, Pepipost, etc

Step 2: SMTP configuration #

Resonance CDP already has a list of SMTP service providers which you can use by default by just adding their SMTP username and password.

d. The above configuration finalizes your domain for sending an email, you can see the below page once your domain is ready to send an email.

For Resonance CDP configuration, Switch to the setting tab (click on the extreme right corner after your profile name) -> click for configuration -> Select Email settings.

Set your credentials has below:

Service to send mail through: Other SMTP servers
Post: 587 (highly recommended way of sending an email)
SMTP encryption type: TLS (encrypted way of passing email from server to server)
SMTP authentication mode: Login
Username for the selected mail service: your SMTP username
Password for the selected mail service: your secret SMTP password.

Once you are done with the setting just test your connection by clicking the Test connection button.

The above configuration will allow you to send emails through SMTP Server using Resonance.

Segment (Broadcast) Emails #

These are marketing emails by default. Segments are assigned to the email which will determine which contacts receive the communication. Note that each contact can only receive the email once – it’s like a mailing list.

Initiating these emails can be done in one of two ways. Prior 2.2.0, sending had to be manually initiated through the UI as an ajax process batched over the contacts. As of 2.2.0, a new cron job is available to do this for you! See Send Scheduled Broadcasts (e.g. segment emails) for more details.

Email Formats #

Emails can be created in both full HTML as well as basic text format to be delivered as necessary to contacts. This is an important part of creating a strong relationship with contacts by providing relevant information in the correct format.

Email Delivery #

Emails are delivered using the method defined by the system administrator. If you are the system administrator for your company, then you will need to add the email protocol for your company to use. Resonance integrates with any email service provider which offers SMTP mail servers as well as several distinct services such as MandrillGmailSendgridMailjetPostmarkSendmail and Amazon SES.

The system can either send emails immediately or queue them to be processed in batches by a cron job.

Immediate Delivery #

This is the default means of delivery. Resonance sends the email as soon as it is instructed by the triggering action. If you expect a large number of emails to be sent, then utilizing the queue is recommended. Sending email immediately may slow the response time of Resonance if using a remote mail service since Resonance has to establish a connection with that service before sending the mail. Also attempting to send large batches of emails at once may hit your server’s PHP limits or email limits if on a shared host.

Queued Delivery #

This is recommended if you plan to send a significant number of emails. Resonance will store the email in the configured spool directory until the command to process the queue is executed. Set up a cron job at the desired interval to run the command:

php /path/to/mautic/bin/console mautic:email:process --env=prod

Some hosts may have limits on the number of emails that can be sent during a specified timeframe and/or limit the execution time of a script. If that’s the case for you, or if you just want to moderate batch processing, you can configure batch numbers and time limits in Resonance’s Configuration.

Email Fields #

You have access to any number of contact fields to be used in your form emails. These can be easily placed within your emails and will be automatically replaced with the appropriate text once the email is sent.

Tracking Opened Emails #

Each email sent through Resonance is tagged with a tracking pixel image. This allows Resonance to track when a contact opens the email and execute actions accordingly. Note that this technology is limited to the contact’s email client supporting HTML and auto-loading of images. If the email client does not load the image, there is no way for Resonance to know if the email was opened.

By default, the tracking pixel image is added at the end of the message, just before the </body> tag. If needed, one could use the {tracking_pixel} within-the-body content token to have it placed elsewhere.

Clicks of each link in an email are tracked and those clicks count can be found at the bottom of email detail page under Click Counts tab.

Unsubscribing #

Resonance has a built in means of allowing a contact to unsubscribe from email communication. If using the builder, simply drag and drop the Unsubscribe Text or Unsubscribe URL tokens into your email. Or insert {unsubscribe_text} or {unsubscribe_url} into your custom HTML. The unsubscribe text token will insert a sentence with a link instructing the contact to click to unsubscribe. The unsubscribe URL token will simply insert the URL into your custom written instructions.

Online version #

Resonance manages also the hosting of an online version of the email sent. To use that feature, simply add the following as URL on text to generate the online version link {webview_url}.

Shopping Cart
Supportscreen tag