During onboarding we'll ask you to set up a number of DNS records in order for your sending domain and tracking to work. 

A DNS record is a database record used to map a URL to an IP address.

Required

DKIM

DKIM is an industry required authentication standard. This is set up via a TXT record for your sending domain. 

Ometria provides the DKIM record to be created. 

Once this has been published the record will be verified by Ometria - until this is complete you can't use the sending domain.

CNAME for tracking domain

This CNAME enables your tracking to work. Ometria provides a unique tracking domain in the format: clickom.domain.com 

This requires a CNAME record to be published which is provided by Ometria.  

CNAME for Return Path domain

This CNAME enables Ometria to receive bounce and complaint information from mailbox providers for your campaigns. 

Ometria provides a unique tracking domain in the format: emailom.domain.com 

This requires a CNAME record to be published which is provided by Ometria.  This record also provides SPF authentication for the domain. 

A record

An A record connects your domain to the IP address of your website. 

We recommend that you create an A record for your exact sending domain which links to your website IP(s). 

Many mailbox providers and filtering companies will check for A records on sending domains and may block mail where none are found. 

A records are used for IPv4 addresses - if your hosting uses IPv6 addresses you will need an AAAA record. 

MX record

An MX record specifies which mail server is able to accept mail for that domain.

It's best practice to setup an MX record for your sending domain, even when the domain won't be used to receive mail.

Just like A records, mailbox providers check for MX records and could reject mail where the record is not found.

DMARC

Your chosen sending domain must be covered by DMARC.

DMARC (domain-based message authentication, reporting and conformance) is an email authentication protocol designed to help email domain owners protect their domain from 'spoofing', or unauthorised use - e.g. a sender using your domain to send unauthorised email for phishing and other purposes.

See: DMARC guide

Highly recommended

Postmaster/abuse@ addresses

It is industry best practice to have working postmaster@ and abuse@ addresses for both your sending domain and return path domain. 

These should go to a monitored inbox so that you can respond to any incoming messages.