Product
What Is a HEM and How Does It Match a Person?
A hashed email (HEM) bridges anonymous browser sessions and real people. How SHA256, SHA1, and MD5 HEMs work in identity resolution.
Product
How Fast Should a Visitor-ID Webhook Fire?
Webhook latency is the difference between a useful signal and a dead alert. The engineering behind sub-second delivery: hot path, retries, slow endpoints.
Product
How to Scale an Identity Graph to 100M+ Matches/Day
The architecture behind 280M profiles, 60B signals, 5M sites, and 24-hour refresh: ingest, hot-path serve, decay, and the tradeoffs.
Product
How Suppression Lists Work in Visitor Identification
Suppression lists are how visitor ID respects opt-outs, customer exclusions, and compliance flags. Why they belong at the graph layer.
Product
Inside the Orbit Pixel Network: How It Works
How a cross-site pixel network produces person-level intent: pixel observation, identity join, scoring, and why this beats licensed bid-stream feeds.
Product
How Often Should Intent Data Be Refreshed?
Intent from last quarter tells you nothing about today. Here is why Leadpipe refreshes every record every 24 hours, and what weekly and monthly refreshes miss.
Product
How We Built the Leadpipe Identity Graph
The principles behind 280M verified profiles and 30-40%+ match rates: deterministic matching, first-party signals, daily refresh, build vs license.
Product
How to Parse JavaScript-Rendered Intent Signals
Most of the modern web renders via JavaScript. How a serious intent pipeline parses SPA pages, headless rendering tradeoffs, and what naive crawlers miss.