Turn anonymous traffic into identified visitors sent through your flows
Browser privacy rules strip out most of your site traffic before your marketing tools ever see it, so real shoppers — including people already on your list — browse, add to cart, and leave without ever triggering a flow. Contextual runs tracking on a subdomain of your own domain and resolves anonymous sessions against an identity graph, then writes the enriched event into Klaviyo, Attentive, or Redo Email & SMS. It builds a parallel set of flows that only send when your native flow didn't, so every dollar it produces is revenue you weren't going to get.
Someone views a product, adds to cart, or starts checkout. Privacy browsers block the third-party scripts your stack relies on, so the session lands in your analytics as an unknown visitor — even when that person is already a subscriber.
Contextual identifies them
Tracking runs from a subdomain of your own domain, so the cookie is first-party and persists for a year instead of the seven days a script-written cookie survives in Safari. Sessions we can't match from your own data are resolved against an identity graph that returns email, phone, name, and address.
The event lands in your marketing platform
The resolved profile and the browse, cart, or checkout event are written into Klaviyo, Attentive, or Redo Email & SMS as a Contextual-specific metric, and forwarded server-side to Meta, TikTok, and Google alongside your existing pixel.
A flow fires only if yours didn't
Contextual builds a duplicate of your abandonment flows keyed to its own metrics, running on a delay. If the shopper would have entered your native flow, the Contextual flow is suppressed. It only ever sends to someone your stack couldn't reach.
Why Contextual is different
Two tools, one line item
Event forwarding tools move your events server-side past the blockers, but they don't tell you who the anonymous visitor was. Identity tools do the opposite. Contextual does both jobs in one integration, including the server-side forwarding that lifts your Meta Event Match Quality score.
First-party by default
Contextual runs on a subdomain of your own domain, so a shopper who identified themselves stays recognized for a year, not seven days. Your own customer data accumulates instead of resetting to a third-party lookup every visit.
Incrementality you can audit
Contextual's flows are suppressed for anyone your native flows would have caught. Open your Klaviyo flow list, filter to the Contextual flows, and read the revenue column. That number is incremental by construction, not by attribution model.
You control the reach
Subscribers always get their flow. For identified visitors who never subscribed, you decide how many go through — high-confidence only, or wide open. Most tools are fixed at one end of that range; yours adjusts any time.
How it fits in the platform
Returns information is a gold mine of data about your customers that can be used across the whole company. Pairing returns directly with other products allows you to create a more personalized experience for each buyer.
We've received your request and will be in touch within one business day.
Something went wrong — please try again.
Sign Up for Redo Updates
Thank you!
We've received your request and will be in touch within one business day.
🇺🇸 ▾
Something went wrong — please try again.
By clicking Submit, I agree to receive promotional messages from Redo via email, text, or phone. I can update preferences via email link or by texting STOP. Reply HELP for support. Msg & data rates may apply, frequency of message varies.
Request a demo with your info below
Thank you!
We've received your request and will be in touch within one business day.