Is Elastic Email Tracking Your Email? How to Block It

Elastic Email tracking is not subtle once you know where to look, and it is not optional from your side of the message. A newsletter arrives, your mail client fetches an invisible image, and a row lands in the sender's activity log with the timestamp, the IP the request came from and enough to name your device class. The vendor documents all of this openly. What it does not advertise is how hard its own setup makes blocking by name.

This is a platform built for bulk. Elastic Email's own email API pricing starts at $19 a month for 50,000 emails, roughly 38 cents per thousand. The record of when you read your mail costs the sender about four hundredths of a cent to produce.

Key Takeaways

• Elastic Email's help center states that it "tracks your emails by displaying a tracking pixel," an image "the size of a single pixel, hidden from the actual email contents."
• Tracking is switched by the trackOpens and trackClicks REST parameters and by the trackopens and trackclicks SMTP headers, so transactional mail carries the same pixel as a campaign.
• The API v4 endpoint GET /events returns a per message log whose EventType values include Open and Click, alongside EventDate, To, Subject and IPAddress.
• Elastic Email's custom tracking domain moves the tracking host onto a subdomain the sender owns, set up as a CNAME from tracking to api.elasticemail.com.
• Because every customer can mint its own tracking hostname, the domains a blocklist must carry grow with the customer base rather than staying at one vendor name.

What Is Elastic Email Tracking?

Elastic Email tracking is the platform's built in open and click reporting: an invisible image reports that you read the message, and rewritten links report which ones you clicked. The company's guide to tracking opens and clicks says it "tracks your emails by displaying a tracking pixel," described as "an image that is the size of a single pixel, hidden from the actual email contents."

Clicks work by interception, and the custom tracking domain explainer puts it without euphemism: "To track those clicks, Elastic Email rewrites the links in your emails. The rewritten links will briefly direct the user through our system so the 'click' can be registered." The address you see on hover is not the address you reach first.

One honest limit belongs here, and the vendor states it itself. Its note on open and click rates says that "in some cases, email software blocks displaying images. When this happens, a tracking pixel is not displayed and thus an open is not counted." Plain text messages carry no pixel at all.

What Does Elastic Email Record About You?

It records a timestamped event per open and per click, tied to your address, with the IP the request came from, a location derived from that IP, and the class of device you read on. The developer side shows this most clearly. Elastic Email's REST API v4 documentation exposes an Events group whose GET /events endpoint "returns a log of delivery events filtered by specified parameters." Those records carry TransactionID, MsgID, To, Subject, EventType, EventDate and IPAddress, with EventType taking values such as Sent, Open, Click, Bounce, Unsubscribe and Complaint.

That shape is the point. A dashboard percentage is an aggregate; an events endpoint with an export function is a queryable history of one named recipient. The same data feeds two reports:

• Geography. The Geography screen "will present you with the geographical data of where your emails were opened," using "IP based geolocation to approximate the geographic location of your email recipients." Country level worldwide, with the United States broken down by state.
• Device details. The Device Details screen "shows you detailed information on what devices your recipients are using to open your emails," sorted into Desktop, Mobile, Tablet and Other. For desktop opens, "instead of device model, we recognize either an email client or browser brand used to open an email."

Elastic Email is candid about something most vendors gloss over. Its geography page warns that "Google Gmail processes all images in emails, including tracking pixels, through its own proxy servers," so the reported location "might map to Google's data centers rather than the recipient's exact location." Gmail's proxy hides your address. It does not stop the open being recorded.

Why Can't a Blocklist Just Name the Domain?

Because Elastic Email lets each sender put the tracker on a subdomain it owns. The custom tracking domain documentation says "the domain that we use to rewrite the links is what we call a 'tracking domain,'" and the domain verification guide gives the recipe: a CNAME record with "Host/Name: tracking" and "Value: api.elasticemail.com." The platform "will look for either 'tracking' or 'email' automatically."

Follow that through. A retailer at example.test sets up tracking.example.test, and from then on the pixel and the click redirect load from a hostname carrying the retailer's brand that sits on no list anywhere. The stated motive is deliverability, not evasion: "using your own domain will help you build your own sender reputation." Evasion is the side effect, and the side effect is what reaches your inbox.

This is the structural reason a static blocklist decays. One vendor name is a fixed target; one tracking hostname per customer is a target that grows every time somebody signs up. The same design runs across the low cost sending market, which is why our breakdowns of MailerSend email tracking and SparkPost email tracking land in the same place. A list that never updates quietly stops working.

One consolation for anyone inspecting a suspicious message: the CNAME is public. A custom tracking domain must resolve back to api.elasticemail.com for the platform to serve the pixel, so a hostname that looks like the sender's own resolves, on inspection, to the vendor. That cuts both ways, and it favours the person doing the checking.

