Is Kajabi Tracking Your Email? How to Block It

Kajabi email tracking is real, it is on, and you can reproduce it from a terminal in about ten seconds. The pixel does not live on kajabi.com or on the creator's website. It lives on email.mykajabi.com, where a plain GET request returns a 43 byte transparent GIF: the entire mechanism in one file. Underneath it is Mailgun.

Key Takeaways

• A GET request to https://email.mykajabi.com/o/abc123 on 21 August 2026 returned HTTP 200, image/gif and exactly 43 bytes: a 1x1 transparent tracking pixel.
• The domain mykajabi.com publishes v=spf1 include:mailgun.org ~all and the mail exchangers mxa.mailgun.org and mxb.mailgun.org, identifying Mailgun as the layer behind Kajabi email.
• Kajabi's help center states that "a hidden tracking pixel is included within this data which allows your email service providers (ESPs) to see that the email was opened."
• Kajabi's Email Link Report shows a creator "the name and email of each contact who viewed a link" plus the date and click count, and automations can tag you the moment an email is opened.
• Kajabi documents no setting that turns open or click tracking off, unlike Loops and Ghost, which both publish an account wide switch.

Does Kajabi Track When You Open an Email?

Yes, and Kajabi says so itself, just not on the page you would think to look at.

The Email Metrics Overview defines an open as a message "delivered and viewed by the recipient" and leaves out how the viewing gets detected. The admission sits in an article about Apple instead, where Kajabi's guide to the iOS 15 email privacy update says plainly: "A hidden tracking pixel is included within this data which allows your email service providers (ESPs) to see that the email was opened."

That absence is the story. Searching the help center in August 2026 turns up no documented control letting a creator disable open or link tracking. Ghost lets a publisher switch the whole analytics apparatus off with one toggle. If Kajabi ships an equivalent, it is not written down anywhere a customer can find it.

What Is email.mykajabi.com?

It is the host that serves Kajabi's open pixel and its click redirect, and it runs on Mailgun.

Start with DNS. On 21 August 2026 mykajabi.com published v=spf1 include:mailgun.org ~all, the mail exchangers mxa.mailgun.org and mxb.mailgun.org, and a DKIM key at smtp._domainkey.mykajabi.com: the footprint of a domain provisioned inside Mailgun, not merely relaying through it.

DNS only proves who sends, so here is the part that proves what is measured. Requesting https://email.mykajabi.com/o/abc123 returns HTTP 200, content type image/gif and a 43 byte body beginning GIF89a, handed over to a token that is obvious nonsense. The sibling path /c/abc123 returns HTTP 400 and the body Bad request, which is what a live click redirect does when a signature fails. /o/ for opens and /c/ for clicks are Mailgun's own tracking URL shapes, and Mailgun describes the mechanism as "tracking pixels and URL redirects to track every time a recipient opens a message". The control test settles it: the same path on a subdomain that does not exist returns a 9,415 byte error page from Kajabi's application.

One honest caveat. Creators can connect a custom email domain, and Kajabi's setup guide asks for "Three TXT records, Two MX records, One CNAME record" under a kjbm subdomain without publishing the values. That count matches Mailgun's pattern, where the single CNAME is the tracking domain, so those creators probably serve the pixel from their own branded host. We could not verify that target and will not invent it.

What Can the Creator Actually See?

Your name and address, attached to a date, in a report they can sort and act on in bulk.

Kajabi's Email Click Report documentation describes a link level report listing "the name and email of each contact who viewed a link, the date on which they clicked the link, and the number of clicks", and says a creator can tag or enroll those contacts straight from it. That is not an anonymous percentage. It is a list of people with your row in it.

Two limits are worth naming, because coverage of email tracking routinely overreaches here. Kajabi's published reports do not show the creator your device model, operating system or city. Kajabi's privacy policy does say Kajabi itself records "your IP address, the type of browser used, identity and type of device used" plus "geolocation, including precise and regional", and that where you are a creator's customer, "Kajabi only acts as a service provider or processor of your data". Your GDPR or CCPA request goes to the creator.

What Happens Automatically When You Open or Click?

You get sorted, without a human ever reading your name.

Kajabi's automation triggers include four events built directly on this data: a broadcast is opened, a link in a broadcast is clicked, a sequence email is opened, a link in a sequence email is clicked. Each can add a tag to your contact record or drop you into another sequence.

