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

Even though custom domain setup and DKIM sender domain verification are both domain related settings, they are not related: Custom domains are used for branding, DKIM sender domain verification is used to ensure the best possible inbox delivery for your emails. However, since setup for both needs to be completed by your IT team it's advisable 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, all Envoke branded domains are replaced with your own domain

A custom domain helps brand recognition for contacts and can even reduce unsubscribe rates as contacts don't suspect potential scamming from a third party domain they may not recognize.


Check if a custom domain is configured

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

  1. Choose a custom domain

  2. Ask your IT team to configure it for you

  3. Let Envoke know once this is done

  4. Envoke will issue an SSL certificate for your custom domain and enable it for your account.

You can use any subdomain of your primary domain as your custom domain. For example if your primary domain is university.com then your custom domain can be anything.university.com

Sample request to send to your IT team to setup a custom domain:

We're using Envoke.com to send broadcast emails and to assist with branding we 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.

We chose the following subdomain: [communications.company.com]

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

Verify 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/

Once this is done, we will let Envoke know and they will issue an SSL certificate for this custom domain.

 

 

Did this answer your question?