For marketing and CRM teams
You shouldn't hear about an email problem from your recipients.
Today, for free: one of your emails is measured as it lands in an inbox, each finding with the excerpt that establishes it. With Version Pro, rolled out in stages, sentinels placed in your journeys reread every send and let you know when something changes.
Today · free
A send, read the way a recipient receives it
Forward it to the address created for you, or upload the file. It is measured on arrival, without loading a single image or following a single link, and the report can be handed as is to whoever will fix it.
- — Check that a change of template or sending platform hasn't broken anything.
- — Check that the unsubscribe link responds, and whether it's itself tracked.
- — Compare your practices with your sector's, on a named basis.
The audit report
- 01 A score per family — technical, compliance, deliverability, experience — and the detail of each criterion.
- 02 The points to fix, each with the excerpt from the message that establishes it.
- 03 The sending platform detected in the headers, and the technical block: weight, rendering, accessibility.
- 04 The message preview, with images blocked, and the report as a PDF.
Version Pro · an example
A signature that breaks
Your sending platform sees the email leave; it doesn't see what arrives. A sentinel placed in your journeys reads every send on arrival, and dates the first one whose signature no longer passes.
-
3 February
Placed in your CRM
Added as an ordinary contact, with its placement conditions: the system, the segment, the consent. We date the placement, you declare the rest.
-
5 February
First email received
The sentinel becomes active. Every email it receives is measured on arrival and kept as evidence.
-
Every send
Still monitored
Authentication, trackers, links, unsubscribe: every email is read side by side with the previous one. The series that holds becomes the baseline.
-
9 April
The DKIM signature stops passing
Held across the whole series, it fails on today's email: an authentication regression, with the header that shows it.
-
09/04 · 08:12
The alert goes out, with its evidence
The finding, why it matters, what's changed since the last mailing that held, how to check it yourself, how to fix it. One alert per change, never per mailing.
Authentication regression
- Sentinel
- mc-n02@temoin.example
- Placed
- By you, in your CRM, on 3 February
- Sender
- news.maisonclaire.example
- Subject
- Spring essentials
- Signature
- dkim=fail d=maisonclaire.example
- Held
- On every email until 2 April
- What changed
- The alert compares today's send with the last one that held: the signing domain, the selector, the header that shows the failure. Nothing to piece together.
- Where to fix it
- The sending platform is read from the headers, and the fix is given for it: where the signature is configured, and what needs to be republished.
- One alert per change
- The regression opens the event, subsequent sends are attached to it, and its return to normal closes it. Never one alert per send.
Sentinels open up with Version Pro, by batches. Request access →
Version Pro · your tests
What your sentinels test
Commitments chosen from a control plan, never written by hand: each has its own protocol, and its result is replayed from the log.
-
Authentication holds
SPF, DKIM and DMARC, read from the headers added when each send is received. An alignment that breaks is dated to the day, with the header that shows it.
Passive: no action, the sentinel receives · Every send
-
Nothing changes unless you decided it
The template fingerprint, the share of tracked links, the measurement domain. A platform migration that brings a tracker back shows up between two consecutive sends.
Passive: no action, the sentinel receives · Between two sends
-
One-click unsubscribe does what it claims
Your headers declare it; a sentinel uses it, and its control sentinel stays subscribed. If sends keep arriving on the first one, a header that is announced but doesn't work is a finding in itself.
Active: the system acts, and every action is logged · Subsequent sends
Your questions
What we're asked first
Do we need to connect our sending platform or our CRM? +
No. We read what a recipient receives: no connector, no API key, no account on your tools. What is measured there is what actually arrives.
Does the analysis count as an open or a click? +
No. No image is loaded, no link followed: your sending platform records nothing of our reading, and your statistics remain those of your recipients.
What is the sector comparison based on? +
On the brands whose sends we receive, and every share names that base: so many brands out of so many analysed, never a percentage of an entire sector.
Does a sentinel weigh on our open rates? +
Version Pro
To your sending platform, it's a contact that never opens or clicks: one line in your sends. You decide whether it stays subject to your inactivity rules, and the sentinel's record notes it.
What about our automated journeys, welcome emails, reminders? +
Version Pro
A sentinel enters through the door you want to test: the form, account creation or the import. It then receives what a contact in that journey receives, and every send is measured on arrival.
What about our transactional emails? +
Version Pro
A sentinel placed through account creation receives what no subscription brings in: confirmation, password reset, welcome. They are read with the same criteria as your campaigns.
Start with one of your sends
It is measured for free, without an account, as it lands in an inbox. Sentinels come next, with Version Pro.