> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getswan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email tracking and deliverability

> What Swan tracks on sequence emails, how open and click rates are calculated, and what deliverability tooling Swan does not provide.

## What Swan tracks

Swan tracks two things on every sequence email: whether it was **opened** and whether a **link in it was clicked**. This tracking is always on for sequence emails — there's no per-sequence or per-email toggle to disable it.

You can see this engagement in three places:

* **[Outreach → Sequences](https://agent.getswan.com/outreach/sequences)** shows opened/clicked indicators on each enrolled contact, with timestamps on each sent email in the contact's message timeline (open a contact's row to see it). You can filter the list to just the contacts who opened or clicked using the Interactions filter, by the date their sequence-contact row was created (when they were added), and by any combination of senders and triggers.
* **[Outreach → Analytics](https://agent.getswan.com/outreach)** rolls engagement up by sender and trigger for sequence contacts created in the selected date range. Opens and clicks continue to count when they happen after that range ends — see [analytics](../workspace/analytics).
* **Asking Swan** — the agent can pull a sequence's full per-contact timeline: every step taken, what was sent, who opened or clicked what and when, replies, and what created the sequence.

## How open and click rates are calculated

The top-level rates count **distinct people** in the creation-date cohort: how many of the contacts emailed opened (or clicked) at least once by the time you view the report. One person opening five times is one open, so rates can't exceed 100%. The sender × trigger performance table counts sequence-contact rows instead, matching the rows shown when you click through to Sequences. Underneath, Swan still records every individual open and click event with its timestamp — and not every recorded open is a human one: corporate security scanners and some mail clients pre-fetch messages, which registers as an open. Treat opens as directional; clicks and replies are the stronger signals.

## What Swan does not do today

Swan's outreach sending is intentionally light on infrastructure it doesn't directly control. It currently does **not**:

* **Warm up mailboxes.** Swan sends from your existing connected inbox as-is; it doesn't run a warmup sequence to build sending reputation before outreach starts.
* **Detect or process bounces automatically.** Swan has no built-in bounce-handling pipeline — a bounce won't show up as a dedicated alert. If you have a [message received trigger](../triggers/message-received) — the personal reply trigger created when you connect a sender — its default instructions include classifying a reply as a bounce and acting on it (finding an alternate email and starting a new sequence). In practice, though, a typical automated bounce notification is sent from a `mailer-daemon@`-style address, and Swan filters those out before the trigger ever fires — the same filtering that keeps them from counting as a real reply.
* **Add unsubscribe links or maintain a suppression list.** There's no automatic unsubscribe footer or opt-out tracking built into outreach emails. If someone asks to stop hearing from you, exclude them (or their company) manually — see [tags, lists and exclusions](../data/tags-lists-and-exclusions).

## Practical guidance

Since Swan doesn't warm mailboxes or watch for bounces itself, deliverability is mostly a function of how you configure sending:

* Keep per-sender daily limits conservative, especially on newly connected inboxes — see [sending limits](sending-limits).
* Send from a domain that's already warmed up and has healthy SPF/DKIM/DMARC records rather than a brand-new domain.
* Treat opt-outs as a manual process: when a contact asks not to be contacted, exclude their contact or company record so no future sequence reaches them.

## Common questions

**Can Swan tell me which specific link someone clicked if my email has multiple links?**
No — click tracking is per-email (did they click something), not per-link, so you can't distinguish which of several links was clicked.

**Does Swan log sent sequence emails anywhere I can see them, like a sent folder?**
Sent messages are visible in the contact's timeline, opened from its row in [Outreach → Sequences](https://agent.getswan.com/outreach/sequences); check [executions and history](../workspace/executions-and-history) for where sequence activity is recorded.

**If a bounce email comes back, will it stop the sequence?**
No — automated bounce-style messages are filtered out as non-replies, so the sequence keeps going as if nothing came back. Watch the sender's inbox directly if you're worried about deliverability to a specific address.

**Should I use a separate sending domain to protect my main one?**
That's a reasonable practice generally, but it's a decision you make on your email provider side — Swan sends through whatever inbox you connect and doesn't manage domains or subdomains for you.

**Does open/click tracking affect my sender's reputation?**
Tracking pixels and link wrapping are standard practice and shouldn't meaningfully affect deliverability on their own, but they're not something you can turn off per sequence today.