07 / Email infrastructure / Analytics

EMAIL TRACKING SYSTEM

Pixel-based email analytics and campaign tracking infrastructure.

Private client project — not publicly deployed.

EMAIL TRACKING SYSTEM
Visitor traffic — opens, clicks and unsubscribes, with IP, ISP and offer filters.

Screenshots

Visitor traffic — opens, clicks and unsubscribes, with IP, ISP and offer filters.
Visitor traffic — opens, clicks and unsubscribes, with IP, ISP and offer filters.
Offers — preview and unsubscribe URLs, affiliate network and type.
Offers — preview and unsubscribe URLs, affiliate network and type.
Domain management — names, mailbox and SSL status.
Domain management — names, mailbox and SSL status.

Overview

Custom tracking — opens via pixels, clicks via redirects, deliverability and per-campaign dashboards. Every open and click is logged against the recipient, the offer and the sending domain, so a campaign's performance can be broken down by more than a single aggregate open rate. Each event also carries a timestamp, so trends across a campaign's lifetime are visible rather than just a final total.

The problem

Marketing needed detailed analytics without expensive third parties, across transactional and campaign mail. Off-the-shelf email platforms bill per contact or per send and bundle tracking with sending, so a team using its own transactional mail infrastructure — AWS SES, for instance — had no way to get the same open, click and deliverability detail without also moving its sending through that platform.

The solution

Laravel tracking service: 1×1 pixel, click proxy, real-time dashboard, domain deliverability and recipient events. The pixel endpoint records an open the moment an email client loads the image, and the redirect proxy logs a click before forwarding the recipient to the real destination URL, so both events are captured without changing what the recipient actually sees. Events are filterable by IP, country, ISP, offer and date, with SSL status tracked per sending domain. Redis queues the incoming pixel and click events so the endpoints respond immediately and the heavier logging work happens asynchronously.

Role

Backend and infrastructure — pixel server, redirects, analytics pipeline, dashboard. Responsible for keeping the pixel and redirect endpoints fast under load, since a slow pixel is a slow-loading email for the recipient. Both services are kept intentionally small and stateless, since they sit on the request path for every tracked open or click, and a crashed pixel endpoint would show up as a broken image in the recipient's inbox.

Result

Millions of events, sub-100ms pixel responses, several campaigns at once. Used across multiple marketing campaigns simultaneously, with per-campaign dashboards and domain-level deliverability visible without needing a third-party analytics platform.

Features

  • Visitor traffic: opens, clicks and unsubscribes
  • Filters by IP, country, ISP, offer and date
  • Offer list with preview and unsubscribe URLs
  • Domain management with SSL status
  • Pixel opens and click redirects
  • Per-campaign dashboards

Technology

Bric Reda
About the author

Bric Reda is a full stack developer based in Tangier, Morocco, building Laravel, React and TypeScript software — SaaS platforms, ERP systems and production applications for businesses in Morocco and Europe.

More about Bric Reda

Selected projects

MATARTAXIANYWARE ERPANYBOT

Related articles

Deploying Modern Laravel Applications
Let's Build Your Project →