Skip to content

An audit tells you what works today. Version Pro checks that it still works tomorrow.

Continuous monitoring measures every email on arrival and keeps it as evidence. With your first access, you place your sentinels; it runs your tests and warns you when something changes.

Still with no access to your systems.

Six benefits, in order of importance

What you get by moving to Version Pro

  1. Continuous analysis

    Every mailing is received, measured, and archived on arrival: trackers, links, unsubscribe, authentication. You see the trajectory of your mailings, not a snapshot taken on audit day.

  2. The integrity of your database

    A sentinel, which we set up with your first access, is known only to the system where you placed it. If another sender writes to it, you'll know: an unexpected use, dated, named, with the message as evidence.

  3. Unlimited sentinels

    As many sentinels as there are tests to schedule: unsubscribe on a set date, purge on deadline, duplicates. Tests open batch by batch as access is granted, and every GDPR rule gets checked against real mailings.

  4. Alerts with the mailing as proof

    A mailing received after unsubscribing, authentication lost, an unexpected sender on a sentinel: the anomalies are already recorded and dated; sending them to the people concerned — DPO or CRM — with the archived message, opens up with your first access.

  5. Under continuous control

    A badge near your forms: “under continuous control since March 2026.” It states how long your mailings have been tested and the date of the last test, never a score, and it links to the register of what's being tested.

  6. Several brands, one team

    One brand is enough for most. Groups and DPO firms track several in a single dashboard, with each person invited to their own scope.

01 — Deploy your sentinels

Sentinels placed where your contacts live

You add them yourself, like contacts, in your CRM, your store, or your forms. Each one is given a function and its placement conditions; no connector, no access to your systems.

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.
Example

Sentinel record

Sentinel
mc-n01@temoin.example
Function
Unsubscribe on a chosen date
Placed in
Your CRM, “France customers” segment
Consent
Tracking declined, partners declined
Inactivity
Excluded from purge rules
Placed on
3 February, by you

We date the placement and every email received; the rest, you declare, and every finding records it as such.

Example

Test scheduled

Unsubscribe on 12/03/2026

12/03 Unsubscribe performed from the email's link, response 200.
18/03 New email received on the unsubscribed sentinel — “This week's new arrivals”
25/03 Second email received, same sender, same list.
Retention sentinel J+1095

The sentinel should have disappeared from the database by the set deadline. An email received after that date shows it was still in a system.

02 — Launch your scenarios

Your GDPR rules, tested on real emails

As many sentinels as tests to schedule, each with its own function. The monitoring uses them the way a subscriber would: it unsubscribes on a chosen date, waits, counts, and observes what happens next.

  • Unsubscribe at a set date

    After the request, no email should arrive on this sentinel again, nor on another sentinel of the same contact.

  • Purge at the deadline you set

    A sentinel dedicated to retention: by the deadline — three years, for example —, it should have disappeared from the CRM.

  • Duplicates and frequency

    The same email received twice by the same contact, or twice across two sentinels, is flagged as an anomaly.

Three possible results, never a verdict →

03 — Let Postmetry monitor

Every email put through the wringer, down to the source code

The email arrives on a sentinel. The analyzer reads the envelope, the authentication, the unsubscribe headers, then the HTML line by line.

Example
Sender news@maisonclaire.example DMARC not aligned
Recipient mc-n01@temoin.example Sentinel unsubscribed on 12/03
Subject This week's new arrivals Promotional campaign

This week's new arrivals

Three pieces that came into the workshop this week, and a reminder about delivery times.

See the selection Unsubscribe
Source of the 18/03 email Tracking pixel detected
  1. Return-Path: <bounce@news.maisonclaire.example>
  2. Date: Wed, 18 Mar 2026 09:04:12 +0100
  3. Authentication-Results: spf=pass dkim=pass dmarc=fail
  4. DKIM-Signature: v=1; a=rsa-sha256; d=news.maisonclaire.example;
  5. List-Unsubscribe: <https://news.maisonclaire.example/u/9f3a>
  6. List-Unsubscribe-Post: List-Unsubscribe=One-Click
  7. Content-Type: multipart/alternative; boundary="b1"
  9. <p>Nos nouveautés de la semaine</p>
  10. <img src="https://t.maisonclaire.example/o.gif?u=9f3a"
  11. width="1" height="1" style="display:none">

Open tracker

A single-pixel image loaded from a measurement domain.

  • 1 · Envelope and recipient
  • 2 · Headers and authentication
  • 3 · HTML and trackers

On your emails, on every send

GDPR and CNIL: what the rule requires, what we prove

