john mark lowry
§ platforms · 2026

pulse

Ad tags fail silently. Pulse watches the measurement layer itself, across the site and the dealer network.

team one internal tool, deployed in production on the agency's internal aws/eks platform. vendor specifics withheld.

the short version

The origin story is the argument: dealer-site conversion tags once dropped off completely and nobody noticed for weeks, because monitoring meant a person scanning pivot tables. Pulse watches 2,246 tags across lexus.com and ~244 dealer sites with daily automated pulls, and Postgres accumulates history past the ad platform's hard 60-day lookback — the database remembers what the vendor won't.

The anomaly engine runs in three layers: deterministic rules, then statistical day-of-week baselines with adaptive per-tag thresholds, then a model-written narrative — the LLM explains, it never detects. Correlated-failure grouping turns fifty dealer tags dropping at once into one root-cause alert instead of fifty pages of noise.

Full case study in progress — artifacts pending clearance or writing time. The insight below is already earned.

Analytics fail silently — the measurement layer needs its own measurement. A broken tag looks exactly like a quiet day until you check.

the insight
ran onPython + FastAPI · PostgreSQL (history accumulator) · React + Visx · 3-layer anomaly engine · production on AWS

← all work