There can be various reasons why your X-header did not appear in your campaigns in Everest after attempting to implement an X-header (or equivalent HTML tag in the body of the email).
Common scenarios
- The reference seeds show that no X-header is present.
- The X-header is incorrect due to a typo or similar issue.
- The X-header has an incorrect format.
- You have changed to a new ESP or MTA and need to set up an X-header again.
Troubleshooting
1. Refer to Everest Inbox Placement tests to view the X-header. Your X-header may only be missing for specific mail streams or IP addresses. It is also possible that the problem started on a specific date and could be related to a recent change (e.g. new IP, new email template, new mail stream).
- Login to Everest
- Click In-Flight > Inbox Placement
- Click Inbox Tests
- Locate the Inbox Tests section and view the X-Header column
- Click Customize Table and select the X-Header column within Display Preferences if the X-Header column is not visible
2. Determine whether an X-header is present in the message headers.
- Login to Everest
- Click In-Flight > Inbox Placement
- Click Inbox Tests
- Click a subject line for a completed test
- Click on the details arrow on the far right side for any mailbox provider
- Click on the details arrow on the far right side under the Headers column for any seed with Inbox or Spam placement. You cannot view headers for Missing seeds.
Everest automatically looks for IDs with these formats. If you see one of these X-headers in the message headers and it is not visible within the X-Header column in Inbox Tests, contact Validity Support.
- X-250ok-CID
- X-rpcampaign
- rpcampaign
- X-PVIQ
- X-Campaign-ID
- X-CampaignID
- x-job
If you see any of these X-headers below in the message headers and it is not visible within the X-Header column in Inbox Tests, contact Validity Support to let them know which format is used.
- Tag-id
- X-10pl8ID
- X-Campaign
- X-Campaign_ID
- x-cid
- X-eC-messenger-mid
- X-EMarSys-Identify
- x-jobid
- X-Listid
- X-MailingID
- X-NSS
3. If an X-header is not present in the message headers, check the body of the email next. Some ESPs cannot or do not make changes to the email headers and the ID may have been entered into the email body. Look in your HTML code for each email template for an ID similar to this example. The X-header may resemble any of those mentioned above in step 2.
- <!-- X-250ok-CID: uniqueid1234567890 -->
4. If an X-header is not found in the message headers or the body, you need to set one up.
5. If an X-header is present, ensure it is implemented correctly. The X-header must be set up with the correct syntax and format for Everest to recognize it.
- Is the X-header written correctly?
- Is the correct format applied?
If these steps do not fix your issue, please contact Validity Support.