An audit checks your procedures at a point in time. Postmetry checks what your recipients receive, on every send. Dated, identically replayable evidence, not a declaration.

  1. CNIL · Article 82 of the French Data Protection Act

    An open tracking pixel is a tracker. Before it loads, it needs the recipient's consent — not just their sign-up to the list.

    What we check

    We read the source code of every mailing and record the measurement image, its host, and its size, with the excerpt that establishes it.

    The rule in detail →

  2. Article L. 34-5 of the CPCE · Gmail and Outlook requirements

    Every prospecting message must offer a simple way to object, and the request must be acted on.

    What we check

    The test we set up: unsubscribing from the link of a real mailing, on a chosen date, then counting what still arrives at that address.

  3. GDPR, Article 5 · CNIL benchmark for a prospect

    A prospect's data can't be kept indefinitely. The CNIL's benchmark: three years after the last contact.

    What we check

    The sentinel we set up: a retention address must have disappeared from your database by the deadline you set. A mailing received after that date will contradict it, dated.

  4. GDPR, Articles 6 and 13 · Article L. 34-5 of the CPCE

    Sharing your contacts with partners requires their agreement, and that they know who with.

    What we check

    A sentinel, set up with your access, is known only to the system where you placed it. Any third-party sender that writes to it will be recorded, named, and dated.

  5. GDPR, Article 32 · Gmail and Outlook requirements

    The GDPR requires appropriate security measures, and mailbox providers require authenticated mailings: SPF, DKIM, DMARC.

    What we check

    We read the authentication verdict set at the reception of every mailing, and we record every change; the alert to your team opens up with your first access.

We never write a qualification. Every line of the report is a dated finding, with its proof; the conclusion is yours to draw, with your DPO.

What Version Pro monitors for you

Six monitors that run without you

Example

The regular tracking of emails

Every campaign measured on arrival. You see the trajectory, not just the last point, and a criterion added later is reread across all your past emails.

22 Aug Tracking pixel removed from promotional emails +14
4 Aug DMARC alignment lost on a subdomain −9
Example

Alerts

Every anomaly goes out to the people concerned, with the email kept as evidence.

  • Email sent after unsubscribe

    Sentinel mc-n01 · 18/03

    CRM, DPO

  • Drop in the technical score

    DMARC alignment lost

  • Campaign received twice

    Two sentinels, four minutes apart

Example

Under continuous control

Embed it near your forms. It says how long your emails have been tested and the date of the last test, never a score, and it leads to the record of what's being tested.

Get our updates

votre@email.fr Sign up

Under continuous monitoring since March 2026 · Postmetry

Example

Several brands, one team

All your brands in a single dashboard. You invite the DPO, the CRM team, or an outside advisor, with their own scope.

Maison Claire4 sentinels · 0 alerts
Claire Maison & Jardin3 sentinels · 2 alerts
Atelier Claire2 sentinels · 0 alerts
DPO CRM Read-only
Example

The sentinel

A sentinel is known only to the system where the brand placed it. Any unexpected sender that writes to it is a fact, dated and named.

mc-n03@temoin.example

Placed by a single brand, on 04/02/2025

news.maisonclaire.example42 emailsExpected
mail.partenaire-deco.com3 emailsThird party
envoi.promo-maison.net1 emailThird party

Regulatory watch

GDPR, CNIL recommendations, email RFCs, Gmail and Outlook requirements. When a rule changes, the criterion is added and reread across all your past emails.

  • CNIL recommendation

    Tracking pixels

  • RFC 8058

    One-click unsubscribe

  • SPF, DKIM, DMARC

    Authentication

  • GDPR, Article 5

    Data retention

04 — Step in only when something changes

An email goes out after an unsubscribe.
You're notified, with the evidence.

  1. 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.

  2. 5 February

    First email received

    The sentinel becomes active. Every email it receives is measured on arrival and kept as evidence.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Example
Alert sent 18/03 · 09:04

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
Deviation found Message archived

On 25 March, the fix is checked on the next email: the resolution is dated the same way as the deviation, and replays the same way.

Without monitoring, the next one to notice would have been a subscriber, a mailbox provider, or the CNIL.

The question we're asked

“I already took the free diagnostic. Why pay?”

Because the diagnostic measures once. It knows nothing about the provider changed in June, or the unsubscribe forgotten in March.

Free tools Version Pro
Your mailings are analysed Once, the one you submit All of them, every campaign
You're notified when something changes No Yes, with the mailing as proof
You know when another sender writes to your sentinels No Yes, with the sender and date to back it up
Your GDPR rules are tested On your answers to a questionnaire On real mailings, on the date you set
You can show it A report, on audit day A dated control report, and a badge that says since when
Several brands, several people One brand, one person All your brands, DPO and CRM invited

Access opened by batches, prepared before the call

Access opens by batches. Leave your sending domain: we prepare your sentinels and the first reading before we call you.

Or write to [email protected]