Identity resolution pixel.
Mail the visitor who never gave you their email.
Most website visitors leave without identifying themselves. The Identity Resolution Pixel changes that — a single JavaScript snippet matches anonymous visitors against a CCPA-compliant postal identity graph, resolves a meaningful share to a deliverable household address, and triggers personalized direct mail tied to the actual visit. The result: a closed-loop touch from anonymous web traffic to a physical mail piece in the recipient’s hand within the post-visit window — and revenue attributed back to the originating visit.
Five steps. One pixel. Closed-loop attribution.
- 01
Drop the pixel on the website
A single JavaScript snippet installs on the site — pages, products, pricing, blog. The pixel is lightweight (under 5 KB), loads asynchronously, and does not affect page performance metrics.
- 02
Anonymous visitors are matched to a postal identity
Visitors land on the site without identifying themselves. The pixel runs hashed signal collection (device, IP, behavior) and matches the visitor against a CCPA-compliant postal identity graph. A meaningful share of U.S. consumer traffic resolves to a household-level identity with a deliverable mailing address.
- 03
High-intent visits flag the recipient for trigger mail
Resolved visits route into the campaign engine with the visit metadata — pages viewed, time on site, exit page, return visits. Trigger rules fire based on intent signals: pricing-page visit, cart abandonment, repeat visit, specific-product depth.
- 04
Mail composes and queues per individual visitor
A 4x6 or 6x9 piece composes per resolved visitor with variable data tied to the actual visit — the product viewed, the offer that aligns with the journey, the personalized landing-page URL. The drop queues for the next available print window.
- 05
Closed-loop attribution back to the originating visit
Response is tied back to the originating visit through the campaign code on the piece. The dashboard shows revenue attributed to specific resolved visits — a closed-loop measurement that retargeting digital ads can rarely produce on the same precision.
Why mailing anonymous traffic outperforms retargeting it.
Display retargeting on an anonymous visitor delivers an impression — most of which gets ignored. Banner-blindness rates are well documented; the click-through math on retargeting display has been deteriorating for a decade. The same visitor, mailed a physical piece tied to the specific page they viewed, gets a response rate that is consistently a multiple of the digital number — because the piece is held, the offer is read, and the recipient remembers the visit.
The compounding play is to do both. The Identity Resolution Pixel resolves the visitor and DirectMail.io pushes the resolved identity to Meta as a custom audience automatically — the same visitor gets the mail piece in the mailbox and the paid social ad in the feed within the same window. Two coordinated touches on a high-intent recipient who otherwise was a single anonymous session in your analytics tool.
The closed-loop attribution is the other structural advantage. Every triggered mail piece carries a campaign code tied to the originating visit. When the recipient converts — by phone, by web visit with a personalized URL, by store walk-in — revenue ties back to the specific visit that triggered the piece. The CFO question of "did the program work" gets a per-visit answer.
Where the pixel earns its keep.
-
B2C e-commerce cart abandonment
A visitor adds a high-value item, hesitates, leaves. The trigger fires direct mail with the abandoned product and an offer, while a Meta retargeting audience captures the same visitor for paid social.
-
B2C pricing-page intent
Visitors who reach the pricing page but do not convert are the highest-intent anonymous traffic on most consumer sites. Mail to that segment closes a meaningful share within the post-visit window.
-
High-consideration B2B intent
Software, financial services, and high-ticket B2B sites resolve traffic to firmographic identity for ABM-style direct mail follow-up — an alternative to LinkedIn outreach with materially higher response.
-
Content site monetization
Editorial and content-led sites resolve high-engagement readers (multiple visits, time on site) and trigger sponsor or product mail to that segment — a direct revenue stream from organic traffic.
Questions teams ask before deploying.
Short answers. For implementation specifics on your stack — pixel install, consent configuration, downstream activation — book a demo.
-
What is an identity resolution pixel and how is it different from a tracking pixel?
An identity resolution pixel collects hashed device and behavioral signals from anonymous website visitors, then matches those signals against a CCPA-compliant identity graph to resolve the visitor to a real household with a mailing address. A standard tracking pixel only tracks behavior under a session ID. The identity resolution pixel adds the matching layer that makes the visitor mailable. The match happens on the server side, the input signals are hashed, and the output is a deliverable postal address suitable for direct mail.
-
What share of website traffic resolves to a postal identity?
Resolution rates vary materially by traffic source, audience profile, and the breadth of the underlying identity graph. Typical U.S. consumer-facing sites see resolution rates that make the program economically viable on traffic volumes most marketers consider modest — meaningfully lower than email-capture rates, but with the advantage that the resolved identity is a verified deliverable address rather than a self-reported email. The platform reports the actual resolution rate per source so the team can see the math on their own traffic.
-
Is identity resolution compliant with CCPA, CPRA, and similar privacy regulations?
The DirectMail.io identity graph runs CCPA-compliant resolution by default and supports the consumer right-to-delete workflow on every resolved record. The pixel collects hashed signals (not personally identifiable information at the browser layer), and the match happens against a graph built from consented data sources. For brands with strict privacy postures, the pixel can be configured to require explicit consent banners before signal collection — the platform supports both modes.
-
How quickly does mail trigger after a website visit?
Trigger speed depends on the print and postal cadence the team configures. Common setups: same-day flag with next-business-day press release, or a daily batch trigger that mails everyone resolved that day. Mail typically arrives 3 to 7 days after the originating visit, depending on USPS service standards to the recipient address. For high-intent triggers (pricing-page, cart abandon), faster cadence configurations are available.
-
Why mail an anonymous website visitor instead of just retargeting them with digital ads?
Two reasons. First, response rates on direct mail to a verified high-intent visitor consistently outperform display retargeting, often by significant multiples — the inbox impression a banner ad delivers gets ignored at well-documented rates, while the physical piece is held in hand and read or recycled. Second, the same recipient can be retargeted across both channels — DirectMail.io exports the resolved identity to Meta and other paid social platforms automatically, so the visit triggers mail and digital retargeting simultaneously.
-
How does this integrate with our existing analytics and ad tech?
The identity resolution pixel coexists with Google Analytics, Adobe, GA4, and standard tag-manager setups — it is one more script in the head. Resolved identities are available through the DirectMail.io REST API and webhooks, so they can be piped into CRM, marketing automation, or BI systems for downstream activation. The platform also natively pushes resolved audiences to Meta Ads Manager as custom audiences for digital retargeting on the same recipient.
-
How is identity resolution different from address appending?
Identity resolution operates on anonymous web traffic — visitors who never identify themselves. Address appends operate on lists where some identifying information already exists (typically email or phone) and the address is filled in from that. The two features compose: a visitor who fills out a form leaves an email; address appends turn that email into a mailable address. A visitor who never fills out a form is invisible to address appends and visible only to identity resolution.
Resolve a sample of your traffic in 30 minutes.
Bring 1,000 sessions of anonymized traffic. We’ll run them through the pixel live and show the resolution rate, the resolved identities, and the trigger configuration that would activate them.