Email engagement tracking for sales — open tracking, click tracking, attachment views, real-time notifications, follow-up timing, and engagement analytics. Use when you can't tell if prospects are opening emails, open data looks inflated or unreliable (Apple MPP, pixel blocking), you don't know when to follow up based on engagement, tracking isn't set up yet and you need to pick a tool, or click/attachment tracking isn't working as expected. For Yesware-specific help, use /sales-yesware. Do NOT use for email deliverability (use /sales-deliverability), cadence design (use /sales-cadence), buying intent signals beyond email (use /sales-intent), SendGrid-specific config (use /sales-sendgrid), Postmark-specific config (use /sales-postmark), Customer.io-specific config (use /sales-customerio), Mailgun-specific config (use /sales-mailgun), Klaviyo-specific config (use /sales-klaviyo), or ActiveCampaign-specific config (use /sales-activecampaign).
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Email engagement tracking for sales — open tracking, click tracking, attachment views, real-time notifications, follow-up timing, and engagement analytics. Use when you can't tell if prospects are opening emails, open data looks inflated or unreliable (Apple MPP, pixel blocking), you don't know when to follow up based on engagement, tracking isn't set up yet and you need to pick a tool, or click/attachment tracking isn't working as expected. For Yesware-specific help, use /sales-yesware. Do NOT use for email deliverability (use /sales-deliverability), cadence design (use /sales-cadence), buying intent signals beyond email (use /sales-intent), SendGrid-specific config (use /sales-sendgrid), Postmark-specific config (use /sales-postmark), Customer.io-specific config (use /sales-customerio), Mailgun-specific config (use /sales-mailgun), Klaviyo-specific config (use /sales-klaviyo), or ActiveCampaign-specific config (use /sales-activecampaign).
Help the user set up, interpret, and act on email tracking data — from understanding how tracking works through interpreting engagement signals and timing follow-ups. This skill is tool-agnostic and applies to any email tracking platform (Yesware, Salesloft, Apollo, HubSpot Sales, Mailshake, Mixmax), with platform-specific sections where relevant.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
What's your tracking goal?
A) Setting up email tracking for the first time
B) Understanding open/click data and what it means
C) Timing follow-ups based on engagement signals
D) Dealing with inaccurate tracking data (Apple MPP, pixel blocking)
E) Choosing a tracking tool
F) Tracking attachments and documents
G) Something else
What tools do you use?
A) Yesware
B) Salesloft
C) Apollo
D) Mailshake
E) HubSpot Sales
F) Mixmax
G) Mailtrack / other lightweight tracker
H) None yet
What email client?
A) Gmail
B) Outlook
C) Both
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
Step 2 — How email tracking works
Core tracking mechanisms
Open tracking: Invisible 1x1 pixel embedded in email. When email is opened, pixel loads from tracking server → open event recorded → notification sent. Works for HTML emails only — plain text emails cannot be tracked.
Click tracking: Links rewritten to pass through tracking server. When clicked → redirect to destination + click event recorded → notification. More reliable than open tracking because it requires deliberate action.
Attachment tracking: Attachments hosted as tracked links (or via DocSend/similar). When opened → view event recorded → notification. Often includes page-by-page analytics showing which slides/pages the prospect spent time on.
Real-time notifications: Desktop/mobile push when prospect engages — opens, clicks, attachment views. Enables immediate follow-up when a prospect is actively engaged.
Thread tracking: Track entire conversation thread, not just initial send. See when prospects re-open earlier messages — a signal they're reviewing the conversation before responding.
How tracking signals map to follow-up actions
Signal
What it means
Recommended action
Timing
Single open
Glanced at it
Wait — could be automated preview
Don't act yet
Multiple opens (3+)
Actively reviewing
Call or send follow-up
Within 1-2 hours
Link click
Researching your offering
Call immediately — hot lead
Within 30 minutes
Attachment view
Deep interest, evaluating
Call or send relevant case study
Within 1 hour
Forward to colleague
Sharing internally
Multi-thread — reach out to the forwardee
Within 24 hours
No open after 48hr
Didn't see it or ignored
Re-send with new subject line
After 48-72 hours
Opened but no reply after 3 days
Interested but not compelled
Follow up with new value angle
Day 3-4
Priority framework
Rank engagement signals from strongest to weakest:
Reply (99% reliable) — they responded, follow up immediately
Link click (85-90% reliable) — they took action, follow up within 30 minutes
Attachment view (85-90% reliable) — deep engagement, follow up within 1 hour
Multiple opens (60-70% reliable) — repeated interest, follow up within 1-2 hours
Forward (high reliability when detected) — internal discussion happening, multi-thread within 24 hours
Single open (low reliability) — don't act on this alone
Critical caveat — always factor in tracking data inflation. Apple MPP inflates open rates (pre-fetches pixels even when the email is never read), and bot clicks from corporate email security tools (Barracuda, Mimecast, Proofpoint, Microsoft Defender) inflate click-through rates by auto-clicking every link to scan for malware. Bot clicks happen within 1-2 seconds of delivery from data center IPs and hit all links simultaneously — human clicks are delayed and selective. Before acting on any open or click signal, consider whether it could be fake. The only truly reliable engagement signals are replies and meetings booked. See Step 3 for full details on identifying and filtering these false positives.
Step 3 — Privacy and accuracy challenges
The two biggest accuracy threats to email tracking data are Apple Mail Privacy Protection (MPP) and bot clicks from security scanners. MPP inflates open rates; bot clicks inflate click rates. Together they can make both of your primary engagement metrics unreliable. Always warn about both when interpreting tracking data, and default to reply rate as the most trustworthy signal.
Apple Mail Privacy Protection (MPP)
Launched with iOS 15 / macOS Monterey (September 2021):
Pre-fetches all email content (including tracking pixels) regardless of whether the user actually opens the email
Result: 100% "open rate" for Apple Mail users — the data is meaningless
Prevalence: ~50-60% of consumer email opens, ~30-40% of B2B email opens
Workaround: Don't rely on open rate as a primary metric. Focus on click-through rate and reply rate instead. If your open rate is suspiciously high (above 80%), Apple MPP is almost certainly the cause.
Bot clicks from corporate email security
Security tools like Barracuda, Mimecast, Proofpoint, and Microsoft Defender pre-scan every link in inbound emails to check for malware. This generates fake click events that inflate your click-through rates with false positives. The problem is especially severe when selling to enterprise or security-conscious organizations, where nearly 100% of emails pass through link scanners.
How to spot them: Bot clicks typically fire within 1-2 seconds of email delivery, come from the same IP block, and hit every link in the email simultaneously. Human clicks happen minutes to hours later with varied timing.
Mitigation: Enable bot click filtering in your tracking tool (most modern tools support this). Use delayed redirect tracking if available. Set a minimum time threshold (e.g., ignore clicks within 5 seconds of delivery). For enterprise prospects, weight replies over clicks as your primary engagement signal — replies cannot be faked by security scanners.
Prevalence: Bot clicks can inflate click rates by 10-50% depending on how many of your prospects use corporate email security. If your click rate seems suspiciously high for cold outbound (above 15-20%), bot clicks are likely the cause.
Privacy-conscious users
Image blocking in email clients prevents pixel loading
~15-25% of B2B recipients block images by default
Workaround: Track replies and clicks (more reliable than opens). Accept that open tracking will always undercount by 15-25%.
Tracking accuracy benchmarks
Metric
Accuracy
Notes
Open tracking
~60-70%
Inflated by Apple MPP, deflated by image blocking
Click tracking
~85-90%
Some bot inflation from security scanners
Reply tracking
~99%
Most reliable signal — hard to fake
Attachment view tracking
~85-90%
Reliable when using tracked links (DocSend, Yesware attachments)
Step 4 — Platform-specific guidance
For platform-specific tracking setup and configuration (Yesware, Salesloft, Apollo, HubSpot Sales, Mailshake, Reply.io, Woodpecker, Seismic, Mixmax, SendGrid, Postmark, Customer.io, Mailgun, Klaviyo, ActiveCampaign, Veloxy, Cirrus Insight), see references/platforms.md.
Step 5 — Actionable guidance
Setting up tracking for the first time
Install the extension/integration for your chosen tool (browser extension for Gmail/Outlook, or platform integration)
Configure notification preferences — start with notifications for clicks and multiple opens only. Single-open notifications create noise.
Enable attachment tracking — always send documents through your tracking tool rather than as raw attachments
Set up team reporting — if you manage a team, configure aggregate engagement dashboards
Educate your team on what tracking data means and doesn't mean (see accuracy benchmarks above)
Building engagement-based follow-up workflows
Design your follow-up cadence around tracking signals rather than fixed time delays:
Trigger-based steps: If prospect clicks a link → skip the next nurture email and call instead
Re-engagement branches: If no open after 48 hours → send a re-engagement email with a different subject line
Escalation rules: If prospect opens 3+ times without replying → escalate to a phone call or LinkedIn touch
Multi-threading triggers: If email is forwarded → research the forwardee and add them to a parallel cadence
Cool-down rules: If prospect opens but never clicks or replies after 3 touches → reduce frequency to avoid fatigue
Team-level metrics to track
Metric
Benchmark
What it tells you
Reply rate
5-15% for cold outbound, 20-40% for warm
Most reliable measure of email effectiveness
Click-through rate
3-8% for cold outbound
Measures interest in your content/links
Bounce rate
<3%
Data quality indicator
Unsubscribe rate
<1% per campaign
Content relevance indicator
Open rate
Use directionally only (unreliable due to MPP)
Trend indicator only — don't optimize for this
Gotchas
Don't treat opens as reliable signals. Apple MPP inflates open rates to near 100% for ~35-40% of B2B recipients. Use opens as directional, not definitive. Click rate and reply rate are far more reliable.
Don't call immediately after one open. A single open could be an email preview, a bot scan, or Apple MPP. Wait for multiple opens or a click before treating it as a buying signal.
Don't ignore bot clicks. Microsoft Defender and corporate security tools pre-click all links, inflating click data. Look for multiple rapid clicks from the same IP within seconds — that's a bot, not a human.
Don't over-track. Tracking every single email (including internal and personal) creates noise and potential privacy issues. Most tools let you disable tracking per-email or per-recipient — use this for non-prospect correspondence.
Don't rely on tracking instead of asking. Tracking tells you someone opened an email — it doesn't tell you what they thought. The best follow-up is a reply asking a question, not "I saw you opened my email."
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.
Before recommending a specific platform skill
This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ## Related skills, e.g., /sales-mailshake, /sales-klaviyo, /sales-apollo), read that platform skill's actual SKILL.md first. The 1-line description in ## Related skills is enough to identify a candidate — it's not enough to commit to it or to write a prompt that invokes it well.
How to read it:
If ~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.
For sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.
For non-sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.
After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.
/sales-veloxy — Veloxy platform help (Salesforce-native field sales with email tracking, drip campaigns, predictive intelligence)
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill.
Examples
Example 1: Setting up Yesware tracking for the first time
User says: "I just got Yesware for my sales team. How do I set up email tracking?"
Skill does:
Walks through Yesware Chrome/Outlook extension installation
Configures tracking defaults — enable open tracking, click tracking, and attachment tracking
Sets up notification preferences — recommend notifying on 2nd+ open and all clicks, not single opens
Shows how to use Yesware attachment tracking for proposals and decks with page-by-page analytics
Explains team reporting setup (Premium+ plans) for manager visibility into rep engagement metrics
Result: Fully configured Yesware tracking with optimized notification settings and team reporting
Example 2: Interpreting high open rate but low replies
User says: "My open rate is 95% but I'm getting almost no replies. What's going on?"
Skill does:
Identifies Apple Mail Privacy Protection as the likely cause of inflated open rates
Explains how MPP pre-fetches tracking pixels regardless of actual opens
Recommends shifting focus to click-through rate and reply rate as more reliable metrics
Also addresses the content side — low reply rate may indicate weak subject lines, poor personalization, or unclear CTAs regardless of tracking issues
Provides benchmarks for healthy reply rates (5-15% cold, 20-40% warm)
Result: Diagnosis of inflated tracking data plus actionable improvements for email content and metrics strategy
Example 3: Building an engagement-based follow-up workflow
User says: "How do I use tracking data to automate my follow-up workflow?"
Skill does:
Maps tracking signals to follow-up actions (single open → wait, multiple opens → call, click → call immediately)
Designs trigger-based branching in the cadence — skip nurture emails when prospect clicks, escalate to phone when multiple opens
Sets up re-engagement rules for no-open scenarios (new subject line after 48 hours)
Adds multi-threading triggers when forwards are detected
Includes cool-down rules to prevent over-emailing engaged-but-not-responding prospects
Result: Complete engagement-driven follow-up workflow with signal-based triggers and branching logic
Troubleshooting
Tracking showing 100% open rate (Apple MPP)
Cause: Apple Mail Privacy Protection pre-fetches all email content including tracking pixels, registering opens even when recipients don't actually open the email. If a large portion of your recipients use Apple Mail (iPhone, Mac Mail), your open rate will be artificially inflated.
Solution: Stop using open rate as a decision-making metric. Switch to click-through rate and reply rate for measuring engagement. If your tool supports it, filter out Apple MPP opens from reporting (HubSpot and some tools now flag these). For follow-up timing, rely on clicks and replies rather than opens.
Click data seems inflated (bot clicks)
Cause: Corporate email security tools (Microsoft Defender, Proofpoint, Mimecast) pre-click all links in emails to scan for malware. This registers as click events in your tracking data, inflating click-through rates with false positives.
Solution: Check if your tracking tool has bot click filtering (most modern tools do — enable it in settings). Manually, look for clicks that happen within 1-2 seconds of email delivery from the same IP — those are bots. Human clicks happen minutes to hours after delivery and show varied timing patterns. Some tools let you set a minimum time threshold (e.g., ignore clicks within 5 seconds of delivery).
Tracking not working at all (pixel blocked / extension disabled)
Cause: Multiple possible causes — (1) browser extension is disabled or not installed, (2) recipient blocks images by default, (3) email was sent as plain text (no pixel), (4) corporate firewall strips tracking pixels, (5) tool integration is disconnected.
Solution: First, verify the extension is installed and enabled in your browser. Send a test email to yourself to confirm tracking works. If tracking works for you but not for specific recipients, those recipients likely block images — this is expected for 15-25% of B2B recipients. Ensure you're sending HTML emails, not plain text. Check your tracking tool's integration status page for any disconnection alerts. Accept that tracking will never reach 100% of recipients.
