Small BusinessIndependent InvestorTrade BusinessAccountingFinanceLegalMarketingOperationsSalesReal EstateTemplatesPricingDocs
Get started

Step Guide: Email Tracking

Email

Track email opens, clicks, and bounces automatically

Overview

The Email Tracking step queries the delivery service for engagement data about a previously sent email and automatically suppresses problematic addresses.

Track

Look up delivery and engagement data for a sent email. Takes the message ID from a previous Send Email step and returns delivery status, open/click counts, bounce information, and spam complaint data.

  • Track whether recipients opened or clicked links in a marketing email
  • Tailor follow-up emails based on engagement. Send a different message to openers versus non-openers.
  • Monitor delivery rates and spam complaints across an email campaign
  • Build re-engagement sequences that skip unresponsive contacts

Takes the message ID from a previous Send Email step and queries the delivery service. Returns delivery status, open and click counts, bounce information, and spam complaint data. Hard bounces, soft bounces, and spam complaints are automatically added to the suppression list. Configure a delay (default 2 days) to allow time for engagement data to accumulate.

Tips
  • Use a longer delay (e.g., 5 days) if you want to capture opens and clicks, not just delivery status
  • Use a Condition step after Email Tracking to branch on engagement (e.g., send follow-ups to openers)

Frequently Asked Questions

How long should I wait before checking tracking data?
The default delay is 2 days. Use a longer delay (5+ days) if you want to capture opens and clicks. Shorter delays only capture immediate delivery status.
Does Email Tracking handle bounces automatically?
Yes. Hard bounces, soft bounces, and spam complaints are automatically added to your suppression list, so future Send Email steps skip those addresses.
Can I track multiple emails from one workflow?
Yes. Add an Email Tracking step after each Send Email step you want to track, mapping the message_id from each sender.