Email activity feed

The Activity page is the single place to see every email event in your account: each send, open, click, and bounce, across all broadcasts and all automations. When you need to answer "did contact X get email Y?", this is where you look — you don't have to know in advance whether the email came from a broadcast or a flow.

What each event means

Every row in the feed is one event for one contact and one email:

• Send — Reach handed the email to the receiving mail server. This is the event that proves an email went out.
• Open — the recipient's mail client loaded the email's tracking image. Treat opens as approximate: some clients block tracking, and others pre-fetch images so an email can register as opened without being read.
• Click — the recipient clicked a tracked link in the email. Clicks are more reliable than opens as a signal of real engagement.
• Bounce — the receiving server rejected the email. Hard bounces (the address doesn't exist) lead to the contact being suppressed, and suppressed contacts never receive email again. See Subscription status and unsubscribes.

Events from broadcasts and automations look the same in the feed; each row shows which message produced it.

Filtering the feed

On a busy account the raw feed moves fast, so filtering is how you actually use it. You can narrow the feed by the dimensions shown in the filter bar — typically contact, event type, message, and time period.

1. Open the Activity page.
2. Apply a filter — for example, a contact's email address, or the event type "bounce".
3. Combine filters to narrow further, such as one contact plus one message.

Two scoped versions of this page exist elsewhere in Reach, and they are the same feed with a filter pre-applied:

• Each automation's activity view is this page scoped to that one workflow. See Automation activity and troubleshooting.
• Broadcast reports summarize this data per campaign. See Broadcast reports.

Answering "did contact X get email Y?"

This is the most common support question the Activity page settles, for your customers and for your own team:

1. Open the Activity page.
2. Filter by the contact's email address.
3. Find the message in question and check its events, from newest to oldest.

Then read the result:

• A send event exists — the email went out. If the contact says they didn't get it, ask them to check spam and search their inbox for your sender address. An open or click event settles it conclusively: the email arrived.
• A send event exists, followed by a bounce — the email went out but was rejected. Check the address for typos. If it hard-bounced, the contact is now suppressed.
• No send event exists — Reach never sent it. The contact may have unsubscribed or been suppressed before the send, a condition in an automation may have routed them past the email, or they never qualified for the message at all. For automation emails, work through the checks in Automation activity and troubleshooting; for broadcasts, confirm the contact was in the audience you sent to.

Common uses

• Verifying a new automation. After activating a flow, trigger it with a test address, then filter the feed to that address and watch the send events arrive in order. This is faster than waiting for real contacts.
• Spotting deliverability trouble early. Filter by bounces over the last few days. A sudden cluster of bounces — especially to one domain like a corporate mail server — is your earliest warning. See Deliverability best practices.
• Confirming an unsubscribe or suppression took effect. After a contact opts out, their address should show no new send events. If you see sends to a contact you believe unsubscribed, check their subscription status first.
• Handling a "stop emailing me" complaint. Filter to the contact and see exactly which messages reached them and when, so you can respond with specifics instead of guesses.

The Activity page tells you what happened to each email. For what those emails achieved — revenue, conversions, attribution across channels — use Ana, Zalify's analytics and attribution product.