MailgunOpen-tracking pixel, click tracking and unsubscribe
Mailgun can insert an open-tracking pixel, and lets you remove it campaign by campaign.
API / Transactionnel · vendor's site ↗ · code mailgun
API-based sending service for developers, intended for the emails an application generates — confirmations, alerts, resets. Owned by Sinch since 2021, like Mailjet.
Postmetry reference sheet
What the vendor says, checked by us
4 sources · last reviewed on 08/20/2026. Still not checked: 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, Sending domain, Logging, Consent history, Granularity of settings.
Postmetry corpus
What brands actually send
9 messages received from 08/07/2026 to 10/19/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 5 not verified
Open pixel Yes 1 note · 20/08/2026 Too few emails seen on 4 of 4 emails from 2 brands, 3 months
Mailgun uses tracking pixels and URL redirects to track every time a recipient opens
Caveat Off by default (event tracking is automatic except for opens, clicks and unsubscribes — introduction page). Two levels: domain (Tracking Settings) and message (o:tracking / o:tracking-opens, which overrides the domain). Pixel position: bottom by default, top via o:X-Mailgun-Track-Pixel-Location-Top.
Tracking Opens · Help centre · last reviewed on 08/20/2026 · confidence medium
Click tracking Yes 1 note · 20/08/2026 Too few emails out of 4 emails from 2 brands, 3 months
When you enable Click tracking, links will be overwritten and point to Mailgun's servers
Caveat Opt-in; o:tracking-clicks accepts htmlonly (rewrite the HTML, leave the text untouched); disabling per link via the HTML attribute disable-tracking=true (introduction page) — documented link-level granularity, rare in this group.
Tracking Clicks · Help centre · last reviewed on 08/20/2026 · confidence medium
Exclusion by campaign Yes 1 note · 20/08/2026 Out of reach
can be enabled on two levels – per sending domain (as mentioned above) and per message
Caveat The per-message setting overrides the domain in both directions (enabling as well as switching off). An implementation nuance noted by the ecosystem: o:tracking must accompany o:tracking-opens/clicks to override a domain set to OFF — to be observed.
Tracking Messages Introduction · Help centre · last reviewed on 08/20/2026 · confidence medium
Unsubscribe 4 not verified
Authentication 4 not verified
Tracking domain Yes 1 note · 20/08/2026 Too few emails out of 4 emails from 2 brands, 3 months
You will need to point CNAME records to mailgun.org for Mailgun to rewrite links and track opens.
Caveat Finding: the branded CNAME is a condition of tracking, not a convenience option — without it, there is neither link rewriting nor a pixel, and the UI blocks the settings. HTTPS via Let's Encrypt on the existing CNAME, HSTS supported, certificates can be regenerated via the API. CNAME target mailgun.org = signature in our corpus.
Tracking Messages Introduction · Help centre · last reviewed on 08/20/2026 · confidence medium
Infrastructure & governance 3 not verified
API Yes 1 note · 20/08/2026 Out of reach
Mailgun offers tracking for clicks, unsubscribes, and opens, with optional HTTPS protocol support
Caveat Tracking settings can be read and modified via the API at every level (domain, message via o:* parameters, link via an attribute); webhooks deduplicated at account/domain level.
Domain Tracking · API documentation · last reviewed on 08/20/2026 · confidence high
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.
9 messages, 6 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 → 19/10/2026
3 months, 6 distinct brands.
Identification signals
What we recognized the sending platform by, message by message.
- X-Mailgun-Sid 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
4 sources- Tracking Opens Help centre · confidence medium 20/08/2026
- Tracking Messages Introduction Help centre · confidence medium 20/08/2026
- Tracking Clicks Help centre · confidence medium 20/08/2026
- Domain Tracking API documentation · confidence high 20/08/2026
Comparable sending platforms
Compare the whole family →Frequently asked questions
Can you turn off open tracking in Mailgun?
Does Mailgun rewrite links for click tracking?
Do your emails go through Mailgun?
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.