Is Ghost Tracking Your Email? How to Block It

Ghost has a good reputation with privacy minded readers, and mostly it earns it. It is open source, you can read the code, it does not run an advertising business, and it does not sell a data product built on your reading habits. None of that means the newsletter in your inbox is untracked. Opens and clicks are measured by default in Ghost, and the click side is measured in a way that is unusually hard to filter, because the tracking link is not on a tracking company's domain. It is on the publication's.

Key Takeaways

• Ghost sends bulk newsletters exclusively through Mailgun, whose open tracking works by embedding a transparent PNG that loads from Mailgun's servers when you open the message.
• Every link in a tracked Ghost newsletter is rewritten to https://yourpublication.com/r/<8 hex characters>, with your member UUID appended as the m query parameter.
• Email click analytics is enabled by default in Ghost and can be switched off by the publisher, not by you.
• Ghost's redirect handler validates the m parameter against a UUID pattern, fires an internal event, and then issues a redirect to the real destination, all in the time it takes the page to move.
• Because the redirect sits on a first party domain that also serves the publication itself, domain blocklists cannot drop it without breaking the site.

Does Ghost Track Email Opens?

Yes, and the mechanism is Mailgun's rather than Ghost's own. Ghost's documentation is blunt about the dependency: "At present, Mailgun is the only supported bulk email provider", and self hosted installs configure it by entering Mailgun API keys. Whether the publication runs on Ghost(Pro) or on someone's own server, the newsletter leaves through Mailgun.

Mailgun's open tracking is the classic implementation. Its own documentation describes a transparent PNG file inserted into the HTML body, which your mail client requests the moment it renders the message. Mailgun notes that text only emails will not track opens, which is the whole story in one sentence: the open event exists only because your client fetched a remote image. We went through the sender side of this in detail in our guide to what Mailgun records about your opens and clicks.

Open tracking is toggled per domain in Mailgun's tracking settings, or per message with the o:tracking and o:tracking-opens parameters. That control belongs to the sender. From the inbox you cannot tell which way it is set until you look at the message source and find the pixel, or fail to.

What Does a Ghost Tracking Link Actually Look Like?

It looks like the publication's own website, which is the point. Ghost's link redirection service builds each tracked link as /r/ plus a slug generated from four random bytes rendered as hex, so eight characters, on the site's base URL. A tracked link therefore reads as something like https://yourfavouritenewsletter.com/r/3f8a1c9d rather than a recognisable analytics vendor.

The identification happens in the query string. Ghost's link redirects service reads the member UUID from the m parameter of the incoming request and checks it against a UUID pattern before using it. So the link that arrives in your copy of the newsletter is not the link that arrived in anyone else's copy: the redirect slug is shared, and the m value is yours alone.

On the click itself, the service dispatches an internal event, sets an X-Robots-Tag of noindex, nofollow on the response so search engines ignore the redirect, and sends you on to the real destination. The whole thing is over in one hop, and the address bar settles on the page you expected. Nothing in the experience tells you a click was attributed to your membership record.

What Can a Ghost Publisher See About You?

More than an aggregate percentage, and less than a full behavioural profile.

Ghost's post analytics documentation defines opens as "the number of unique members that opened your newsletter" and clicks as "the number of unique members who clicked a link in your newsletter", with rates compared against the averages of the last 20 newsletters sent. Unique members, not anonymous counts, is the operative phrase. The changelog announcing newsletter click analytics is explicit that a publisher can get a breakdown of exactly which members opened or clicked, and that the feature is enabled by default.

In practice that means a Ghost publisher can answer questions about you specifically. Whether you opened the last six issues. Which of two links you chose. Whether you have gone quiet, which is the input to a re engagement campaign or a cleanup that removes you from the list. That is ordinary newsletter operations, and it is also a per person reading log that you were never shown a consent screen for.

Why Is First Party Tracking Harder to Block?

Because the usual defence is a list of bad domains, and there is no bad domain here.

Most tracking domain blocklists work on the assumption that tracking lives somewhere obvious and separate, the way Beehiiv and Substack route their measurement through hosts you can name and refuse. Ghost's click redirect is served by the publication's own web server on the publication's own domain. Blocking it means blocking the site you subscribed to read.

The open pixel is a softer target but still not a fixed name: it is served through the Mailgun sending domain that the publication configured, frequently a subdomain of the publication's own domain rather than anything branded Mailgun. So a rule written for one Ghost newsletter tells you nothing about the next one. The defence that works here is structural rather than list based: stop your client fetching remote images at all, and stop the redirect being the thing that carries you to the destination.

Can the Publisher Just Turn It Off?

Yes, completely, and some do. Ghost's help page on disabling analytics states that "all analytics features in Ghost, including web analytics, newsletter opens, newsletter clicks, member sources and outbound link tagging can be turned off", under Settings then Analytics.

Credit where it is due: that is a single switch that removes the entire apparatus, which is more than most platforms in this category offer, and it is genuinely one of the better privacy postures available to a publisher. But it is opt out, not opt in. The default is on, and the decision sits with the person sending, not the person reading. If you want a guarantee rather than a hope, it has to come from your side of the message.

How Do You Block Ghost Newsletter Tracking?

• Stop the open from ever registering. The Mailgun pixel is an image request. If it never fires, there is no open event, no timestamp and no record that the message reached a live human. Gblock strips tracking pixels out of messages in Gmail before your browser requests them, so the newsletter renders and the beacon does not.
• Turn off automatic image loading in Gmail as a backstop. Settings, General, then "Ask before displaying external images". This blocks everything remote, including the images you actually wanted, which is why most people abandon it, but it is free and it works.
• Do not click the link in the message. Copy the link, and if it is a /r/ redirect you can often reach the destination by opening the publication's website and finding the post there instead. The redirect only attributes a click it actually receives.
• Strip the m parameter if you must use the link. Removing ?m=<uuid> keeps the redirect working while removing the part that says the click was yours. The click still counts in aggregate; it stops being attached to your membership record.
• Read in a client that never loads remote content. Plain text mode or a proxying client defeats pixel tracking by design. Apple's approach does something different and worth understanding: it prefetches images for everyone and reports fake opens, which poisons the data rather than withholding it.
• Check before you assume. Our guide to detecting email tracking pixels in Gmail shows how to read a message source and see what is actually in a given newsletter. Some Ghost publishers really have switched it all off.

The Honest Summary

Ghost is not the villain of this story, and pretending otherwise would be dishonest about a platform whose code you can read and whose analytics can be disabled outright with one switch. It sits at the reasonable end of a bad category.

What it does do is normalise a per member reading log that arrives switched on and lives on a domain you have no way to filter. The pixel is Mailgun's, the redirect is the publisher's, and the UUID in the link is yours. Whether that log exists at all is a decision made by whoever runs the newsletter. Whether it gets any data from you is a decision you can still make yourself, in the inbox, every time a message renders.