Does the SMTP Relay Path Track You Too?

Yes, and it uses the same switches under different names. Elastic Email's tracking documentation lists trackOpens=true/false and trackClicks=true/false as REST API parameters, and trackopens=true/false and trackclicks=true/false as SMTP headers for anyone relaying mail through the service.

That matters more than it sounds. A shopping cart, a helpdesk or a WordPress plugin pointed at the relay is not running a marketing campaign, but its password resets, order confirmations and shipping notices go through the same pipeline and can carry the same pixel. Transactional mail is the category readers assume is safe because it is functional. Nothing in the plumbing enforces that assumption.

A note for compliance readers. Elastic Email carries a per contact ConsentTracking field, set to Allow, Deny or Unknown, and a Deny value overrides the account's global tracking setting. That is a real control. It is also entirely in the sender's hands, populated by whatever it captured at signup, and you cannot inspect its value from inside a message.

How Do You Tell If a Message Is Tracked?

Read the raw source and look for a one by one image plus links that point somewhere other than where they claim. In Gmail on the desktop, open the message, click the three dot menu at the top right and choose Show original. Then run three checks.

1. Search for <img and height="1". A one pixel image with no meaningful alt text near the end of the body is the classic open beacon.
2. Compare a link's visible text with its href. If the button names the sender's shop and the target is a different host with an opaque identifier in the query string, the click is counted.
3. Check where that hostname points. A CNAME resolving to api.elasticemail.com names the platform behind a subdomain that looks like the sender's own.

Our walkthrough on detecting email tracking pixels in Gmail covers the same inspection for trackers that do not announce themselves. One caveat: no pixel is not proof of privacy, because a rewritten link tracks a click with no image involved.

How Do You Block Elastic Email Tracking?

Start by stopping your mail client from fetching remote images, because that defence ignores hostnames entirely and therefore survives the custom tracking domain problem. In Gmail on the desktop, open Settings, See all settings, and under Images choose Ask before displaying external images, following Google's guide to turning images on or off in Gmail. Gmail's default is the opposite: it proxies images through Google, which conceals your IP address but still fetches the pixel, so the open still lands in the sender's log.

Links need separate handling. No image setting touches a rewritten link, so a click still reports the time, the message and your identity even with every image blocked.

Which Blocker Actually Handles This?

Named honestly, with the custom tracking domain as the deciding column. Our roundup of email tracker Chrome extensions goes further on each option.

Where Gblock fits, without inflation. It blocks tracking pixels from loading and strips tracking redirects out of links before you click, and its blocklist updates on its own rather than waiting for a release, which is what keeps pace with new tracking subdomains. It runs inside Gmail, so your address and provider stay where they are. What it cannot do is name a hostname nobody has seen yet, so pair it with the images setting above. Our comparison guide on how to block email tracking in Gmail walks the settings in order.

What This Means for Your Inbox

Relays like this one sit underneath software you never chose. You signed up with a shop or a SaaS tool; its mail may travel through Elastic Email, Postmark, SparkPost or half a dozen others, and the tracking configuration belongs to whoever wrote the integration. Our look at Postmark email tracking found the identical pattern: a documented pixel most senders leave on because the dashboard looks empty without it.

The scale is not in doubt. Englehardt, Han and Narayanan's Princeton study, I never signed up for this!, examined more than 12,000 emails from roughly 900 senders and found 85 percent carried embedded third party content, 70 percent of it classed as trackers by protection lists. Custom tracking domains erode exactly those lists, one CNAME at a time.

So work in this order, and treat the boring step as the load bearing one:

1. Set Gmail to Ask before displaying external images. It is the only defence that holds when the pixel sits on an uncatalogued hostname.
2. Inspect a suspect message with Show original, looking for a one by one image and links whose target does not match their label.
3. Add a blocker that handles rewritten links as well as pixels, because no image setting touches a redirect.
4. Prefer a blocklist that updates itself, and treat any list, ours included, as the layer on top rather than the floor.

Sources: Elastic Email: Tracking opens and clicks; Elastic Email: What is a custom tracking domain and why is it important; Elastic Email: How to verify your domain; Elastic Email: Geography; Elastic Email: Device details; Elastic Email: Your open and click rates; Elastic Email REST API v4 documentation; Elastic Email: Email API pricing; Princeton CITP: I never signed up for this!; Google: Turn images on or off in Gmail. Vendor documentation was read on 1 September 2026. Elastic Email does not publish a fixed pixel URL path, so none is stated here; the verifiable anchor is the tracking CNAME target, api.elasticemail.com.