Identity Resolution Pixel

An identity resolution pixel is a first-party JavaScript tag that resolves a portion of anonymous website visitors to deterministic identity records, including a deliverable postal address. It runs in the browser, captures a small set of signals at page load, and queries an identity graph to return whatever identity record matches that visitor with a high enough confidence score. The output, where a match happens, is a real person attached to a real mailing address — turning what was previously an anonymous visit into a mailable lead the brand can follow up with through direct mail, email, SMS, or any other channel they have a postal-address-keyed audience for.

Why this exists now

Identity resolution as a category is older than the current pixel-based implementations — data co-ops have been matching pseudonymous identifiers against consented identity graphs for decades. What changed in the late 2010s and early 2020s was the operational maturity of doing it at the browser layer in real-time, and the privacy framework around when and how the resolved data could be used. Today’s pixels run on consented identity graphs maintained by data partners under CCPA/CPRA, GDPR (where applicable), and the constellation of state-level privacy laws now in force. The pixel doesn’t identify visitors who haven’t consented to be in the graph; it identifies visitors who have, by matching signals their browser already exposes against the graph entries those signals correspond to. Match rates on the better implementations land in the 50 to 60 percent range on U.S. consumer traffic.

How it actually works

The brand drops a JavaScript tag on their site — a single line, deployed through a tag manager or a server-rendered template. On every page load the tag captures a defined set of signals: hashed first-party identifiers if the visitor is logged in (email hash, phone hash), browser fingerprint inputs (user agent, language, time zone, screen size), and behavioral signals (referrer, page path, session timing). These signals get sent to the identity provider’s matching engine, which queries the identity graph for a record whose signals match closely enough to clear a configurable confidence threshold. Where a match clears, the engine returns the matched record — deterministic identifiers (name, postal address, sometimes email and phone) — back to the brand’s data layer.

The matched records flow into whatever audience system the brand uses. In DirectMail.io, they flow directly into a mailable audience that can be triggered into a postcard send the same day, dropped into an email cadence, pushed into a Meta or Google custom audience, or retained in a 90-day retargeting window. The point is not the resolution itself but what the resolution unlocks — the ability to mail or message a high-intent visitor who otherwise would have left the site without leaving a name behind.

What goes in, what comes out

Input: a JavaScript pixel deployed on the brand’s site; the live signals that pixel captures from each visitor; and the consented identity graph the matching engine queries. Output: matched identity records with name, deliverable postal address, and (depending on the match strength) email and phone, scoped to a configurable retargeting window. Records that don’t match clear the threshold are not returned — the system fails closed, not open.

Common pitfalls

The first pitfall is treating the match rate as the only metric. A 60 percent match rate on bot traffic is worse than a 35 percent match rate on real high-intent visitors. Match rate is a function of who’s on the site, not just how good the graph is — and serious shops measure response rate on the resolved cohort, not match rate alone. The second pitfall is mailing the resolved cohort without a clear privacy posture. CCPA, CPRA, and the state-level patchwork all impose disclosure requirements when first-party data is enriched with third-party identifiers, and the brand — not the pixel vendor — carries the compliance responsibility. The third pitfall is treating every resolved visitor the same. A visitor who bounced off the homepage and a visitor who reached the checkout are very different intent signals; the campaign that mails them the same offer wastes money on both. Resolution feeds into segmentation; it doesn’t replace it.

How DirectMail.io runs it

DirectMail.io implements the resolution pixel as a first-party tag deployed in the customer’s domain, with the matched records flowing directly into the platform’s mailable audience system. From there a brand can trigger postcards on the same day a resolved visitor lands, push them into Meta and Google custom audiences, or fold them into a multi-touch cadence with email and SMS. The match infrastructure runs against a consented graph maintained under the privacy framework documented on the Identity Resolution Pixel feature page; the packaging options — standalone pixel, mail-fulfillment add-on, full-funnel — live on the Identity Resolution solution page.

When to use this

• On any site with meaningful anonymous traffic. If the marketing layer is converting only a small percentage of visitors and the rest leave without identifying themselves, identity resolution is the highest-leverage tool to recover that audience.
• For high-consideration purchases. Auto, real estate, financial services, healthcare — categories where the buying cycle is long enough that mailing a follow-up days later is still well within the consideration window.
• For cart abandonment recovery beyond email. Email cart-abandonment workflows top out around 10 percent recovery on most catalogs. Mail and email together — especially with synchronized timing — lift recovery substantially.