Tie + Elevar, now Audiense Online · Different jobs, one shared seam

Elevar keeps your data clean.
Tie makes your audience bigger.

Elevar, now part of Audiense Online after its acquisition into the Audiense portfolio, is server-side conversion tracking: it makes sure the events from the shoppers you already have reach Meta, Google, and Klaviyo reliably. Tie's job starts where that one ends: Tie ID identifies the anonymous shoppers tracking never names, Tie Predict scores who is ready to buy, and Tie Priority makes sure the message is seen. Most brands can run both. But the two products do overlap in one place, shopper identification, and if that’s what you want, here’s why Tie should be your top choice.

up to
0
%

Tie ID identifies up to 70% of all site traffic

+
0
%

Portland Leather Goods grew campaign revenue 18% with Tie Predict

+
0
%

OluKai grew revenue per send 55% with Tie Priority

 Past the plateau
Different jobs
01 — Different jobs

Elevar works on your data.
Tie works on your audience.

Elevar's bread and butter is tracking infrastructure: server-side conversion events, Conversion API plumbing, a clean data layer. It is genuinely deep in that lane, and Tie does not do that plumbing. If your problem is "our event tracking broke after iOS 14," Elevar is a fine answer, and nothing on this page argues otherwise.

Tie answers a different question: who is actually on your site, when are they ready to buy, and will messages you send them be seen? Tracking measures the shoppers you already know. Tie also grows the audience itself, scores it, and delivers to it. Different jobs, which is why plenty of brands run both, and why the comparison that matters is the one seam the two products share.

02 — The one seam: identification

Both products identify shoppers.
Only one finds you new ones.

Elevar's Session Enrichment reconnects returning shoppers to the profiles you already own, so more Klaviyo flows fire. That’s useful, and why Tie does the same thing: it recognizes 95% of returning shoppers across sessions and devices. The difference is everyone else. Roughly nine in ten visitors never identify themselves, and re-recognition cannot reach them by design. Tie ID resolves that anonymous majority into net-new contacts, up to 70% of all site traffic, each with 200+ Tie Attributes. If identifying shoppers is the priority you are buying for, this is the seam that decides it.

The share of your traffic each product can identify

Every bar below is 100% of your site traffic. Returning shoppers make up roughly a third of it, and that third is the only part a re-recognition tool can ever work with. Klaviyo natively recognizes ~27% of returning shoppers, about 9% of all traffic. Elevar's Session Enrichment lifts identifiable returning-shopper events by 50%, per Elevar's own documentation, reaching ~40% of returning shoppers, about 13.5% of all traffic. Tie recognizes 95% of returning shoppers, about 30% of all traffic, and then Tie ID keeps going into the anonymous majority, identifying up to 70% of everything.

Returning shoppers ≈ 33% of traffic · re-recognition stops here
Klaviyo, out of the box — the baseline
~9% of all traffic
9%
Natively recognizes ~27% of returning shoppers. Everyone else browses as a stranger.
Elevar Session Enrichment
~13.5% of all traffic
+50%
A 50% lift in identifiable returning-shopper events, per Elevar's own docs: ~40% of returning shoppers. Real, and still confined to the returning third.
Tie
up to 70% of all traffic
95% of returning ≈ 30%
+ the anonymous, identified by Tie ID
Tie recognizes 95% of returning shoppers, then Tie ID crosses the line no re-recognition tool can: net-new identification of the anonymous majority, up to 70% of everything.
0
%
of all site traffic identified by Tie ID (up to)
95%
of returning shoppers recognized across devices
200+
Tie Attributes attached to every identified shopper
net-new
contacts added to Klaviyo, not just events stitched

Keep the tracking clean with whichever tool you trust. But when the goal is a bigger identified audience, re-recognition is a feature; identification is Tie's bread and butter.

03 — Recognition, proven

Recognition at platform scale.
With a holdout to prove it.

Beekman 1802 didn’t need more visitors. They needed to recognize the ones they already had so that they received the right messages for their stage in the lifecycle, the exact job re-recognition is hired for.

Tie surfaced 100K+ returning shoppers Klaviyo was treating as strangers and routed them back into existing flows, without touching deliverability.

