How to Track Multiple Sender Addresses With One Account

Most tracking tools assume you send from one address. Almost nobody does.

Table of contents

A freelancer has a personal professional address and one per client project. A small company has a commercial address, a support address and a founder address. Anyone who has run a side project for more than a year has accumulated at least three.

Why single-mailbox tools become expensive

When a tracker binds itself to one mailbox, every extra address means another configuration, another dashboard, or another seat on the invoice. Sales platforms charge per user, and often count each connected mailbox as one.

The result is familiar: you track the address that generates the most revenue, and you fly blind on the others. Which is a shame, because the occasional quote sent from a side-project address is often the one where knowing matters most.

How mailcheck handles it

In mailcheck, the sender address is metadata on the tracked email, not a subscription unit. One account, any number of addresses.

Concretely:

• Install the extension once, in the browser where you work.
• Connect it to your mailcheck account.
• Open Gmail or Zoho Mail with any of your addresses, in any tab or profile.
• Enable tracking on the emails that matter.
• The history shows which address each message was sent from, alongside the recipient, the subject and the opens.

Gmail and Zoho Mail appear in the same list, so a company running its main domain on Zoho and a legacy address on Gmail sees everything in one place.

Browser profiles and workspaces

Many people separate clients with browser profiles, or with spaces in Arc. This is a good habit for authentication, and it usually confuses tracking tools, which see each profile as a fresh install.

The mailcheck extension stores its API key in the browser's synchronised storage, so an installation in a second profile signed into the same browser account picks it up. Where that is not the case, connecting a second profile takes one click and, since a recent fix, no longer disconnects the first one.

What this does not solve

Tracking multiple addresses on one account does not mean sharing data with a team. Everything sits under a single mailcheck account. If two people need their own history, they need their own accounts.

Nor does it merge identities: two addresses writing to the same recipient produce two separate tracked emails, as they should.

Aliases, delegated mailboxes and shared addresses

Not all extra addresses are the same, and they behave differently under tracking.

An alias is another address delivering to the same mailbox. When you send from an alias, the message leaves the same account, so tracking works exactly as it does on the main address. The sender address is simply recorded as the alias, which is what you want when reviewing history later.

A delegated mailbox, where you send on behalf of someone else, is more subtle. The message is composed in your browser, so the extension sees it and tracking applies, but the recorded sender is the mailbox you are writing from. If two people share that delegation, the history will not distinguish who pressed send.

A shared address, such as a support or contact address used by several people, raises the same question. Tracking tells you the address sent a message and that it was opened, not which colleague wrote it. If that distinction matters, it needs to live in your own process rather than in the tracking data.

Keeping the history readable as it grows

Once several addresses report into one account, the history becomes a mixed stream. Three habits keep it usable:

• Track selectively. This is the main one. A history containing only messages that mattered stays readable indefinitely; one containing everything becomes noise within a month.
• Use the sender column. Filtering or sorting by sending address effectively separates your projects without any additional configuration.
• Export periodically. A CSV per quarter gives you a record outside the tool, which is a reasonable habit for anything you might need later.

What happens when you add a browser or a machine

Working from a laptop and a desktop, or across two browsers, used to be the classic way to break a tracking setup: connecting the second device would invalidate the first, quietly.

That specific failure is fixed in mailcheck. A key that has already been used is protected, so connecting a new browser adds an installation rather than replacing one. Both keep working, both report into the same history, and you can see in your dashboard which keys exist and when each was last used.

If a device stops recording, the extension now says so explicitly rather than reporting a generic connection error, which was the previous behaviour and misled people into blaming the network.

When one account is not the right answer

Everything above assumes one person with several addresses. If two people need to track their own messages, they need separate accounts, and that is the correct design rather than a limitation.

Sharing one account between colleagues means sharing the history, the quota and the credentials, which is uncomfortable on all three counts. If your situation is genuinely a team one, the question to ask is not how to stretch a personal tool, but whether the visibility you need belongs in a CRM instead.

Conclusion

If you send professional email from more than one address, the question to ask a tracking tool is not what it costs per month, but what it costs when you add the third address. With mailcheck the answer is nothing, which removes the main reason people end up tracking only half of what they send.

Frequently asked questions

Does each sender address cost extra?

No. In mailcheck the sender address is metadata on the tracked email, not a subscription unit, so one account covers any number of addresses across Gmail and Zoho Mail.

Can two people share one account?

Technically yes, practically no. They would share the history, the quota and the credentials. If two people need their own tracking, they need their own accounts.

Does connecting a second browser break the first?

Not any more. A key that has been used is protected, so a new browser adds an installation instead of replacing one, and both keep reporting into the same history.

All articles →