How it works
Observe, test, monitor
An email is observed as it arrived, for free. With Version Pro, opened by batches, sentinels you place in your own tools test your rules, then stay in place: whatever changes is dated, with its evidence.
The three phases
-
01 — Observe · free
A mailing, read as it arrived
Submit an email: trackers, links, unsubscribe, authentication — every finding with the excerpt that establishes it. A suspicious message is read the same way, without loading or tracking anything.
-
02 — Test · Version Pro
Your commitments, put to the test
Sentinels, placed in your CRM, your store, or your forms, run tests chosen from a library: unsubscribe, objection to tracking, consent.
-
03 — Monitor · Version Pro
What changes, dated, with its evidence
The sentinels stay in place. A mailing that contradicts a commitment that was met reopens the test, an unexpected sender flags itself: one alert per change, never per mailing.
Observe runs today, with no account. Test and monitor open up with Version Pro, by batches. See Version Pro →
An example, from placement to first alert
A sentinel's life
It receives what your contacts receive, without ever opening anything. Every step of its life is dated in its log, and that log is what the timeline unfolds.
-
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.
-
12 March
Unsubscribed on the chosen date
Via the link in the email: response 200, timestamped, archived. Its control sentinel, placed the same day, stays subscribed.
-
12 to 18 March
Still monitored
The sentinel stays in place. What it receives is now read side by side with what its control sentinel receives.
-
18 March
An email arrives after unsubscribing
The unsubscribed sentinel receives “This week's new arrivals”, and so does its control sentinel: the deviation is confirmed.
-
18/03 · 09:04
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.
Email received after unsubscribing
- Sentinel
- mc-n01@temoin.example
- Placed
- By you, in your CRM, on 3 February
- Sender
- news.maisonclaire.example
- Subject
- This week's new arrivals
- Commitment
- Unsubscribe on 12/03, response 200
- Control
- The same email, received on the control sentinel
Sentinels open up with Version Pro, by batches. Request access →
The sentinel
An address placed in your own systems, that lives like your contacts
A function — receive, unsubscribe, object to tracking —, placement conditions that you declare, and a history that dates itself.
- An address of ours, placed by you
- You add it yourself, as a contact: no access to your systems, no connector. The address gives no hint of what it's testing.
- It goes in through the door being tested
- Form, account creation, import: it goes in like a real contact, and it's the whole journey that gets tested, double opt-in and synchronisations included.
- It opens nothing, clicks nothing
- We load no image and follow no link. To your sending platform, it's a contact that never engages; leaving it under your inactivity rules or excluding it from them is one of its placement conditions.
- You know where it is
- You declare the system, the segment, the consent, and we date the rest. It tests your tools — the sending platform, the synchronisations, the purge rule — and every stage of its life stays in its log.
The result of a test
Three results, never a verdict
A test relates to a commitment you selected, never to the law. Its result is replayed from the log, and gives back the same one.
-
Met
The commitment is checked over the whole test window, and the control sentinel shows there really was something to observe.
-
Deviation found
A mailing contradicts the commitment. It becomes the evidence: dated, with its headers, replayable from the log.
-
Not conclusive
The control sentinel received nothing either: perhaps nothing went out during the window. A silence proves nothing, and the result says so.
Once concluded, a test stays under monitoring: an email that later contradicts a commitment marked as met reopens it as a deviation.
Depending on who's reading it
The same life, a different purpose for each role
A sentinel is placed and lives the same way for everyone. What changes is the deviation each person expects from it.
-
Marketing et CRM
9 AprilThe DKIM signature stops passing
Held across the whole series, it fails on today's email: an authentication regression, with the header that shows it.
-
DPO et juridique
18 MarchAn email arrives after unsubscribing
The unsubscribed sentinel receives “This week's new arrivals”, and so does its control sentinel: the deviation is confirmed.
-
DSI et RSSI
22 AprilAnother sender writes to it
An address only you held receives a message from a sender nothing connects to you: an unexpected use, dated, with its evidence.
-
Agences et cabinets
27 MarchA line in your portfolio changes
Among your brands, Maison Claire moves into deviation: its unsubscribe link is now tracked, found without access to its tools.
Start by observing
Upload an email: its report tells you where you stand today. Version Pro checks that it still holds true tomorrow.