If you send from multiple sending domains, but you send the same campaigns from all, you may want to see each campaign as a single test in Inbox Placement (rather than a test for each domain). To do this, combine them into a single campaign in Everest, using the Everest universal header to replace your usual X-header or body comment. Learn more about X-headers.
How it works
Using the universal header does not require additional configuration in Everest. Instead, you will update your X-header or body comment, either with your ESP or in your email campaign template, to use the universal header.
You will configure a unique header code for each deployment you want to come in as a single campaign in Everest.
- Use the same code on that campaign, no matter what domain it comes in from.
- But use that code only for that campaign.
- Everest will see the header code across domains and treat them all as one campaign in Inbox Placement, reporting the results under one test.
- You'll do the same process for each campaign you want to combine from multiple domains. Make sure the code is different from one campaign to the next.
Because Everest looks for the universal header before searching for ESP-specific X-headers or body comments, it will use the campaign ID from that header even if your ESP automatically generates a unique X-header for each deployment. In effect, the universal header overrides all other X-headers and body comments.
Note: Inbox Placement will only run the Diagnostics feature on the first email seen. In other words, your campaign will be attributed to the domain we see first in the deployment, and we will run the standard diagnostic checks for reputation, authentication, and best practices on that domain.
Format
- X-header: X-250ok-CID: 250ok-UID-en_______________
- Body comment: <!-- x-250ok-CID: 250ok-UID-en_______________ -->
The universal header will work either in the email headers or in the body. Using both is not necessary.
- The header MUST contain the Everest account name as the first part of the header. For example:
- Parent account name: account_name_inc
- UK child account name: account_name_uk
- No spaces are allowed. Please use underscores.
Example
Let's say we have an Everest account called Acme Inc.
Acme sends from 2 sending domains: acmetools.com and acmesupplies.com. However, both domains send out the same campaigns, and Acme wants to use the universal header.
In this case, their header would look something like this:
X-250ok-CID: 250ok-UID-en_acme_inc_070620220940
or
X-250ok-CID: 250ok-UID-en_acme_inc_4thofjulysale_070620220940
The most important part of this is X-250ok-CID: 250ok-UID-en_acme_inc. The header part (X-250ok-CID: 250ok-UID-en) tells our system that this is the universal header and it should ignore the domains. The company name (_acme_inc) tells us which account sent the test.
Everything after this initial required code (070620220940 or 4thofjulysale_070620220940) is customizable, and that is what tells us what campaign these emails are related to. It should be a unique value per campaign, as in one code for campaign X and a different code for campaign Y.
- If you have someone knowledgeable in HTML, you may want to autogenerate the header with the date, campaign ID, or some other campaign-specific code so you don't have to do it manually.
Going back to our example, Acme would put the header X-250ok-CID: 250ok-UID-en_acme_inc_070620220940 in the campaign emails from acmetools.com and in the campaign emails from acmesupplies.com, because they want both emails to be considered the same campaign for Inbox Placement results.
Let's say Acme Inc. has two child accounts (Acme Europe and Acme Canada) that are experiencing the same problem. They can use the universal header with campaigns sent from the child account domains as well. Acme would just update the universal header to include the child account name instead of the parent account name, like this: X-250ok-CID: 250ok-UID-en_Acme_Europe_070620220940.
