Tracking

Kata measures replies, clicks, unsubscribes and conversions. It does not track opens.

Replies

Every reply is sorted into one of six kinds:

Kind	Effect
`interested`	Counts as a success for the angle. The lead shows in leads to call. The sequence stops.
`not_interested`	The sequence stops.
`unsubscribe`	The sequence stops and the address goes on the suppression list.
`ooo`	Out of office. Logged; the sequence goes on. When the reply gives a return date (in any language), the next email waits until the day after, 30 days at most.
`wrong_person`	Not the right person (someone else handles it, has left the company). The sequence stops; the lead gets `wrong_person` and, when the reply names one, `referral` in its data. The agent lists them in `status` to find the right contact.
`other`	The sequence stops.

The Inbox

Every reply lands in the Inbox, one row per lead, newest first: its kind, the lead, the campaign, the mailbox that got it, the first line, and a dot while you have not opened it. Filter by kind, campaign or mailbox, or search. A row opens the lead with the whole thread and the Reply box. The AI sorts each reply; click its tag to correct it. A new tag never restarts a sequence: any kind except ooo stops it, and moving away from unsubscribe takes the address off the suppression list. The agent reads the same list with list_inbox and corrects a tag with set_reply_status.

Answering a reply

Open the lead (Inbox, CRM or Canvas): the Reply box drafts an answer with the agent, then sends it from the same mailbox, in the same thread. The agent does the same with reply. The answer shows on the lead's timeline. Zapmail mailboxes send it with their thread ids, but their replies do not come back to Kata yet.

Clicks need a link domain

Clicks are counted only on the sending domain's own link domain: go.<your domain> (or get, try, info when go is taken). There is no shared tracking domain.

setup_link_domain sets it up when the domain is in your Cloudflare (token in Integrations with DNS: Edit). It is active a few minutes later, once the certificate is issued (check_link_domains).

Without a link domain, {{link}} is the campaign link itself. Clicks are not counted, but the kata token is still added, so replies and the postback still measure the campaign.

Bot clicks

Mail security scanners (Outlook Safe Links, Mimecast, Proofpoint…) open every link before the person does. Kata logs those clicks but does not count them. A later human click still counts.

Why no opens

Kata sends plain text with no tracking pixel. Pixels hurt deliverability, and Apple Mail fakes opens anyway.

Kata pixel (kata.js): what leads do on your site

The Kata pixel is one script on your site. It sees the leads who came from a Kata email, and tells Kata the pages they visit and their conversions.

html

<script async src="https://api.katasend.com/kata.js"></script>

Put it before </head> on every page. The snippet is also in Integrations › Pixel, with copy buttons, and an Install with AI prompt: paste it into your coding agent (Claude Code, Cursor, Lovable…) and it adds the pixel, the kata('convert') calls on your success pages and the payment postback, with your own URLs.

01
It keeps the token.
Every {{link}} adds kata=<token> to your URL. The script saves it in a first-party cookie and localStorage, for 90 days.
02
It sends page views.
The path only (no query string, no title), once per page and 30 minutes. Each one shows on the lead's timeline: “Visited /pricing”.
03
It reports conversions.
Call kata('convert', {value: 49, event: 'purchase'}). It works like the postback: the lead is converted, its sequence stops, the value adds up. Other fields are saved on the lead. Once per event name and lead.

html

<script>window.kata = window.kata || function () { (kata.q = kata.q || []).push(arguments); };</script>
<script async src="https://api.katasend.com/kata.js"></script>
<script>kata('convert', { value: 49, event: 'purchase', plan: 'pro' });</script>

Privacy: visitors who never came from a Kata email send nothing. No fingerprint, no third-party cookie. Unknown tokens are ignored, and one lead sends 60 events an hour at most. A browser call can be faked by anyone who has the link: for payments, prefer the postback from your backend.

Unsubscribe

Every email carries a List-Unsubscribe header, so Gmail and Yahoo show their unsubscribe button. With a link domain it is a one-click link; without one it is a mailto. Opening the link only shows a button: the unsubscribe happens on the click, so scanners that open every link unsubscribe nobody.