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
What Does an Orbit Score of 80 Actually Mean?
A field guide to reading the Orbit intent score from 1 to 100, what each band represents, and how to set thresholds that surface real buyers.
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 Early Can Orbit Detect In-Market Buyers?
A week-by-week look at how Orbit catches buyers in the research phase, how early signals appear, and what thresholds surface genuine intent vs noise.
Product
Why Does Orbit Refresh Intent Every 24 Hours?
Intent decays in days, not weeks. A look at why Orbit runs a 24-hour refresh cycle, how the pipeline actually works, and what weekly refresh costs you.
Product
What's Inside an Orbit Intent Topic?
A field-level teardown of how Orbit builds an intent topic, what a person-level signal contains, and what a score of 80 actually represents.
Product
How Is Visitor Identification Accuracy Measured?
Accuracy, match rate, and completeness are different things. The methodology, failure modes, and how Leadpipe scored 8.7/10 in an independent test.
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
What Is an MCP Server for Sales Data?
What an MCP server is, why it matters for sales data, and how the Leadpipe MCP gives agents direct access to 27 tools across intent, visitor, and pixel data.
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.