Shopper Identification & Identity Resolution
Recognize the shopper. Before they log in.
Tie ID recognizes your site traffic and connects it to real shopper profiles across devices, browsers and email aliases, then pushes each one into the Klaviyo flows you already run.
ID de-anonymizes your highest-value web traffic — matching anonymous visitors to real profiles and syncing them to Klaviyo so you can email shoppers you'd otherwise lose.
Performance
Track how many shoppers Tie identified over time and where these profiles were sent.
| Audienceselect to filter chart | Status | Total | Destination: Google/Meta | Destination: Klaviyo | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Matches | New | Return | Matches | New | Return | Matches | New | Return | ||
Page View Visited any page | Active | 7,830 | 3,360 | 4,470 | 3,980 | 1,620 | 2,360 | 3,850 | 1,740 | 2,110 |
View Item Viewed a product page | Active | 5,210 | 1,840 | 3,370 | 2,540 | 920 | 1,620 | 2,670 | 920 | 1,750 |
Add to Cart Added item, no purchase | Active | 3,530 | 820 | 2,710 | 1,654 | 390 | 1,264 | 1,876 | 430 | 1,446 |
Started Checkout Began checkout process | Active | 1,890 | 420 | 1,470 | 892 | 198 | 694 | 998 | 222 | 776 |
Up to 70% of all shoppers
Start building shopper profiles from the first visit, not the email opt-in
95%+ of existing subscribers
Never lose shopper journey context because the shopper doesn't log in
Cookieless and cross-device
Server-side signals that persist across sessions
Double opt-in, privacy ready
On-site consent plus upstream partner consent
The same session. Two very different views.
Flip between what your ESP can see and what Tie ID resolves it to. Same visitors, same afternoon.
Cookies were never the identity layer. They were a workaround.
They're cleared, easily broken and don't survive jumps between devices. So most of your returning customers arrive looking brand new. Tie ID connects the dots with a 280M+ consented consumer identity graph.
Cookie-based tracking
Tie ID
Works without a cookie
No. Safari, iOS and privacy settings clear it
Yes. Server-side signals plus the identity graph
Cross-device
No. Phone and laptop look like two strangers
Yes. One profile per shopper, across devices and aliases
Share of traffic recognized
Roughly one in ten, only if they log in or click through
Up to 70% of all shoppers
Match method
Cookie present or not
Hybrid deterministic and probabilistic
Consent
Whatever the cookie banner allows
Double opt-in: on-site and Tie network consent
Who owns the data?
Depends on the vendor
You do. Tie is the processor, and every client is siloed
One shopper. Multiple signals. One profile.
A phone in private mode, a work laptop, a second email address and an old order look like four strangers without Tie.
synced to KlaviyoFrom an anonymous visit to a recognized profile.
No developer lift. Most brands connect Tie in a few hours.
A shopper lands on your site
Server-side signals from the session, such as device, IP and a hashed email are captured without relying on a cookie or login.
Tie resolves the identity
Deterministic identifiers link the session to one shopper profile across devices and aliases. Probabilistic models fill in the gaps.
The profile lands in your ESP
Profiles sync in real time, so abandonment and lifecycle flows fire for high-intent shoppers your ESP couldn't see.
Everything Tie ID does.
Identity is the foundation the rest of Tie runs on. Predict scores the profiles Tie ID resolves, and Priority protects the sends that reach them.
Cross-device resolution
One profile per shopper, whether they browse on a phone, buy on a laptop or use a second email.
Cookieless by design
Server-side signals plus proprietary probability models, so identification survives Safari, iOS and privacy settings.
Configurable match tiers
Choose how much traffic to ID. Recognize more or fewer shoppers depending on your use case and Tie's confidence in the match.
200+ attributes per profile
Demographic, contact and behavioral attributes on every resolved shopper, and on the lists you already have.
Real-time data sync
Website activity and platform data flow continuously between Tie and your ESP, so profiles and flows stay current.
Consent-first, siloed data
Double opt-in before any identification. You are the controller, Tie's the processor. No cross-client access, ever.
“The lift we see [with Tie] is amazing, but the customer journeys we're able to start are the real benefit. You can really drive focused messages to your user rather than continuing to blast out your evergreen messages.”
Kyle Turadek
Sr. Director, Growth & Ecommerce
$2.1M
H1 Tie revenue
6K
New orders
34x
Return on investment
.svg)
Add more shoppers to your existing flows.
Tie ID creates or enriches the Klaviyo profile. Your existing flows do the rest.
Abandoned cart, for anonymous shoppers
resolved profile → cart flow
Returning customers who never logged in now enter the abandoned-cart series with their history attached.
Browse abandonment
resolved → browse flow
Product-page visits from a recognized shopper trigger the browse flow instead of vanishing.
Welcome and post-visit nurture
first resolve → welcome
A first-time resolve starts the welcome series, with demographic attributes ready for personalization.
tie_id_sourceemail hash + devicetie_last_seen2 min ago · carttie_household_income$150K–$200Ktie_consentdouble opt-in ✓Common questions
How identification works, what it captures and how consent is handled.
All questions →How does Tie identify anonymous website visitors?
Most tools recognize a browser. Tie resolves the person. Every site visit leaves signals — server-side events, IP, device characteristics, behavioral patterns — and Tie matches those against a 280M+ consented consumer identity graph. When a deterministic match exists, we use it. When one doesn't, proprietary AI extends recognition probabilistically to visitors other tools drop. When the match clears your confidence threshold, the shopper's profile is created or enriched in your ESP.
Tie resolves returning visitors across IPs, devices, browsers and email aliases using a proprietary network of 1,000+ data sources, and because nothing depends on a browser cookie, identification survives Safari, iOS and privacy settings. The payoff is continuity: the same shopper is recognized as the same shopper across devices, sessions, and months, instead of entering your database as a new person every time they come back on a different phone. In practice that lifts identification from roughly 10% of your shoppers to as much as 70%.
What information can Tie identify about website visitors?
Tie can identify a wide range of information about your website visitors—from details like name and contact information to enriched insights such as age, gender, household income, and marital status. It also captures detailed website activity and determines whether a shopper is already a customer or exists in your CRM, and predicts how likely they are to engage with future marketing—giving you a more complete view of how each individual engages with your brand.
Does Tie use deterministic or probabilistic matching?
Both. Every match is deterministic to the household: verified emails, hashed identifiers and order history tie the session to a known home. The probabilistic layer then works out which person in that household is browsing, for example one partner rather than the other, and a profile only syncs once the match clears your confidence threshold.
How does Tie handle identity resolution across devices and sessions?
Tie links different identifiers—like IP address, email, cookies, and device IDs—to a single shopper profile using consented data, all within each client's own siloed environment. This allows Tie to recognize the same person across devices and sessions, whether in real time or through batch enrichment. Each match includes confidence and recency signals, helping ensure accuracy while maintaining a unified view of the customer.
What is Tie's real-time match rate?
Tie can recognize up to 70% of U.S. website visitors in real time, against roughly one in ten for a typical ESP. Flexible controls let you set your own thresholds for data quality and match confidence, so you decide which shoppers are suitable for ad audiences versus your Klaviyo database.
How often is Tie's identity data refreshed?
Tie's data is updated on a near real-time basis. Your website activity and platform data flow into Tie without interruption, with incremental updates roughly every 10 minutes. Tie is not a data co-op: your customer data is never pooled with or shared across other brands. Third-party enrichment attributes refresh on their providers' cycles against our enforced recency standards, and you can filter audiences by data recency at any time.
Can Tie enrich existing CRM or email lists?
Yes. Connect your ESP and Tie enriches your existing profiles in place — mailing addresses for direct mail, plus demographic attributes like household income, gender, and marital status. Because enrichment runs against live profiles instead of a static file, attributes keep filling in and updating as shoppers return, so your segments stay current rather than aging out from the day of a one-time upload.
See what Tie finds on your site.
A 20-minute walkthrough on your own traffic — positive ROI within 30 days.
Identity, intent and inbox placement for ecommerce brands, inside the tools you already run.
Klaviyo Preferred Tech Partner