Traffic Sources
How they arrived
Traffic SourceTraffic MediumCampaignAd ContentKeyword / TermReferrerAd Placement
Target the right visitor by anything you know.
Reach shoppers by who they are, where they are, and what's happening around them — 37 signals, from referrer and geography to their local time of day and the experiments they've already seen. Every visitor is bucketed on the server, before the page paints.
Target on 37 signals, not the usual six.
Most tools hand you geography and device and call it targeting. Mtrix reads the whole visitor — how they arrived, where and when they’re shopping, what they’ve done before, and even which experiments they’ve already seen.
37 signals
8 categories
0 lines of code
Geographic
Where they are
CountryCityState / RegionTimezone
Device & Technical
What they’re on
Device TypeBrowserScreen WidthScreen HeightConnection TypeLanguage
User Behavior
What they’ve done
Session CountPages in SessionDays Since First VisitReturning VisitorPrevious Converter
Experiment History
rare
What they’ve already seen
Variants SeenExperiments SeenTotal Experiments SeenDays Since Last ExperimentSaw Only Winning Variants
Page & Product
What they’re looking at
Page TypeProduct TypeProduct IDProduct PriceFunnel Name
Time-Based
local time
In the visitor’s local time
Hour of DayDay of WeekWeekendDate Range
Custom Attributes
bring your own
Anything your store knows
Loyalty tierInventory levelWeather feed…anything you pass
Every signal is a condition you compose yourself — no tracking plan to rebuild, no developer to wait on. Weather, loyalty tier, or anything else your store knows drops in as a Custom Attribute and targets like the rest.
Bucketed on the server. No flicker.
Client-side tools load the page, run a script, then swap the content — and the shopper sees the flash. Mtrix decides who gets what on the server, so the page arrives right the first time.
-
Decided before the page responds
Mtrix matches the audience and picks the variant inside the API request — before a byte of HTML comes back. The shopper sees the right experience first, never a flash of the wrong one.
-
No client-side latency tax
There’s no blocking script in the browser waiting to decide who gets what. Nothing to download and evaluate before the page can render — pages still load in under two seconds.
-
Precise, without the pixel sprawl
Targeting is evaluated on the server against the incoming request. No second tracking script, no tag-manager detour, no visitor data shipped around to make the call.
Client-side tools
Page loads
Script runs
Content swaps
Flash of the wrong page
Mtrix · server-side
Request
Server picks variant
Page paints once
Right the first time · zero flicker
The variant is chosen inline with the request — no extra round-trip, no client wait.
Overlapping tests that never collide.
Most platforms make you buy an add-on or wire up exclusion groups to keep experiments from interfering. Mtrix does it for you — and turns a visitor’s history into a targeting signal along the way.
-
Overlapping tests, never contaminated
Put two experiments on the same page and Mtrix keeps each visitor in one or the other. Results never bleed together — cleaner data, no exclusion groups to configure, no engineering to coordinate.
-
A visitor’s variant becomes a signal
Whichever variant a visitor was bucketed into is itself something you can target on. Greet the new-checkout group with a matching offer, or exclude anyone who saw the pricing test — it’s just another condition.
Pricing test
Running
Control
Variant Bassigned
Variant C
assignment becomes a signal
Checkout redesign
Audience
⚗
Variants Seen
has not seen
Pricing test / Control
⚗
Variants Seen
has seen
Pricing test / Variant B
One visitor · one experiment · zero contamination