How to configure a messaging channel
In Vero Newsletters, "channels" are used to configure the connection or provider that will be used to send your messages to a given endpoint. Channels are intentionally flexible and designed to support any message type, from well-known platforms and products to custom channels.
Currently, Vero Newsletters only supports email channels (more coming soon).
Vero Newsletters comes with an email channel preconfigured so you can start sending straight away. This channel is named "Vero Mailer" and Vero automatically manages the domain and IP addresses associated with this channel.
Add a channel
Click Channels then Add next to the channel provider you want to configure. Give your new channel a name, add the required API keys (or other authorization credentials) and select Save.
Your channel is now available to select when creating a Newsletter.
Setting a default channel
When creating a new newsletter Vero will default to a specific channel. You can set the default channel by choosing Mark as Default within the Channels menu.
Important notes on specific channels
If using the preconfigured "Vero Mailer" channel, your emails will look something like this:
Email clients will show as being sent "via veromailer.com" (or similar) because the domain of the from address used to send the email (e.g.
chrishexton.com) does not match the domain of the server that sent the email (e.g.
The Custom Domain channel type enables you to send emails using your own domain, removing the mismatch and "via veromailer.com" message.
Requesting DNS records
Select Add next to the Custom Domain channel type. Name the channel and add the Domain you'd like to send from. Vero will generate the DNS records you need to add to your DNS host.
Once you've added the DNS records to your host return to Vero and select Verify domain. Vero will test to ensure your DNS records are visible. Once verified you will be able to send using your newly configured channel.
Custom subdomains for link tracking
By default Vero Newsletters will generate tracking links using the subdomain "email". For example, if you configured the domain
mydomain.com, we'd rewrite links using the subdomain
You can email our support team to request that we use a different subdomain for link tracking.
When configuring Sendgrid as an email channel Vero will add an event webhook entry in order to sync message interactions back to Vero.
Sendgrid only supports one event webhook. As a result, if you have already configured a webhook Vero will not install its webhook. In this scenario Vero will only be able to record "Sent" history in Logs and Reports.
Vero Newsletters supports Sendgrid's IP Pools. You can add a single IP Pool per Sendgrid channel configuration in Vero.
When configuring Mailgun as an email channel Vero will add an event webhook entry in order to sync message interactions back to Vero. This will be added in addition to any event webhooks you have already configured in Mailgun.
When configuring Mailjet as an email channel Vero will add an event webhook entry for each event type in order to sync message interactions back to Vero.
Mailjet only supports one event webhook per event type (e.g. "opens", "clicks", etc.) As a result, if you have already configured a webhook for a specific event type Vero will not install its own webhook for that event type. In this scenario Vero will not be able to record the history for that event type in Logs and Reports.
Mandrill (Mailchimp Transactional Email)
When configuring Mandrill as an email channel Vero will add an event webhook entry in order to sync message interactions back to Vero. This will be added in addition to any event webhooks you have already configured in Mandrill.