Know exactly when every email event happened
Most campaign reports give you a count. An email tracker that stamps the moment of every open, click, bounce and unsubscribe gives you a sequence — which is what you need to tell a contact who read it twice apart from one who never opened it at all.
- Precise timestamps for delivery, first open, first click, and unsubscribe
- A timestamp on every recipient row — not just campaign-wide totals
- See how long a contact took to open, and to click after opening
- Export logs for CRM sync, compliance, or custom analytics
ms
timestamp precision
4
event types tracked
Per-recipient
event timeline
CSV
export format
Millisecond precision
Every event is timestamped with exact date and time — no rounding.
Full event history
See every interaction per recipient: all opens, all clicks, in sequence.
Exportable logs
Download the full event log as CSV for CRM sync or compliance.
How email event timestamping works
Send your campaign
Pingovo dispatches your email and records the delivery timestamp immediately.
Events captured automatically
Opens trigger the tracking pixel; clicks go through a redirect — all logged with exact timestamps.
View the timeline per recipient
Open any recipient record to see their complete event timeline in chronological order.
How email tracking actually works
There is no read receipt in email. Nothing in the protocol lets a sender ask whether a message was read, so every email tracker in existence infers it from two side effects, and both have edges worth knowing about before you draw conclusions from a number.
Opens — a 1×1 pixel
An invisible image, unique to that recipient, is added to the message. When the mail client requests it, the request is an open: it carries the time, the user agent and the requesting IP. If images never load, the open never registers.
Clicks — a rewritten link
Each link is rewritten to pass through Pingovo first. The click is recorded with its timestamp and the destination, then the recipient is redirected onward. A click is a much stronger signal than an open, because nothing loads it automatically.
Why a raw open count is worth less than the timestamp beside it
Corporate security gateways fetch every image in a message the moment it is delivered, to scan it. That fetch looks exactly like an open — same pixel, same request — and it inflates open rates for precisely the recipients who are hardest to reach. Pingovo discards opens recorded within two seconds of the send for that reason: a scanner pulls the image immediately, a person almost never does.
The filter has one deliberate exception. Gmail and Yahoo proxy images through their own infrastructure at the moment a human opens the message, not on delivery, and they then serve every later view from cache without the pixel ever reaching us again. Rejecting those requests would throw away the recipient's one and only real open — so a fetch identifying itself as Google's or Yahoo's image proxy bypasses the timing check and is always counted.
The other direction is Apple's Mail Privacy Protection and every client that blocks remote images: those opens never reach anyone's tracker at all. Which is why the honest reading of open data is directional — treat the count as a floor, use clicks as the real engagement signal, and use the timestamps to see the shape of the response rather than its exact size.
Every recipient is a row, not a statistic
Campaign totals tell you how a send went. They cannot tell you whether the contact you are about to call opened it. Each recipient keeps its own sent, opened, clicked and unsubscribed stamps, so a name can be looked up directly rather than inferred from a percentage.
Filter the list by what happened — opened but never clicked, bounced, unsubscribed — and the export follows the filter you are looking at. You get the segment you were reading, not the whole campaign to re-filter in a spreadsheet afterwards.
- Sent, opened, clicked and unsubscribed times on every row
- Filter by status, then export exactly that view as CSV
- Soft bounces are shown as their own state — a temporary rejection is not an outcome
opened 09:47:02
opened 10:02:18
opened 11:15:40
opened 14:38:51
Frequently asked questions
Four event types are recorded: open, click, bounce and unsubscribe. Each recipient row carries the time it was sent, the time it was first opened, the time a link was first clicked, and the time it unsubscribed.
Not per contact. A recipient row records the first open, so repeat opens by the same person do not appear on their own timeline. Campaign-wide open counts and the hour-by-hour open chart do include every recorded open, so you can see when engagement clustered across the whole send.
Open any campaign and go to the Recipients tab. Each contact carries its own sent, opened, clicked and unsubscribed timestamps, and you can filter the list by status and export the result as CSV.
Yes. Export the full recipient event log as a CSV from any campaign report. The export includes email address, event type, and ISO timestamp for every recorded event — suitable for GDPR data subject requests.
No, and no tool can — email has no read receipt. An open is inferred from a tracking pixel loading, which means it misses anyone whose client blocks remote images and can be triggered by machines that were never going to read anything. A click is the reliable signal: nothing loads a link automatically, so a click timestamp is a person.
No. Corporate gateways fetch every image the moment a message is delivered, which would register as an instant open. Opens recorded within two seconds of the send are discarded as prefetch. The exception is Gmail and Yahoo, whose image proxies fetch on a genuine human open rather than on delivery — those are always counted, because discarding them would lose the recipient's only recorded open.
Apple's Mail Privacy Protection loads images on Apple's servers for some recipients and not at all for others, and a growing share of clients block remote images by default. Neither produces a trackable open. The count is a floor, not a measurement — read it as a trend against your own past campaigns, and lean on click timestamps when you need certainty.
Start for free
Get full event timestamps and activity logs from your very first send.