Aug 25, 2026 · 10 min read
Is Campaigner Tracking Your Email? How to Block cmpgnr.com
A link in a marketing newsletter points at cmpgnr.com. Six consonants, no vowels, no brand. We probed the domain, its certificate, its DNS and its registration to work out who is waiting on the other end of that click.
Hover a button in a marketing email and read the status bar before you click. If it says cmpgnr.com, you are looking at Campaigner email tracking, and the domain has just told you nothing. Six consonants. Zero vowels. No company name, no product name, nothing a search engine explains in one line. The sender's logo sits at the top of the message, but the host under the button belongs to somebody else.
That gap between the brand you recognise and the host you actually contact is the whole mechanism. So we stopped guessing and started probing.
Key Takeaways
- cmpgnr.com is the tracking and redirect domain behind Campaigner, an email marketing platform whose own site names J2 Global Canada, Inc., a Ziff Davis company, as the trademark holder.
- The domain was registered on 4 October 2006 through CSC Corporate Domains, Inc., a registrar used by large brand owners rather than individual buyers.
- Its TLS certificate covers both cmpgnr.com and *.cmpgnr.com, and trk.cmpgnr.com, trk2.cmpgnr.com and click.cmpgnr.com all resolve and answer today.
- trk2.cmpgnr.com and click.cmpgnr.com both point at an AWS load balancer in the ca-central-1 region, matching the Canadian entity named in Campaigner's trademark notice.
- Campaigner's published privacy policy states that its services "do not recognize browser do-not-track signals."
Every claim above came from a request we made ourselves. Where we could not confirm something, this article says so.
What Is cmpgnr.com?
cmpgnr.com is the domain Campaigner uses to carry tracking and redirect traffic for the marketing email its customers send. Nothing in the name says that. The evidence does.
Request the root over HTTPS and you get an HTTP/2 200 with 4,367 bytes of HTML titled Campaigner® Email Marketing Software. It is not a homepage but a fallback for people who arrived by mistake: "Campaigner® is an email service provider, and email sent from [host] comes from our subscribers." The footer closes it out: "© 2025 Ziff Davis. All rights reserved. Campaigner® is a trademark of Ziff Davis and its affiliates." The domain does identify itself. Just only after you have already clicked.
The response headers say more than the page. Traffic passes through an Istio service mesh (server: istio-envoy, plus an x-envoy-upstream-service-time header) in front of a long lived .NET application that sets an ASP.NET_SessionId cookie with HttpOnly; SameSite=Lax. The header that matters most is cache-control: private, which forbids any shared proxy from caching the response. For a tracking host that is not an oversight, it is the design: a cached response never reaches the origin, and a request that never reaches the origin never becomes a row in a report. It is the same infrastructure reading we use to detect email tracking pixels in Gmail.
Registration adds ownership signal: created 4 October 2006, registrar CSC Corporate Domains, Inc., Amazon Route 53 nameservers. CSC is a corporate brand registrar; nobody ends up there buying a domain on a whim. The registrant organisation is redacted in public whois, so ownership comes from two footers instead, both first hand. cmpgnr.com credits Ziff Davis. campaigner.com reads "© 2004 – 2026 J2 Global Canada, Inc., a Ziff Davis company."
One detail nobody else seems to have connected: trk2.cmpgnr.com and click.cmpgnr.com are CNAMEs to an AWS Application Load Balancer in ca-central-1, Amazon's Canadian region. The corporate paperwork says Canada, and the packets agree with the paperwork.
What Does Campaigner Email Tracking Actually See?
Any platform that reports opens and clicks learns the same four things from your inbox: your IP address, your user agent, the timestamp, and which recipient the request belongs to. Campaigner is not unusual here. The mechanics are the industry standard ones.
An open pixel is a remote image reference in the message body, typically a transparent 1x1 GIF, with a unique identifier per recipient baked into its URL. Your client fetches it, and the server writes down what arrived:
- IP address resolves to a coarse location and a network operator.
- User agent names your device, operating system and often your mail client.
- Timestamp shows when you were awake, at your desk, or checking mail on a Sunday.
- Recipient identifier turns all of that from anonymous traffic into a row with your name on it.
Be precise about what an "open" is: an inference, not an observation. The server knows an image was fetched. It does not know a human read anything. Apple's Mail Privacy Protection widens that gap enormously by downloading remote content in the background when a message arrives rather than when you view it, and by routing the fetch so the sender never sees your address. Every prefetch lands in the report as an open. Anyone reading a Campaigner open rate as a measure of human attention is reading a number padded with messages nobody looked at.
Click tracking is harder to dodge. The platform rewrites every link so the visible href points at its own host, carrying an identifier plus the real destination. You click, the tracker logs the hit, and only then redirects you onward. Some platforms also set a cookie at that hop so activity on the landing site attributes back to the email. We did not capture a live Campaigner click URL, so we will not invent its parameter or cookie names. The shape of the exchange is what matters, and we break it down in email open tracking vs click tracking. Campaigner's own privacy policy is candid about the category: "Cookie, Pixels and Other Trackers may also collect Personal Data about online behavior."
Why Is the Domain Just Consonants?
Because a domain you cannot read is a domain you cannot object to. Strip the vowels out of "campaigner" and you get a host that is short, unmemorable and functionally anonymous to the person hovering over it.
That buys two things at once. Recognition disappears, so the brand in the email keeps the credit while a third party keeps the data. And hand written filter rules fail: a recipient who blocks "campaigner" catches nothing, because the vendor name never appears.
The certificate shows how far the pattern scales. Subject CN=cmpgnr.com, with subject alternative names cmpgnr.com and *.cmpgnr.com. A wildcard means new per customer subdomains can be issued without touching the certificate. In practice trk, trk2 and click are all live right now; img.cmpgnr.com does not resolve, so the wildcard is capacity rather than proof that every name exists.
The fallback page gives the game away. It ships a tiny script, getVARS(), whose only job is to write window.location.host into that sentence about email service providers. The apology is built to be served from whatever hostname you arrived on. You do not write a page that way for one domain. You write it that way for a family of them.
This is the second vowel stripped tracking domain from the same corporate family we have taken apart. iContact runs on icptrack.com, registered in 2004; Campaigner runs on cmpgnr.com, registered in 2006. Two products, two unreadable hosts, one parent. If you read how iContact tracking works and how to block it, none of this will surprise you, and the same defences apply.
One caveat, stated plainly. Many platforms let a sender CNAME their own subdomain at the tracker, so the status bar shows email.somebrand.com and the vendor vanishes completely. We are not asserting Campaigner offers this: its knowledge base renders entirely through JavaScript, and Campaigner does not publicly document custom tracking domains, defaults or reporting fields on any page we could fetch.
How Do You Block Campaigner Email Tracking in Gmail?
Turn off automatic image loading in Gmail, then treat every link in a marketing email as a redirect until you have read where it goes. Those two habits kill most of the signal.
- Stop images loading by themselves. Open Gmail Settings, then See all settings, then General. Under Images, choose Ask before displaying external images and save. No fetch, no open, no row.
- Know what Gmail's proxy does and does not do. Google serves remote images through its own servers, so the tracker records a Google address, not yours. Your location stays hidden, but the fetch still happens and still carries the identifier that names you. "Gmail already protects me" is half true, and the wrong half.
- Hover before you click. If the host is cmpgnr.com and not the brand that emailed you, the click is written down before you arrive anywhere.
- Resolve links before sharing them. Paste the rewrite into the address bar, let it redirect, then copy the final destination. Forwarding the raw rewrite hands the sender an attribution row for everyone you sent it to.
- Use a blocker rather than living with images off forever. A filter that drops tracking requests per message beats a blanket setting you will get tired of. We compare the options in how to block email tracking in Gmail.
Campaigner vs Other Trackers: What Blockers Actually Stop
No extension stops tracking at the sender's end. They all work the same way, by refusing to make the request the tracker is waiting for. The differences are coverage and where they run.
- Ugly Email flags messages containing known trackers with an eye icon in the Gmail list before you open them. Strong at labelling, bounded by its list.
- PixelBlock blocks pixel loads in Gmail and marks where one was found. Narrow and focused, and it does nothing about rewritten links.
- Trocker is open source, marks trackers, and reveals the true destination behind a rewritten link, exactly the problem a host like cmpgnr.com creates.
- Proton Mail blocks remote content by default and proxies images, but it is a mailbox rather than a Gmail add on, so adopting it means leaving Gmail.
- HEY screens senders and strips trackers server side before the message reaches you. Also a different mailbox, also a full migration.
Gblock sits in the first group: it runs inside Gmail, blocks remote tracking content before it loads, strips tracking rewrites out of links, and updates its blocklist automatically so you never maintain a list of unreadable domains by hand. To be straight with you, we have not published a verified test showing Gblock blocks cmpgnr.com specifically. What it blocks is the class of request cmpgnr.com depends on: a remote fetch carrying a per recipient identifier. For the wider field, see our comparison of email tracker Chrome extensions and how to block them.
What Senders Should Disclose
If you send marketing email through Campaigner, the pixel in your template is your exposure, not your vendor's. You are the controller; the platform processes on your instructions.
In the EU and UK that matters more than most senders assume. The EDPB's Guidelines 2/2023 on the technical scope of Article 5(3) of the ePrivacy Directive put a tracking pixel squarely in scope: it instructs the recipient's terminal equipment to send information back, landing it in the same consent conversation as cookies rather than a quiet legitimate interest corner. The UK regulator's guide to PECR covers the same ground for UK recipients.
US rules are looser on tracking and stricter on the exit. The FTC's CAN-SPAM compliance guide says nothing about open pixels, but it does require you to honour an unsubscribe request within 10 business days and include a valid postal address in every message. In California the CCPA treats an identifier linked to a person as personal information, and an email tracking identifier is precisely that. One line in Campaigner's policy deserves a compliance officer's attention: the services "do not recognize browser do-not-track signals." A recipient who set that signal expressed a preference the platform will not act on, and the disclosure burden lands on you.
The Domain Will Never Explain Itself
cmpgnr.com will keep telling you nothing, and that is the design. Registered since 2006, behind a wildcard certificate that can mint new subdomains at will, with one public page that is an apology written to be served from any hostname in the family.
The fix is not to memorise the domain. Vendors change hosts, senders point their own at the tracker, and the next unreadable six letter host is already registered somewhere. Change the default instead: stop your inbox making requests you did not ask for, and read where a link goes before you go there. Do that once and the name on the host stops mattering.