Skip to content

SparkPostOpen-tracking pixel, click tracking and unsubscribe

In our corpus, 36 of the 47 emails sent through SparkPost, by 10 brands, loaded an open-tracking pixel (77%).

API / Transactionnel · Renamed to Bird (2024) · code sparkpost

Compare

American sending infrastructure, acquired by MessageBird in 2021 and sold under the Bird name since 2024. Its Momentum sending server, which other platforms such as Adobe Campaign also run, adds the X-MSFBL header.

Renamed to Bird (2024). The product and its emails are the same; only the name and the site have changed. The internal code, however, does not move — it's what the measurements already made are attached to.

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 contact, Consent — absence means no pixel, Tracking anonymization, Traceable choice, List-Unsubscribe, RFC 8058 — one click, Preferences page, Transactional exceptions, DKIM, SPF, DMARC, Logging, API, Consent history, Granularity of settings.

Postmetry corpus

What brands actually send

Observation base 10 brands · 3 months 47

47 messages received from 08/19/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 7 not verified

Open pixel Not verified Pas encore documenté Non vérifié Observed seen on 21 of 31 emails from 7 brands, 3 months
Click tracking Not verified Pas encore documenté Non vérifié Observed seen on 31 of 31 emails from 7 brands, 3 months
Exclusion by campaign Yes 1 note · 20/08/2026 Out of reach
By default

and archive recipient lists and disable open and/or click tracking

Caveat Per message via X-MSYS-API over SMTP; over REST, options per transmission and per individual recipient (options block per recipient in the Transmissions API) — recipient-level granularity therefore exists at send time, without a stored profile field.

SMTP API · API documentation · last reviewed on 08/20/2026 · confidence high

Exclusion by contact Not verified Documentation muette Non vérifié Out of reach
Consent — absence means no pixel Not verified Documentation muette Non vérifié Out of reach
Native consent collection Non vérifié Pas encore documenté Non vérifié Out of reach
Tracking anonymization Not verified Documentation muette Non vérifié Out of reach
Traceable choice Not verified Documentation muette Non vérifié Out of reach

Unsubscribe 4 not verified

List-Unsubscribe Not verified Pas encore documenté Non vérifié Observed seen on 15 of 31 emails from 7 brands, 3 months
RFC 8058 — one click Not verified Pas encore documenté Non vérifié Observed seen on 15 of 31 emails from 7 brands, 3 months
Preferences page Not verified Documentation muette Non vérifié
Transactional exceptions Not verified Pas encore documenté Non vérifié

Authentication 3 not verified

DKIM Not verified Pas encore documenté Non vérifié Observed seen on 47 of 47 emails from 10 brands, 3 months
SPF Not verified Pas encore documenté Non vérifié Observed seen on 47 of 47 emails from 10 brands, 3 months
DMARC Not verified Documentation muette Non vérifié Observed seen on 47 of 47 emails from 10 brands, 3 months
Sending domain Yes 1 note · 20/08/2026 Never observed out of 47 emails from 10 brands, 3 months
By default

The domain you are sending from. It will be used in the "From:" header

Caveat Verified sending domains (DNS or verification mailbox), a separate CNAME bounce domain for alignment, controlled sharing with subaccounts.

Sending Domains API · API documentation · last reviewed on 08/20/2026 · confidence high

Tracking domain Yes 1 note · 20/08/2026 Never observed out of 31 emails from 7 brands, 3 months
By default

SparkPost picks the first tracking domain it can find to use in this order

Caveat An explicit hierarchy: 1. domain associated with the sending domain, 2. subaccount default, 3. account default. A verified CNAME is required, HTTPS configurable. Paths /f/ (clicks) and /q/ (opens) — URL pattern for esp_signatures.

Tracking Domains API · API documentation · last reviewed on 08/20/2026 · confidence high

Infrastructure & governance 4 not verified

Logging Not verified Pas encore documenté Non vérifié Out of reach
API Not verified Pas encore documenté Non vérifié Out of reach
Consent history Not verified Documentation muette Non vérifié Out of reach
Granularity of settings Not verified 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 47 messages received

Open pixel loaded 77 %

36 messages out of 47

List-Unsubscribe present 38 %

18 messages out of 47

RFC 8058 declared 38 %

18 messages out of 47

Brand's tracking domain 0 %

0 messages out of 47

Period observed

08/2026 → 30/10/2026

3 months, 10 distinct brands.

Identification signals

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

  • scph0622 26 %
  • scph0624 23 %
  • scph1223 17 %
  • scph1021 13 %
  • scph1025 9 %
  • sparkpostmail.com 6 %
  • scph0123 2 %
  • scph0423 2 %
  • scph0824 2 %

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

Frequently asked questions

Can you turn off open tracking in SparkPost?

Yes, campaign by campaign: SparkPost lets you send a campaign without inserting the open-tracking pixel.

Do your emails go through SparkPost?

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