Amazon SESOpen-tracking pixel, click tracking and unsubscribe
API / Transactionnel · AWS · vendor's site ↗ · code amazon-ses
Amazon Web Services' fully managed email sending service, which applications call through an API or SMTP. It handles transactional messages as well as campaigns and newsletters.
Postmetry reference sheet
What the vendor says, checked by us
5 sources · last reviewed on 08/20/2026. Still not checked: Open pixel, Tracking anonymization, List-Unsubscribe, RFC 8058 — one click, Preferences page, Transactional exceptions, SPF, Sending domain, Logging, API, Consent history, Granularity of settings.
Postmetry corpus
What brands actually send
29 messages received from 08/08/2026 to 10/30/2026. Below the threshold of 30 messages and 8 brands: no rate is published.
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 2 not met · 1 partial · 3 not verified
Click tracking Yes 1 note · 20/08/2026 Too few emails seen on 5 of 13 emails from 4 brands, 3 months
To capture link click events, SES replaces the links in your emails with links
Caveat Links are rewritten to point to an SES server, under the same event publishing condition. Default domains are operated by AWS (pattern awstrack.me — to be established in our corpus, not cited on the page).
Configuring custom domains to handle open and click tracking · API documentation · last reviewed on 08/20/2026 · confidence high
Consent — absence means no pixel No 1 note · 04/08/2026 Out of reach
A sending infrastructure, not a campaign tool. It handles no consent at all: a developer can perfectly well send without a pixel, but all the logic lives in their application. The capability is real; it simply isn't in the product.
Observations in the interface, first batch · Help centre · last reviewed on 08/04/2026 · confidence medium
Unsubscribe 4 not verified
Authentication 2 not verified
DKIM Yes 1 note · 20/08/2026 Too few emails seen on 29 of 29 emails from 16 brands, 3 months
SES génère une paire de clés public/privé et ajoute automatiquement une signature DKIM
Caveat Four documented modes: Easy DKIM (CNAME), DEED (multi-region), BYODKIM and manual signing — the widest range among the tools we reference. Signatures are "facultatives" (optional) in principle.
Authentification d'e-mails avec DKIM dans Amazon SES · API documentation · last reviewed on 08/20/2026 · confidence high
DMARC Yes 1 note · 20/08/2026 Too few emails seen on 28 of 29 emails from 16 brands, 3 months
les messages doivent être authentifiés par le biais du SPF ou du DKIM
Caveat Guide to meeting DMARC via SPF (custom MAIL FROM) or DKIM; the policy is left to the client.
Mise en conformité au protocole d'authentification DMARC dans Amazon SES · API documentation · last reviewed on 08/20/2026 · confidence high
Tracking domain Yes 1 note · 20/08/2026 Too few emails out of 13 emails from 4 brands, 3 months
Specify a custom domain to use for open and click tracking elements
Caveat Custom redirect domain per configuration set (several possible), with a three-mode HTTPS policy (REQUIRE / REQUIRE_OPEN_ONLY / OPTIONAL) — a per-stream granularity not seen elsewhere. "all SES indicators are removed" with a custom domain (developer guide page).
put-configuration-set-tracking-options · API documentation · last reviewed on 08/20/2026 · confidence high
Infrastructure & governance 4 not verified
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.
29 messages, 16 brands, below the threshold of 30 messages and 8 brands: no rate is published. A percentage on so few emails, or so few brands, describes what one brand configured, not what the sending platform does.
Period observed
08/2026 → 30/10/2026
3 months, 16 distinct brands.
Identification signals
What we recognized the sending platform by, message by message.
- amazonses.com 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
5 sources- put-configuration-set-tracking-options API documentation · confidence high 20/08/2026
- Mise en conformité au protocole d'authentification DMARC dans Amazon SES API documentation · confidence high 20/08/2026
- Configuring custom domains to handle open and click tracking API documentation · confidence high 20/08/2026
- Authentification d'e-mails avec DKIM dans Amazon SES API documentation · confidence high 20/08/2026
- Observations in the interface, first batch Help centre · confidence medium 04/08/2026
Comparable sending platforms
Compare the whole family →Frequently asked questions
Can you turn off open tracking in Amazon SES?
Does Amazon SES rewrite links for click tracking?
Do your emails go through Amazon SES?
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.