Back to How it Works Index
Technical Deep-Dive

Real-time Tracking & Campaign Reports Flow

Understand the core mechanics, queues, and logic routines running on our servers when processing this module.

System Execution Pipeline

Below is the step-by-step sequence of events executed by our background workers.

1

Pixel Loaded

A recipient opens the email. Their mail client downloads the tracking pixel.

2

Redirect Clicked

Recipient clicks a link. The browser visits our server, which registers the click and redirects them.

3

Geo IP Lookups

The server resolves the recipient's IP to identify their country and city.

4

Dashboard Update

Metrics are compiled, and Socket.io pushes updates to active browser dashboards.

5

PDF Export

User requests a report. Puppeteer renders the charts and saves a PDF download.

Developer & Architect Notes

Technical Architecture

This module operates as a stateless service hosted across horizontally scalable server nodes. Distributed state coordinates through highly optimized Redis transactions to ensure consistency without deadlocks.

IP GeolocationGeoIP Database Lookup
Live UpdatesSocket.io Client-Server Sync

Edge Fail-Safe Rules

Critical protocols (like connection failure retries, cool-down timers, and data limits) are verified before outbound dispatches. Failures degrade gracefully, prioritizing list health and preventing blacklisting.

Analytics ChartsRecharts Visualization Library
PDF GeneratorServer-side Puppeteer Renderer
Technical FAQ

How real-time tracking & campaign reports behaves.

Answers about the execution flow, failure handling and limits of this module.

How are opens and clicks tracked?

Opens are recorded through a 1x1 tracking pixel embedded in the message, and clicks through redirect links that log the event before forwarding the recipient to the destination.

How quickly do results appear?

In real time. Events stream to the analytics dashboard over a WebSocket connection, so you can watch a campaign progress rather than waiting for a batch report.

Can I see where my recipients are opening from?

Yes, approximately. Open events are resolved to a location and device type from the request. One caveat worth knowing: Gmail and Yahoo load images through their own proxy servers, so opens from those providers reveal neither the reader's device nor their true location, and are reported as unknown rather than guessed.

Can I export a report to share?

Yes. Campaign results can be exported as a PDF report suitable for sending to a client or stakeholder.

Is open tracking reliable?

Open rates are directional, not exact, on any platform. Privacy features such as Apple Mail Privacy Protection pre-fetch tracking pixels, which inflates opens. Click tracking is the more dependable engagement signal, and both are reported separately here for that reason.