Skip to content

SplioOpen-tracking pixel, click tracking and unsubscribe

In our corpus, 231 of the 234 emails sent through Splio, by 26 brands, loaded an open-tracking pixel (99%).

vendor's site ↗ · code splio

Compare

French customer-relationship marketing platform, focused on loyalty and retail.

Postmetry reference sheet

What the vendor says, checked by us

Documentation maturity 3 / 20 capabilities 15 %

3 sources · last reviewed on 08/20/2026. Still not checked: Open pixel, Click tracking, Exclusion by campaign, Exclusion by contact, Consent — absence means no pixel, Tracking anonymization, Traceable choice, List-Unsubscribe, RFC 8058 — one click, Transactional exceptions, SPF, DMARC, Tracking domain, Logging, API, Consent history, Granularity of settings.

Postmetry corpus

What brands actually send

Observation base 26 brands · 3 months 234

234 messages received from 08/02/2026 to 10/30/2026.

Postmetry reference sheet

What this ESP allows

Catalog shared by both pages. Each note carries its source, its date, and its confidence level.

On the right, what our emails say about it: matching, contradicted, never observed despite the volume, too few emails to conclude — or out of reach, when the capability can't be read from an email.

Tracking 8 not verified

Open pixel Non vérifié Pas encore documenté Non vérifié Observed seen on 214 of 214 emails from 26 brands, 3 months
Click tracking Not verified Documentation muette Non vérifié Observed seen on 214 of 214 emails from 26 brands, 3 months
Exclusion by campaign Non vérifié Pas encore documenté Non vérifié Out of reach
Exclusion by contact Non vérifié Pas encore documenté Non vérifié Out of reach
Consent — absence means no pixel Non vérifié Pas encore documenté Non vérifié Out of reach
Native consent collection Non vérifié Pas encore documenté Non vérifié Out of reach
Tracking anonymization Non vérifié Pas encore documenté Non vérifié Out of reach
Traceable choice Non vérifié Pas encore documenté Non vérifié Out of reach

Unsubscribe 3 not verified

List-Unsubscribe Non vérifié Pas encore documenté Non vérifié Observed seen on 214 of 214 emails from 26 brands, 3 months
RFC 8058 — one click Non vérifié Pas encore documenté Non vérifié Observed seen on 214 of 214 emails from 26 brands, 3 months
Preferences page Yes 1 note · 20/08/2026
By default

Gérez les abonnements de vos contacts avec le centre de préférences - Avr.

Caveat Preference centre launched in April 2025 — a dated capability, which is rare. The Splio unsubscribe form already existed (unsubscribe reasons in reporting). Hosting and customisation: a dedicated article to open.

Splio Product Updates · Help centre · last reviewed on 08/20/2026 · confidence medium

Transactional exceptions Non vérifié Pas encore documenté Non vérifié

Authentication 3 not verified

DKIM Yes 1 note · 20/08/2026 Consistent seen on 234 of 234 emails from 26 brands, 3 months
By default

une signature cryptographique que Splio inclura dans les en-têtes de votre message

Caveat Splio signs, with public keys in the client's DNS; the guide also covers SPF (merged into a single record) and DMARC (reporting function) — spf/dmarc anchors to be added in a second pass on the same page.

Authentification des emails avec Splio : Guide DNS essentiel · Help centre · last reviewed on 08/20/2026 · confidence medium

SPF Non vérifié Pas encore documenté Non vérifié Observed seen on 234 of 234 emails from 26 brands, 3 months
DMARC Non vérifié Pas encore documenté Non vérifié Observed seen on 231 of 234 emails from 26 brands, 3 months
Sending domain Yes 1 note · 20/08/2026 Never observed out of 234 emails from 26 brands, 3 months
By default

les clients dédient un sous-domaine ou un nom de domaine aux envois

Caveat The first contractual source among the tools we reference: a dedicated subdomain is an obligation of the charter, with a publicly identifiable WHOIS owner required. The charter also requires an unsubscribe link that is "clairement visible et fonctionnel" (clearly visible and functional) — contractual reinforcement of list-unsubscribe.

Charte anti-spam · Contractual document · last reviewed on 08/20/2026 · confidence high

Tracking domain Non vérifié Pas encore documenté Non vérifié Never observed out of 214 emails from 26 brands, 3 months

Infrastructure & governance 4 not verified

Logging Non vérifié Pas encore documenté Non vérifié Out of reach
API Non vérifié Pas encore documenté Non vérifié Out of reach
Consent history Non vérifié Pas encore documenté Non vérifié Out of reach
Granularity of settings Non vérifié Pas encore documenté Non vérifié Out of reach

Postmetry corpus

Observed in our corpus

Recorded by our analyzers on messages received on addresses we control. Nothing from the reference sheet here, no access to the tool.

Out of the 234 messages received

Open pixel loaded 99 %

231 messages out of 234

List-Unsubscribe present 100 %

234 messages out of 234

RFC 8058 declared 100 %

234 messages out of 234

Brand's tracking domain 0 %

0 messages out of 234

Period observed

08/2026 → 30/10/2026

3 months, 26 distinct brands.

Identification signals

What we recognized the sending platform by, message by message.

  • splio 100 %

Limits of this analysis

It doesn't say what a brand has actually configured. A sending platform that allows turning off the pixel says nothing about which brands have done so — that's what a brand's report answers.

It doesn't rank. No score, no recommendation: capabilities don't carry the same weight depending on the use, and that weight isn't ours to set.

A “not checked” cell is not a “no”. It says nobody has gone to look yet, and nothing else.

The corpus does not establish a capability. A rate of observed pixels says what brands send, not what the tool can do.

Sources

3 sources

Do your emails go through Splio?

The sending platform is read from the headers, not from a claim. The report names it, and says where to fix the findings with that vendor.

Analyze one of my emails