Insight · Engagement
Engagement events track what the recipient does after delivery: opened, clicked, complained, unsubscribed. Every event ships with bot, proxy, and VPN verification plus device and geolocation context — so an open rate inflated by Apple Mail prefetch and scanner bots stops fooling you. The signal you can act on, separated from the noise.
Engagement · Open detail
TransactionalVerification signals
↑ a real human, on real consumer infra
Recipient actions
Once a message is delivered, the recipient takes over the story. Every action they take is captured the instant it happens — with the context to tell a genuine signal from an automated artifact.
The tracking pixel loaded — with bot, proxy, VPN, and hosting flags so you know whether a human or a scanner triggered it.
A tracked link was followed — which link, from which device, in which country, verified the same way opens are.
Marked as spam via the ISP feedback loop. Flows straight into suppression, and you can see the message that triggered it.
Opted out through the preference centre or list-unsubscribe. Captured and honoured immediately, no manual step.
Two opens · same campaign
which one counts?Bot
No
Hosting
No
Device
iPhone
Bot
Yes
Hosting
Yes
Device
cache
Open verification · is it real?
Apple Mail Privacy Protection prefetches every tracking pixel the moment a message lands — before the recipient lifts a finger. Gmail's image proxy fires opens for caching. Corporate scanners follow every link. The raw open rate is a sum of these phantom events plus the real ones, and most platforms can't pull them apart.
Every engagement event in ONE carries verification signals — bot flag, anonymous-proxy / VPN / hosting-provider / Tor flags from the IP intel layer, full user agent, geolocation. The headline number is still there. But each event also tells you whether it was a human on a phone in Karachi or a scanner on hosting infra in Frankfurt. Filter one way for the headline, the other way for the truth — then feed only verified engagement into your segments and lead scores.
Three ways to consume
The same engagement events feed all three. The dashboard for analysis, webhooks to score leads and update your CRM, Pushover for the moments you want to know the instant a VIP opens.
Pull
The Engagements surface — events by country, device, browser, subject, plus a Newsletter vs Transactional split and per-event detail with full verification signals. Filter to verified humans before you draw a conclusion.
Best for: campaign analysis, audience insight.
Push · systems
Every action — open, click, complaint, unsubscribe — fires a webhook to your endpoint the moment it happens. Score leads in your CRM on click, suppress on complaint, trigger a follow-up sequence on open. The verification flags travel with the payload.
Best for: lead scoring, CRM sync, automation.
Push · people
Define a criterion — a complaint comes in, a key account clicks, a verified open from a target segment — route the webhook to the Pushover mobile app, and the alert lands on your phone instantly. The moments worth knowing about right now.
Best for: sales signals, complaint watch.
Why verification changes the math
Engagement metrics drive real decisions — which subject lines win, which segments are warm, which leads to route to sales. If the underlying events are half bots, every one of those decisions is skewed.
Since Apple Mail Privacy Protection rolled out, a large share of 'opens' are pixel prefetches that happen whether or not a human ever sees the message. Add Gmail's image proxy and corporate link scanners, and the raw open metric becomes a blend of real interest and machine noise. Tuning content against that blend means optimizing partly for what bots respond to.
ONE attaches verification signals — bot, anonymous proxy, VPN, hosting provider, residential proxy, Tor exit node — to every engagement event. You can compute the headline open rate for the board deck and a verified-human open rate for the decisions that actually matter. The two are often strikingly different, and knowing the gap is itself useful.
Because verified engagement flows through webhooks too, your downstream systems inherit the same discipline. Score a lead on a verified click, not a scanner following links. Trigger a sales alert on a real open from a target account, not a prefetch. The quality filter lives on the event, so everything reading the event gets it for free.
What this replaces
Without per-event bot/proxy verification, open rate blends real humans with pixel-prefetching scanners. Tuning subject lines against that number optimizes for whatever the bots respond to. ONE's verification flags let you filter to verified human opens before drawing a single conclusion.
Routing a 'hot lead' to sales because a corporate scanner followed every link in your email wastes the rep's time and erodes trust in the data. Webhook engagement events carry the bot/hosting flags, so your scoring logic can require a verified human action before it fires.
A complaint that sits unseen in a dashboard until the weekly review is a reputation risk you let compound. Criteria-based Pushover alerts put a complaint on the responsible person's phone the moment the feedback loop reports it — and the offending message is one tap away.
If opens and clicks only live in the ESP's dashboard, your CRM and product analytics are flying blind. Instant webhooks push every verified action to wherever your team actually makes decisions, so engagement isn't a silo.
Common questions
Engagement tracks the recipient: did they open, click, complain, unsubscribe. Delivery status (DSN) tracks the message: did it reach the recipient's mail server, and if not why. Engagement answers 'did it work?'; DSN answers 'did it land?' This page covers engagement; delivery status (DSN) has its own deep-dive. They're two separate event streams, and ONE keeps them distinct on purpose.
Every engagement event is enriched with IP intelligence — the source IP is checked against categorisations like anonymous proxy, VPN, hosting provider, residential proxy, public proxy, and Tor exit node, plus a bot heuristic. Those flags surface on the event alongside the user agent, browser, OS, device, and country. You don't write your own filter — the flags are already on the event when you read it, in the dashboard and in the webhook payload.
Yes. Apple Mail Privacy Protection and Gmail's image proxy prefetch tracking pixels from their own caching infrastructure, which lights up the Hosting Provider flag (and often Bot) on the engagement event. Real opens from a human device come from consumer ISP or mobile-carrier IP space with the bot/proxy/hosting flags all set to No. Filter on those flags to isolate verified human opens.
Yes. An open event fires when the tracking pixel loads, a click event when a tracked link is followed, a complaint event when the ISP feedback loop reports it. The live dashboard updates in real time and webhooks fire in real time — there's no batch delay between the recipient's action and the notification.
Every one — open, click, complaint, unsubscribe. Each fires an instant webhook to your endpoint carrying the full event payload, including the verification flags, device, geo, and the message it relates to. Use them to score leads, sync your CRM, trigger follow-up sequences, or keep suppression in lockstep with complaints.
Pushover is a mobile push-notification app. You wire an engagement criterion — a complaint, a verified open or click from a key account or target segment — through a webhook to Pushover, and matching events arrive as a push notification on your phone instantly. Same event stream as the webhooks, routed to a human. Ideal for sales signals and complaint watch.
Yes. Every event carries a feed-type label — Transactional or Newsletter (campaign) — and the dashboard offers a side-by-side comparison plus filters for campaign-opened, campaign-clicked, transactional-opened, and transactional-clicked. You can analyse engagement quality separately for the two send paths, since their audiences and expectations differ.
Related
The sibling signal. Engagement tracks what the recipient did; DSN tracks where the message went — received, queued, delivered, bounced.
Read moreFeed verified engagement — not bot noise — into dynamic segments. Build a "genuinely engaged in the last 30 days" audience that actually means it.
Read moreComplaint and unsubscribe engagement events flow straight into suppression. Webhook them too, to keep your own systems in lockstep.
Read moreEngagement events roll into campaign-level reporting, audience cuts, and comparative reports for longer-horizon analysis.
Read moreEvery engagement event is attributed to the Bridge the original message was sent through. Compare engagement quality per app.
Read moreWebhooks push engagement out; the REST API lets you pull and act. Together they cover both directions of the integration loop.
Read moreMumara ONE · Realtime Engagement Tracking
Opens, clicks, complaints, unsubscribes — every action in real time, every one carrying bot, proxy, and VPN verification. Watch it live, stream it via instant webhooks, or push it to your phone with Pushover.
