For many companies, who the message is sent from is just as important as what the message says - which means it is important to have a custom sending domain. A custom sending domain refers to the part of your email that comes after the "@". For example,

In order for BuyerGenomcis to send email on the behalf of your custom sending domain, you or your IT team will need to make adjustments to your Domain Name System (DNS) configuration. These are routine, straightforward updates that IT teams can easily make.

This guide outlines the requirements necessary for your BuyerGenomics set-up, and presents the optional components you or your team may want to implement for your domain.


Your Domain Name System tells internet users and services how to connect to your brand. Much like how your contact list contains information on how to contact individuals, your DNS instructs browsers, email services, and users how to receive and load your website, online store, or emails. 

Updating your DNS records - or the rules in your DNS Configuration that tell how people can connect to/receive your services - allows you to send email from your Brand domain from within BuyerGenomcis.

Required Configurations

There are three components that will be affected by the records in this section: 

  • From Domain (the domain that your emails will come from - e.g.,
  • Web Domain (the domain that will host your email preferences/unsubscribe pages)
  • Tracking Domain (the domain that is used for your Universal Touch System implementation)

To successfully implement these components, your DNS configuration will need the following records:

NameRecord TypeTTLValue
TXT300DKIM records

The substitutions for the all-caps name fields, as well as the values, for each of these records will be provided for you.

Note: Your web domain must not currently exist. When you receive your DNS Configuration instructions, make sure that the web domain does not exist prior to implementation.

Recommended Configurations

While the configurations in this section are not required, they are highly recommended. They are important for email deliverability, domain verification, and reporting - among other reasons.

The two components are: 

  • Google Site Verification

These components require the following records: 

Record Type
DMARC parameters
Google Verification Code

Like above, we will provide you with the all-caps name fields and value substitutions. 

Note: By default, if you do not already have a DMARC record, we will give you a DMARC record with a policy of "none". When you decide to change your policy to "quarantine" or "reject", we strongly recommend you verify any other email systems you may use to ensure their SPF and DKIM records are set up properly, and that you know the differences between DMARC policies.