Email Tracking for Zoho Mail on a Custom Domain

Almost nobody chooses Zoho Mail for a personal address. People choose it to run business email on their own domain, cheaply, without handing everything to Google. That changes what tracking needs to handle.

Table of contents

If you send from hello@yourcompany.com through Zoho, the questions you have about open tracking are not the same as a Gmail user's. This guide answers them in order.

Why Zoho attracts custom domains

Zoho Mail became popular with small businesses, freelancers and agencies for a straightforward reason: it lets you run professional email on your own domain at a fraction of what the alternatives cost, with a web interface that does not feel like a compromise.

The consequence is a user base that skews heavily towards business sending. Quotes, proposals, client updates, invoices, hiring. Exactly the messages where knowing whether the email was opened changes what you do next.

And yet the tracking ecosystem around Zoho is thin. Most tools were built for Gmail and never went further. That gap is the reason mailcheck supports both.

Does the domain change anything for tracking?

No, and this is the part that reassures most people.

Open tracking works on the recipient's side. A small image is embedded in the message, and when the recipient's mail client loads it, the open is recorded. None of that depends on which domain you send from, whether it is a Zoho subdomain or your own company domain.

There is nothing to configure in your DNS for tracking to function. No record to add, no domain to verify, no authentication step. If your Zoho account sends mail today, tracking will work on it today.

What the custom domain does change is the shape of your setup, because businesses rarely have just one address.

The real complication is multiple addresses

A typical custom domain on Zoho does not look like one mailbox. It looks like this:

• your own name, for direct client conversation
• a shared address like hello@ or contact@, for inbound
• a billing or invoicing address
• sometimes a second domain entirely, for a side project or a rebrand in progress

The question that follows is predictable: does tracking need a separate account, or a separate subscription, for each of those?

It does not. mailcheck attaches to your browser session rather than to a single address, so every address you send from in the Zoho web interface is tracked under one account. We covered the mechanics of this in tracking multiple sender addresses with one account, and it applies identically to a custom domain.

Setting it up on a custom domain

The full procedure, with nothing domain-specific in it:

1. Install the mailcheck extension in Chrome, Brave, Arc or any Chromium browser.
2. Open the extension and connect your mailcheck account. Google sign-in works even though you use Zoho, it identifies you rather than reading your mail.
3. Open the Zoho Mail web interface and compose a message.
4. Look at the compose toolbar. The tracking toggle reads Tracking ON, because tracking is enabled by default for new emails.
5. Send normally. The message appears in your tracked list straight away.

That is the whole setup. The step people expect and never find is the DNS one, because it does not exist.

What about aliases and send-as?

Zoho lets you send as an alias, and small teams use this constantly: one mailbox, several public faces.

Because tracking is applied at the moment you compose in the browser, the alias you pick in the From field does not affect whether the email is tracked. It is recorded either way, and the sending address is stored alongside it so your history stays readable when you look back at it weeks later.

This matters more than it sounds. A tracked email you cannot attribute to the right address is close to useless when you are trying to reconstruct a client conversation.

Five things that actually break tracking

Since the domain is not the problem, here is what genuinely is:

1. Sending from the Zoho mobile app. The extension lives in the desktop browser. Mobile sends are not tracked.
2. Sending from a desktop mail client. Same reason. Outlook or Thunderbird connected to Zoho over IMAP bypasses the browser entirely.
3. The recipient blocking images. No image load, no open, even though the email was read.
4. A corporate gateway stripping remote images. Common in large enterprises and in some regulated industries.
5. A privacy proxy pre-loading images. The opposite failure: an open recorded when nobody read anything.

Notice that four of the five are about the recipient or the device, not about you. That is the nature of open tracking, and it is why it should be read as a signal rather than a measurement.

Tracking and deliverability are not the same problem

Custom domain owners often arrive with the two questions tangled together, so it is worth separating them.

Tracking tells you what happened after an email arrived. Deliverability decides whether it arrived at all. A perfectly tracked email that landed in spam will simply never register an open, and you will read that silence as disinterest when it was a routing failure.

If your domain is new, or you have never configured SPF, DKIM and DMARC, do that before drawing conclusions from tracking data. Zoho documents the records for its own service, and the effort pays for itself. Our guide on why emails bounce and what it costs you covers the adjacent failure mode.

Get delivery right first. Then tracking tells you something true.

A setup that holds up for a small team

A few habits that keep this workable past the first month:

• Track selectively. Quotes, proposals and follow-ups. Not internal threads.
• Keep one account per person. Tracking follows the browser session, so shared logins produce a history nobody can read.
• Check the dashboard weekly rather than hourly. Patterns across days say more than a single open.
• Write down what an open means to you. A team that agrees "two opens plus three days equals follow up" behaves consistently. One that improvises does not.

Conclusion

Running Zoho Mail on a custom domain changes nothing about how open tracking works. There is no DNS record to add and no domain to verify, because the mechanism lives on the recipient's side.

What a custom domain does bring is several sending addresses, aliases, and a team, and those are handled under a single account. The things that genuinely break tracking are mobile sends, desktop mail clients, and what the recipient's mail system does with images.

Fix deliverability first, track the emails that carry real decisions, and Zoho stops being the platform nobody built tools for.

Frequently asked questions

Do I need to add a DNS record to track emails from my own domain?

No. Open tracking works through an image loaded by the recipient, so nothing needs to be configured on your domain.

Can I track several addresses on the same domain?

Yes. Tracking follows your browser session rather than a single address, so every address you send from in the Zoho web interface is covered by one account.

Does sending as an alias break tracking?

No. The alias you choose in the From field does not change anything, and the sending address is stored with each tracked email.

Are emails sent from the Zoho mobile app tracked?

No. The extension runs in a desktop browser, so mobile and desktop mail clients bypass it.

Will tracking hurt my deliverability?

Tracking a small number of one-to-one business emails is not what puts mail in spam. Missing authentication records and poor list hygiene are far more likely causes.

All articles