A lightweight pixel resolves 50% to 60% of anonymous visitors to a verified postal identity — name, address, email, phone, and around 70 demographic fields. Run the campaign on DirectMail.io, push the data into your web-to-print, or push it straight to your CRM.
They browse the product pages. They check the prices. They put items in the cart. They don’t fill out a form. They don’t make a phone call. They don’t identify themselves — and your CRM never sees them. The traffic is real, the intent is real, and your campaigns can’t reach them.
One JavaScript snippet on the site, under 5 KB, async, no impact on Core Web Vitals. Hashed signals collect on the visit, match against a CCPA-compliant identity graph, and resolve to a verified household. The match happens server-side — no personally identifiable information is collected at the browser layer.
Full name, postal address, email, phone — the verified individual behind the visit, not a session cookie.
Household composition, income tier, presence of children, homeowner status, length of residence.
Age range, gender, marital status, ethnicity (where consented), occupation, education, language preference.
Pages viewed, time on site, return visits, exit page, product depth, cart contents — the visit context, not just the visitor.
Hobbies, charitable affinities, travel patterns, vehicle ownership, pet ownership — drawn from consented household-level signals across the identity graph.
CCPA / CPRA-compliant by default. Consumer right-to-delete handled per record. Configurable consent-banner gating for stricter privacy postures.
Identity resolution is a data layer. You decide how it gets activated — run it on DirectMail.io, plug it into a web-to-print workflow, or push it to your own systems. Many customers mix paths: a CRM push for the digital activation, DirectMail.io for the mail piece.
We build the campaign.
You bring the pixel and the website. We resolve the identities, set up the omni-channel campaign, and run mail, email, SMS, and Meta retargeting on the platform. Attribution rolls up in one dashboard. Same workflow as every other DirectMail.io campaign.
Mail · Email · SMS · MetaYou print, we resolve.
For printers and agencies running their own production, the resolved identities flow into a connected web-to-print workflow — yours or ours — with variable data ready for the press. Each piece personalizes to the visitor: pages they viewed, products they considered, the offer that fits.
For printers + agenciesWe resolve, you activate.
Resolved identities — name, email, phone, and the demographic fields — push into your CRM, marketing automation, ad platforms, or BI stack via API, webhooks, or SFTP. You activate on your own schedule and your own stack. We sit underneath the data layer.
Salesforce · HubSpot · Klaviyo · Snowflake · Meta · GoogleA visitor adds a high-value item, hesitates, leaves. The identity is resolved, the resolved record fires into the campaign engine, and a personalized direct mail piece — with the abandoned product, an offer that fits, a personalized URL — drops the next press cycle. Email and Meta retargeting fire in parallel.
Mail · Email · MetaVisitors who reach a pricing page, a product detail page, or a configurator without converting are the highest-intent anonymous traffic on most consumer sites. Resolve them, mail them, retarget them — with the specific product or offer they were looking at on the piece.
Mail · Personalized landing pageEvent sites see massive anonymous browse traffic — tour pages, venue pages, date pages — followed by long consideration windows. Resolve the browser, mail them with the dates that align with their location, push them into your ticketing CRM for re-targeting in your own stack.
Mail · CRM pushCustomers who once had an account, then stopped engaging, often return to browse without logging in. The pixel re-identifies them on those return visits and triggers reactivation campaigns — a category of revenue most marketing stacks leave on the table because the visitor is invisible to logged-in analytics.
Mail · Email · CRMSoftware, financial services, and high-ticket B2B sites resolve anonymous traffic to firmographic identity — company, role, address — for ABM-style direct mail outreach. An alternative to LinkedIn that materially outperforms display retargeting on the same audience.
Mail · ABM list buildEditorial sites, podcasts, and content-led businesses resolve high-engagement readers (multiple visits, deep time on site) and trigger sponsor mail, product mail, or affiliate offers. A direct revenue stream from organic and earned traffic that previously had no monetization path.
Mail · Sponsor activationA live-entertainment company that produces tours for some of the biggest entertainers in the world (NDA — we can’t name them) has run identity resolution as a primary acquisition channel for over two years.
By their own internal attribution, this is the #1 data source in their entire marketing stack — outperforming every paid media channel, every list buy, and every partnership they’ve evaluated. Anonymous browsers on tour pages, venue pages, and date pages get resolved, mailed, and re-targeted in their CRM, and the resulting attribution is what made this their lead channel.
A lightweight JavaScript pixel installs on the website. When a visitor lands, the pixel collects hashed device and behavioral signals. Those signals match against a CCPA-compliant identity graph — built from consented data sources across hundreds of millions of US households. A meaningful share of visitors resolves to a verified household: name, postal address, email, phone, and the demographic fields. The match happens server-side. No PII is collected at the browser layer.
Typical match rates land between 50% and 60% on US consumer traffic. Specific rates vary materially by traffic source (paid social typically resolves higher than organic search), audience profile (consumer beats B2B), and time of day. The platform reports the actual resolution rate per traffic source so the team can see the math on their own site rather than relying on a category average.
For each resolved visitor: full name, postal address, email, phone, plus around 70 demographic fields covering household composition, income tier, age range, lifestyle and interest signals, homeowner status, and behavioral context from the visit itself (pages viewed, time on site, exit page, return visits). The exact fields available depend on the consented data layered into the resolved record — the platform returns whatever the identity graph holds for that household.
Three options. (1) Run campaigns directly on DirectMail.io — mail, email, SMS, Meta — and we do the activation. (2) Push the resolved identities into a connected web-to-print workflow for printers and agencies running their own production. (3) Push the resolved identities into your CRM, marketing automation, ad platforms, or BI stack via API, webhooks, or SFTP — you activate on your own stack. Mix-and-match is fine: many customers use a CRM push for digital activation and DirectMail.io for the mail piece.
Yes. 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 stricter privacy postures, the pixel can be configured to require explicit consent banners before signal collection — both modes are supported.
Trigger speed depends on the cadence configured. Common setups: same-day resolution and next-business-day press, 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 (cart abandon, pricing-page visit), faster cadences are available — same-day mail induction is supported when the print partner can hit the cycle.
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. They compose well: a visitor who fills out a form leaves an email; address appends fill in the address. A visitor who never fills out a form is invisible to address appends, and visible only to identity resolution. Most active customers run both.
Two common structures. Volume-based, priced per resolved identity returned (with rate cards that step down as monthly volume rises), is most common for marketers running steady programs. Outcome-based, priced as a share of attributed revenue, is offered for marketers running short cycles or testing the channel before committing. Both structures include the pixel, the resolution engine, and the data delivery layer. Activation costs (mail piece, postage, email send, Meta spend) are separate.
Yes. Many customers buy identity resolution as a data layer and run activation on their own stack — their CRM, their marketing automation, their print partner, their ad accounts. The platform is built to be modular at the data boundary. If the team wants the data and nothing else, that is a supported configuration.
Bring 30 minutes and a URL. We’ll walk you through the pixel, the data delivery options, and what your specific traffic mix is likely to resolve. No commitment.