For DPOs and legal teams
Your procedures are written. Check that they are applied.
Today, free of charge: your open-tracking practices are read against the CNIL rule, with each deviation in detail. With Version Pro, rolled out in batches, sentinels put what your procedures promise to the test: unsubscribing, objecting to tracking, declining partners.
Today · free
Your tracking practices, read against the rule
Seven to ten questions on how your emails measure opens. Based on your answers, the result sets out the rule and the conditions it lays down, without deciding for you which one applies.
- — Answer an internal question with evidence, not a statement.
- — Identify the rule that applies to tracking and the conditions it sets.
- — Keep the state of a mailing even after the template is changed.
The diagnostic
- 01 An immediate score, based on your answers, with its breakdown by area.
- 02 What to look at: each deviation, with the rule and the conditions it lays down.
- 03 The full report as a PDF, sent to your inbox.
- 04 From self-reported to observed: the audit of one of your real emails.
Version Pro · an example
An email after unsubscribing
Unsubscribing is promised in a policy and handled in an ESP, sometimes in several. A sentinel unsubscribed on a chosen date, alongside a control sentinel that stays subscribed, shows whether the emails stopped.
-
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
- Silence alone proves nothing
- If the unsubscribed sentinel receives nothing more, its control sentinel shows whether the brand kept sending. Without it, the test is not conclusive, and the report says so.
- Every action, logged
- The unsubscribe click, its response and its time are archived with the email that followed it. The result is replayed from the log, identically.
- The fact, and your decision
- The alert says what was received, when, and after which action. What the rule concludes from it is yours to decide, evidence in hand.
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.
-
Unsubscribing is handled, and when
A sentinel unsubscribes on a chosen date, then the checks follow, for up to thirty days. The result is an observed delay, never a verdict.
Active: the system acts, and every action is logged · 30 days
-
Objecting to tracking alone is respected
A sentinel declines tracking from your preference centre, without unsubscribing. The following emails show whether the open tracker has disappeared.
Active: the system acts, and every action is logged · Next email
-
Declining partners is honoured
A sentinel signs up through your form, partner box declined, and the state of the page is recorded; another accepts it. A third-party sender on the first one only becomes an attributable deviation.
Active: the system acts, and every action is logged · 30 and 90 days
Your questions
What we're asked first
Does the product tell us whether we follow the rules? +
It tells you what can be observed, with the excerpt of the message that establishes it. The rule and its conditions are set out alongside; what it concludes remains your decision.
Does a finding hold if the template has changed since? +
The message is archived as it arrived, never modified. A dated finding can be reread on the original evidence, even when the next day's email no longer looks like it.
Does repeating a measurement give the same result? +
Yes. Each measurement comes from a versioned analyser, with no network and no randomness: replayed on the same message, it returns the same result, and the version that produced it is recorded.
Who on our side knows where a sentinel is placed? +
Version Pro
Those you choose. The sentinel is known to the brand, and the control report says so: it tests your systems, not the good faith of those who operate them.
What is a test worth if nothing was sent? +
Version Pro
It returns “not conclusive”, and says so. Any test that draws a conclusion from an absence pairs two sentinels placed under the same conditions, only one of which undergoes the action.
What is left at the end of a test? +
Version Pro
A control report: the protocol, the date of each action, the messages received and the result — met, deviation found or not conclusive. It can be passed on as is, internally or to an adviser.
Start with your tracking practices
The diagnostic is free, with no account, and details each deviation against the rule. Sentinels come next, with Version Pro.