Welcome to the tutorial

How to implement Google & Yahoo’s email sender requirements in 2024.

Follow the steps in the easy to follow video tutorial below, to prepare your Klaviyo account for Google and Yahoo’s new email sender requirements in 2024.

In this video tutorial you will be shown how to setup your branded sending domain in your Klaviyo account, configure your DMARC policy and add the DNS Records in root domain via your Web Host provider (eg. Siteground, GoDaddy).

Let’s get started!


Setup a Branded Domain

Branded sending domains (also known as dedicated sending domains) give you better control over your sender reputation. They also improve your branding in the “from” address in the inbox by removing the sent “via klaviyomail.com” disclaimer. Branded sending domains are a great deliverability best practice, and are a requirement for bulk senders who regularly email Google and Yahoo recipients starting in February.

Just note that once your branded sending domain is enabled, you need to gently warm your sending infrastructure for the next 2 – 4 weeks.

Never batch and blast your entire list, I will continue to shout from the segmentation best practices mountain top as long as I have to! You want to start by sending emails to your 30-day Engaged Segment only. Then if all looks okay with your metrics, you can send campaigns to your 60-day Engaged Segment, then your 90-day Engaged Segment.

New sender requirements should not bury your email program. If you email the people that want to be emailed (okay, there’s more technical structure to that) and stop emailing those that don’t, these changes will be (gasp) a GOOD THING!

Configure your DMARC policy

DMARC authentication is a protocol policy that servers use to make sure emails are coming from a legitimate sender. Brands use DMARC policies to protect the domain in their sender email address from unauthorized use by bad actors.

DMARC authentication is set up in your DNS provider (like Siteground, GoDaddy or Cloudflare). If you do not already have a DMARC policy in place, configure a DMARC policy* on your root domain that contains the following:

v=DMARC1; p=none;

Recommended but not required: rua=mailto:dmarc-reports@yourbrand.com (You’ll also need to set up a dedicated reports@ email to receive DMARC status reports).

If you already have a DMARC policy in place, you do not need to make any changes to your p tag value. Just make sure you have an rua tag set up with a valid email address included in your policy. You also only need to configure DMARC on your root domain, you do not need to add an additional policy to any subdomains used for sending.

About DMARC reports

DMARC reports allow you to monitor the email messages sent using your domain, which can help protect you against spoofing and phishing. The rua tag tells inbox providers which email address to send DMARC status reports to.

While you don’t need to actively monitor this inbox right away, it is a best practice to have a dedicated email inbox where you collect DMARC reports so your security or compliance team can easily review them when necessary.

Currently, it is not a requirement from Gmail or Yahoo that senders must have an rua tag in their DMARC policy. But, setting this up now will help future-proof your policy since inbox providers will continue to tighten sender requirements over time.

Other Helpful Links:

Explore third-party tools that can help you update and manage your DMARC policy

Still have questions?