This is the part most people miss. A pixel sold as "measuring open rates" sounds like something that ends in a chart. In Kajabi it ends in a state change on your record: the image your mail client fetched becomes a tag, and the tag becomes the reason you get different email from everybody else on the list. The pattern runs from Mailgun's raw event pipeline upward; Kajabi just puts it one click from a creator with no technical background.

Does Apple Mail Privacy Protection Already Handle This?

Only on Apple Mail with the feature enabled, and it corrupts the data rather than withholding it.

Apple's legal notice on Mail Privacy Protection is blunt about the stakes: without it, senders "may learn when and how many times you opened their email, whether you forwarded the email, your Internet Protocol (IP) address, and other data that can be used to build a profile of your behavior and learn your location." Kajabi has told its own customers the resulting numbers are unreliable, writing that Apple Mail preloads images "including the tracking pixel, regardless of if the recipient actually opened the email or not", then pointing creators at clicks, the one metric Apple's prefetch does not fake.

None of it helps a Gmail user in a browser. Gmail proxies images through Google's servers, hiding your raw IP, but still fetches the pixel when the message renders. The open fires; your row appears. We covered the wider distortion in Apple Mail faking half of all email opens.

How Can You Check for Yourself?

Read the raw message. It takes under a minute and needs nothing installed.

• Open the original. In Gmail, open the message, click the three dot menu at its top right and choose "Show original". The full source loads in a new tab.
• Search for the host. Press Ctrl or Cmd plus F and search for mykajabi. An <img> tag on a /o/ path is the open pixel, usually at the very bottom of the HTML, since that is Mailgun's default placement. Every visible link appears as a /c/ URL on the same host, carrying the token that ties your click to you.
• Do not assume the domain. On a custom email domain the pixel host carries the creator's brand, so the path shape is the tell. Our walkthrough on detecting email tracking pixels in Gmail covers the general technique.

How Do You Block Kajabi Email Tracking in Gmail?

The open is an image request, the click is a redirect: two things to stop, and one no tool can reach.

• Stop the pixel before it is requested. Gblock removes tracking pixels from messages inside Gmail before your browser fetches them, so the 43 byte GIF is never retrieved and no open event exists to tag you with. The email still renders.
• Turn off automatic image loading as a backstop. Gmail Settings, then General, then "Ask before displaying external images", documented on Google's image settings help page. Free and effective, and it blocks the images you wanted too, which is why most people abandon it.
• Deal with the links, not only the pixel. Blocking images does nothing about the /c/ redirect. Gblock strips tracking links so the destination opens directly; failing that, open the creator's site and navigate there yourself.
• Know the limit. Delivery, bounces, unsubscribes and spam complaints are recorded server side, and no blocker touches them. You remove the open and the click, not your presence on the list. Our guide to blocking email tracking in Gmail covers the rest.

How Does Gblock Compare to Ugly Email, PixelBlock and Trocker?

All of them block pixels. The differences are link handling, upkeep, and whether you have to leave Gmail, and we go through the field in our roundup of email tracker Chrome extensions and our blocker comparison.

Ugly Email is MIT licensed, flags tracked messages with an eye icon and blocks the detected pixel locally. Trocker is free and open source, works across several webmail providers, and is the only free option here that also marks tracked links. PixelBlock does straightforward pixel blocking, though its Manifest V2 lineage means you should confirm you are running a maintained build. Proton Mail and HEY block remote content at the client level: excellent protection that requires moving your email.

Gblock's differences are specific rather than sweeping. It stays inside Gmail, so nothing about your setup changes. It strips tracking links as well as pixels, which matters more than usual here, because clicks are the metric Kajabi tells creators to prefer. And its blocklist updates itself, so when a creator moves to a custom email domain and the pixel arrives from an unfamiliar hostname, you are not the one who has to notice.

The Honest Summary

Kajabi is not doing anything the rest of the email marketing industry does not do. It is doing it at the scale of a platform whose creators passed $10 billion in earnings from more than 150 million customers in August 2025, most of them running email out of the same box they run checkout from.

What separates Kajabi from the better behaved platforms is not the pixel but the silence around it. Loops publishes an account wide off switch. Ghost publishes one too. Kajabi publishes a page explaining that Apple broke open rates, concedes the pixel exists in the process, and documents no way to stop sending it. A row gets written because your mail client fetched a 43 byte image from a host you never agreed to contact. That fetch happens in your browser, and it is the only part of this arrangement you control.