Resources · Menu · Free, no email · Updated

EMAIL PLATFORM: BEYOND SEND THE CAMPAIGN

If the only lever you pull is send more, performance keeps slipping. Work through what your platform is for besides the send button, read the signals honestly, and leave knowing which fixes are yours and which belong to whoever owns the domain.

How it works

  1. Say why you are here.
  2. Name your platform if you know it. It only changes a note or two.
  3. Mark each capability: using it, heard of it, or not using it.
  4. Do the marketing-owned actions first. Escalate only what the signals say to escalate.

Diagnose beyond the send button

Why are you here?

Used for a light note only. This is not a vendor audit.

Anything you have actually seen

Only tick what you have observed in the reporting.

Nothing you enter here leaves your browser. Close the page and it is gone.

Your capability menu and the month actions will appear here.

Do the marketing-owned actions first. If the signals point at authentication, the email authentication guide explains what to hand your IT team, and this page deliberately stops short of DNS records.

An orientation aid. Vendor capabilities differ by tier and none of this is legal advice on consent. Nothing you enter is sent anywhere or stored.

Goes well with

GuideFree
Email authentication in plain English

SPF, DKIM and DMARC, explained for people who run a business, not a mail server.

Get the guide

If you would rather have this done with you than to you, this is the work I do. See services

Most dips are hygiene, not creative

An open rate falling on an unchanged list is usually decay. The instinct is to redesign the template, which is the most visible response and rarely the cause. Suppression, sunset rules and a working preference centre move the number more reliably than a new header image, and they cost less. The signals in this tool exist to stop the expensive redesign happening before the cheap fix has been tried.

Know when to stop and escalate

A complaint spike hitting several mailbox providers at once is not a content problem and it is not yours to fix from a marketing seat. This page tells you when that line has been crossed and then stops: DNS records are not configured from a web page. What to hand your IT team is in the email authentication guide.

COMMON QUESTIONS

Is this a deliverability engineering guide?

No. It tells you when to escalate. It does not configure SPF, DKIM or DMARC, and it deliberately does not offer DNS instructions.

Will it connect to my email platform?

No. You mark each capability yourself and nothing is stored.

Does it work if I am not sure which platform we use?

Yes. The platform field only changes a note or two. The capabilities and the signals are the same across the major platforms.

What if everything is marked as in use?

Then the actions go deeper rather than wider: send yourself through your own welcome journey, find your complaint rate, and count how many emails one person could receive in a week.