$
520,947
net revenue recovered in 3 months
4,754
new orders from reactivated profiles
108,647
returning shoppers reactivated
These numbers are measured against a holdout, not credited by attribution.
More flows firing is easy to show and hard to trust: not every recognized shopper who later buys was caused to buy by the recognition. A holdout is the only way to tell attribution from lift, hold a control group back and measure the net-new revenue the recognized group produced that the control did not. Tie's proof of value is a holdout-based incrementality report, not a self-reported multiplier. Whichever identification tool you choose, ask how its revenue number was measured.
04 — Beyond identification

An identified shopper is the start.
Tie ships the layers that turn them into revenue.

Identification tells you who’s there. Revenue comes from what happens next, and these are the layers that come with Tie's platform, alongside your existing stack rather than in place of it. Each one below is a live customer result.

Attributed revenue

New & returning contacts, with 200+ attributes each.

Tie identifies up to 70% of all site traffic and attaches 200+ Tie Attributes to every identified shopper: demographics, financial and property signals, purchasing behavior, interests. Enough to segment and personalize, not just to fire an event.

up to 70%
of site traffic identified
200+
attributes per shopper
Know when · Tie Predict

Know who’s ready, not just who converted.

Tracking tells you what happened after the send. Predict tells you who to send to beforehand. Portland Leather Goods was seeing diminishing returns from sending more emails. With Tie Predict they focused sends on the shoppers ready to buy now, and campaign revenue increased 18%.

+18%
revenue per campaign (Portland Leather Goods)
Get seen · Tie Priority

Identified isn’t connected.

A bigger list only pays if the messages land. Tie Priority moved OluKai's sends into the Gmail Primary inbox in 24 hours; across dozens of A/B tests the placed variant lifted revenue per send 55% and click-through 42%. And when Twillory's sender reputation crashed before the holidays, Priority restored 100% inbox placement and took their Postmaster score from Medium back to High in weeks.

+55%
revenue per send (OluKai)
100%
placement restored (Twillory)
Any revenue being driven off our Tie emails means it was missed by Elevar. We literally would not have that revenue otherwise.
CRM & CX Director
05 — Who does what

Two products, one comparison.
Overlap in one place.

Here’s where each product is strong, and where they meet. Elevar owns the tracking lane. Tie owns the audience lane. The seam between them is identification.

Tie

The audience platform

Tie ID identifies up to 70% of all traffic as net-new contacts, each with 200+ Tie Attributes
Returning-shopper recognition covered too: 90%+ recognized, 108,647 reactivated at Beekman 1802
Tie Predict scores buy-readiness per shopper, per campaign, before the send
Tie Priority lands sends in Gmail Primary and repairs sender reputation when it slips
Holdout-measured proof, incrementality reports, not self-reported multipliers
&
Elevar · part of Audiense Online

The tracking layer

Server-side tracking and Conversion API plumbing, genuinely deep, a lane Tie does not enter
Clean data layer and event delivery to Meta, Google, Klaviyo, and 40+ destinations
Session Enrichment re-recognizes known shoppers, the one place the products overlap; it adds no net-new contacts
No predictive scoring and no inbox placement or reputation product, those layers come from elsewhere in the stack
Now one product line inside a portfolio, acquired by Buxton and folded into Audiense as Audiense Online

Running Elevar and happy with it? Keep it. Tie isn’t asking for that slot.

Tie runs alongside your tracking stack: one integration, and the audience, scoring, and placement layers switch on without touching your event plumbing. And if what you are actually shopping for is shopper identification, buy the product where identification is the whole point, not a feature. Run Tie next to your current setup and measure the lift against a holdout. Nothing to rip out to find out.

The bottom line

Keep your tracking clean.
Make your audience bigger.

Elevar does the first job well, and Tie does not compete for it. The second job, identifying the anonymous majority, knowing when they are ready to buy, and landing the message where it gets seen, is what Tie was built for. If identifying shoppers is your priority, that is the choice this page is about.

up to 70
%

of site traffic identified
(Tie ID)

+
18
%

campaign revenue
(Portland Leather Goods, Predict)

+
55
%

revenue per send
(OluKai, Priority)