The custom domain option is only with the Pro or Multi-account monthly billing plans and with the Pay As You Go plan.

Custom domains and DKIM sender domain verification are both domain related settings but they are not related: Custom domains are for branding, DKIM sender domain verification is for inbox delivery. However, since setup for both needs to be completed by your IT team it's recommended they are configured at the same time.

Using a custom domain helps with branding. It's an optional setting.

When you setup a custom domain references to all Envoke branded domains will be replaced with your own domain:

This helps brand recognition for contacts and can even reduce unsubscribe rates.


Example:

Here's how the email preference manager page URL appears without a custom domain:

The same page with custom domain enabled:

Check your current custom domain

You can check if a custom domain is currently enabled for your account from the Custom Domain section of the Account Settings page.

Configuring a custom domain

Choose a custom domain then ask your IT team to configure it. Let us know once this is done, we'll then issue an SSL certificate for your custom domain and enable it for your account.

You can use any subdomain of your primary domain: custom.yourdomain.com. For example communications.acme.com

Example request to your IT team:

We're using Envoke.com to send bulk email and want to use a custom domain as a display domain that our contacts see when they hover over links in emails and view the email preferences page.

Please add a CNAME entry to the DNS of our domain: [company.com]
Point [communications.company.com] to nvk.envoke.com

Verity setup by going to [custom.yourdomain.com]/form/8795/if/

The page will show "It works!" if setup is done correctly. Here's an example of a working setup: demo.envoke.com/form/8795/if/

 

 

Did this answer your question?