EMAIL TRACKING & DELIVERY

Monitor email opens, clicks, and delivery status. Manage bounce handling and suppression lists to protect your sender reputation.

Tracking

## Email Tracking

📊 ParsaLink tracks the following events for every email sent through the platform:

Event	Description
Sent	Email was accepted by the sending server
Delivered	Confirmed delivery to the recipient's inbox
Opened	Recipient opened the email (tracked via a 1×1 pixel)
Clicked	Recipient clicked a tracked link in the email
Bounced	Email could not be delivered (soft or hard bounce)
Unsubscribed	Recipient clicked the unsubscribe link
Spam Complaint	Recipient marked the email as spam

✓ All events are visible on the contact or lead's Activity Timeline in real time.

***

Delivery

## Viewing Delivery Status

📬 From the email sending history page (Email → Sent), you can see every email sent by your team with its current delivery status. Filter by:

• Date range • Sent by (team member) • Status (opened, bounced, etc.) • Template used

🔍 Click any email row to see the full delivery log including timestamps for each tracking event.

***

Bounces

## Bounce Handling ### Hard Bounces

⚠️ A hard bounce means the email address is permanently invalid — the domain doesn't exist, the mailbox doesn't exist, or the address has been permanently blocked. ParsaLink automatically:

1 Records the bounce on the contact's activity timeline.

2 Marks the contact's email as invalid.

3 Adds the email address to the suppression list to prevent future sends.

⚠️ Hard bounces are a serious deliverability signal. A high bounce rate (above 2%) will damage your sender reputation with ISPs and may get your sending domain or IP flagged. Keep your contact lists clean.

### Soft Bounces

🔄 A soft bounce indicates a temporary delivery failure — the recipient's mailbox is full, the server was temporarily unavailable, or the message was too large. ParsaLink retries soft bounces automatically. After 3 failed retries, the email is marked as permanently bounced.

***

Suppression

## Suppression Lists

🚫 The suppression list is a set of email addresses that ParsaLink will never send to, regardless of what automations or bulk sends are triggered.

➕ Addresses are automatically added to the suppression list when:

• A hard bounce occurs • The recipient clicks an unsubscribe link • A spam complaint is received

**Managing the suppression list:**

⚙️ Go to Email → Suppression List to view all suppressed addresses. You can:

✓ Search for a specific email address to check if it's suppressed.

✓ Remove an address from the suppression list if it was added in error (e.g., a temporary server issue caused a false hard bounce). Use caution — re-adding a truly invalid address will just bounce again.

✓ Add manually — Add a specific email address to suppress proactively (e.g., a competitor or internal address).

***

Unsubscribe

## Unsubscribe Handling

📧 Any email template that includes {'{{unsubscribeLink}}'} provides recipients with a one-click opt-out. When someone unsubscribes:

1 Their email is added to the suppression list.

2 The contact's emailOptOut field is set to true in the CRM.

3 A note is added to their activity timeline recording the opt-out event.

📌 ParsaLink does not automatically add unsubscribe links to transactional or individual emails. You control where the unsubscribe link appears. For marketing and bulk emails, always include it — it's a legal requirement in most jurisdictions (CAN-SPAM, GDPR, CASL).

***

Spam

## Spam Complaint Handling

🚨 If a recipient marks your email as spam (via Gmail or Outlook's "Report Spam" button), ParsaLink receives a feedback loop notification (when configured with SES or compatible SMTP providers). The recipient is automatically added to the suppression list and their emailOptOut field is set to true.

⚠️ Spam complaint rates above 0.1% are treated seriously by email providers. If you see a rising complaint rate:

✓ Review your email content for spam trigger words.

✓ Ensure your recipient list is opted in and engaged.

✓ Make unsubscribe links easy to find and use.

***

Tracking Pixel

## Tracking Pixel and Link Tracking

🖼️ Open tracking uses an invisible 1×1 pixel image embedded in HTML emails. When the recipient's email client loads the image, an open event is recorded.

🔗 Link tracking replaces your URLs with ParsaLink tracking URLs. When a recipient clicks, ParsaLink records the click and redirects them to the original URL within milliseconds.

ℹ️ Some email clients (including Apple Mail with Mail Privacy Protection enabled) pre-fetch tracking pixels, which can inflate open rates. Click tracking is generally more reliable as a signal of genuine engagement.

*** ## Per-Template Analytics Every email template carries a dedicated analytics page at **CRM → Emails → Analytics → \[Template]**. It rolls up sends from that template across every contact and surfaces: * **Stats cards** — sent / delivered / opened / clicked / bounced / complained / replied, with rates * **Time-series chart** — opens, clicks, and replies plotted by day across the lookback window * **Recent Sends list** — the last 25 sends with per-recipient delivery state * **Bounced Recipients** + **Complained Recipients** — quickly find who flagged the template * **Health Badge** — a single-glance summary (Healthy / At-Risk / Damaging) computed from bounce + complaint rates against your sender reputation ### AI Review Click **Get AI Review** on any template's analytics page. ParsaLink runs an LLM analysis over the template body, the actual recipient interactions, and the bounce / complaint data, then returns: * What's likely working (subject line, CTA placement, length, tone) * What's likely costing you opens or clicks * Concrete rewrite suggestions you can copy into a new version The review is grounded in the data you actually have — not generic email-marketing advice — so it's useful even when the template has only a few dozen sends. *** ## The SES Event Pipeline (Workspaces on SES) Workspaces sending through Amazon SES get a richer feed than basic SMTP can offer. When SES is configured with a Configuration Set that publishes to SNS, ParsaLink ingests: 1. **Delivery** events → the email reached the recipient's mail server 2. **Bounce** events (hard / soft / transient) → automatically flips affected contacts onto the suppression list for hard bounces 3. **Complaint** events → suppressed immediately + flagged in the per-template analytics 4. **Open** events → tracking pixel rendered in the recipient's client 5. **Click** events → recipient clicked a tracked link Set up is `Settings → Workspace Email → Advanced → Configuration Set`. The events feed both the per-template analytics page and the contact's activity timeline, so you can drill in from either angle. *** ## Inbound Events from `parsa-assistant@` Replies routed through your workspace's `parsa-assistant@` address are captured by SES → SNS → ParsaLink. Each inbound email: * Logs to the matched contact's timeline * Triggers any active `email_received` automation rules * Falls back to alerting the contact's assigned user if no automation matches For larger inbound mail (over 150 KB), SES first stages the raw message in an S3 bucket; ParsaLink fetches the full body from there, processes it, then discards the S3 object. Smaller messages ride entirely in the SNS notification.