Tracking · SMTP

Track your SMTP emails

Add a few headers to the emails you already send. You get opens, clicks, a one-click unsubscribe and every recipient saved as a contact — nothing to create first.

Same server, same login

The headers

All optional. Add them to the message like any other header — use only the ones you need.

X-Sendcorex-Trackheader

The name these emails are grouped under in Analytics.

  • Created on the first email — nothing to set up before.
  • Same name, same track: case and extra spaces don't matter ("Welcome Email" = "welcome email").
  • Up to 100 characters. Use one per kind of email, like "Welcome" or "Invoice".
X-Sendcorex-Track: Weekly Newsletter
X-Sendcorex-Track-Opensheader · yes/no

Count who opened the email.

  • Adds an invisible pixel to the HTML part.
  • Automatic opens (Apple Mail privacy, security scanners) are counted apart — they never inflate your open rate.
  • Without a track, the open is still saved on the contact, just not grouped in Analytics.
X-Sendcorex-Track-Opens: true
X-Sendcorex-Track-Clicksheader · yes/no

Count who clicked each link.

  • Links in the body pass through Sendcorex and redirect instantly to your page.
  • You see the top links and which contacts clicked them.
X-Sendcorex-Track-Clicks: true
X-Sendcorex-Unsubscribeheader · yes/no

Use the Sendcorex unsubscribe link.

  • Put [unsubscribe] in the body (or [unsubscribe_url], [unsub_url], [opt_out_url]). Each recipient gets a personal link.
  • Also sets List-Unsubscribe and one-click for Gmail and Yahoo, replacing any List-Unsubscribe you set.
  • Whoever unsubscribes stops getting emails from your whole account: campaigns, API and SMTP.
  • true without the placeholder is rejected with 554 and nothing is sent.
X-Sendcorex-Unsubscribe: true
X-Sendcorex-Contact-Listheader

The contact list where recipients are saved.

  • Created if it doesn't exist yet. Without it, recipients go to "API Contacts".
  • Recipients are saved only when you use one of these headers. A plain email saves nothing.
  • Someone already in your contacts is updated, never duplicated.
X-Sendcorex-Contact-List: Newsletter

Example

A newsletter with everything on. Only the message part changes — keep your connection code as it is.

await transporter.sendMail({
  from: '"The Weekly" <news@yourdomain.com>',
  to: 'subscriber@example.com',
  subject: 'Issue #42',
  html: '<p>This week in tech...</p><a href="[unsubscribe]">Unsubscribe</a>',
  headers: {
    'X-Sendcorex-Track': 'Weekly Newsletter',
    'X-Sendcorex-Track-Opens': 'true',
    'X-Sendcorex-Track-Clicks': 'true',
    'X-Sendcorex-Unsubscribe': 'true',
    'X-Sendcorex-Contact-List': 'Newsletter',
  },
});

Where you see the results

Nothing to configure. The first email with a track already shows up in your dashboard.

Analytics

How many opened and clicked

Every track is a row in the Sends table, next to your campaigns. Open it for the full report: activity by hour, best time to send, providers, devices, countries and top links.

Open Analytics

Contacts

Every recipient, saved

Recipients are saved in the contact list you choose (or "API Contacts"). Each contact keeps its history: received, opened, clicked, bounced, unsubscribed.

Open Contacts

People

Who opened, who clicked

In Analytics, open your track and press "Who opened", "Who clicked" or "Unsubscribed". Your contacts open already filtered — export, tag or add them to a list.

See who opened

Server replies

What the server answers after DATA when tracking is on.

ReplyWhen
250 OK id=…Accepted. One ID per recipient, comma-separated — the same IDs you see in logs and webhooks.
554 5.6.0X-Sendcorex-Unsubscribe is true but the body has no [unsubscribe]. Nothing is sent — add it and send again.
451 4.3.0Unsubscribe is temporarily down. Temporary: your SMTP library retries on its own.

Good to know

Invisible to recipients

Every X-Sendcorex-* header is removed before the email goes out.

Any spelling works

Header names are not case-sensitive. Yes/no headers accept true, 1, yes or on (and false, 0, no, off).

Accents in names

Track and list names can be RFC 2047-encoded (=?UTF-8?B?…?=). Most libraries do it for you.

500 tracks per account

Past the limit the email still goes out, just without a track.

Legacy

The old [[Name]] tag

Can't add headers in your app? The tag in the body still works — it is the only option that needs no code change.

Anywhere in the body
<p>Welcome aboard!</p>
<p>[[CRM Welcome List]]</p>

What it does

The tag is removed from the email. "CRM Welcome List" becomes the track and the contact list, with opens and clicks on and unsubscribe off.

Mixing both

If you also send the new headers, they win: the tag only fills what you left out.

Deprecated

Accounts still using the tag get an email, at most once a week, asking to switch. It keeps working until then.

Old reference codes

A code like [[7CK-JDL-Y1L]] is now read as a track with that name. The old tracking endpoints were removed — everything lives in Analytics.