One store. A page for every shopper.

Build audiences from 37 signals — the ad they clicked, what they searched for, their device, how often they've been back, or anything you know about them — and show each audience its own version of your store. Mtrix picks the version on the server, and returning shoppers keep the one they saw.

Start freeBook a demo

An illustration of five shoppers arriving at the same store. A shopper from an autumn Instagram ad on a phone matches the “Autumn ad — mobile” audience and sees the autumn edit. A shopper who searched for a reed diffuser sees a diffuser page. A returning visitor sees what is new. A gold loyalty member sees early access. A shopper who matches no audience sees the original page.

Shoppers arriving

37 signals.
Combine any of them.

Where they came from, the device they're on, how often they've been back, which experiments they've already seen, the page they're looking at, or a value your own store sends. Pick the signals, set the values, and you have an audience.

Everything you can target

All 37 options in the library, in the 8 groups you'll find them under.

  • Traffic Sources7

    Target users based on how they arrived at your site

    • Traffic Source
    • Traffic Medium
    • Campaign
    • Ad Content/Creative
    • Keyword/Term
    • Referrer
    • Ad Placement
  • Device & Technical6

    Target based on user's device and technical capabilities

    • Device Type
    • Browser
    • Screen Width
    • Screen Height
    • Connection Type
    • Language
  • Geographic4

    Target users based on their location

    • Country
    • City
    • State/Region
    • Timezone
  • User Behavior5

    Target based on user actions and engagement

    • Session Count
    • Pages in Current Session
    • Days Since First Visit
    • Returning Visitor
    • Previous Converter
  • Experiment History5

    Target users based on their experiment exposure

    • Experiments Seen
    • Variants Seen
    • Total Experiments Seen
    • Days Since Last Experiment
    • Saw Only Winning Variants
  • Page & Product Context5

    Target based on current page and product information

    • Page Type
    • Product Type
    • Product ID
    • Product Price
    • Funnel Name
  • Time-Based4

    Target based on time and date conditions

    • Day of Week
    • Hour of Day
    • Weekend
    • Date Range
  • Custom Attributes1

    Target based on custom user attributes

    • Custom Attribute

Give every audience
its own version.

Attach the audience to an experiment, build the page they should see, then choose: send all of them to it, or keep a control and measure the lift first.

  • Decided on the server Mtrix checks the audience and picks the version on the server, not with a script in the shopper’s browser.
  • The same page next time The pick is saved against the visitor for 30 days, so a returning shopper sees the version they saw before.
  • No flicker on Mtrix stores Stores built on Mtrix render the chosen version straight away. Other stores get the same with a server-side integration.
  • Experiences that don’t collide Add a “has not seen” rule for another experiment, and shoppers already in that one stay out of this one.

Show every shopper their page.

37 signals to build audiences from, a version of your store for each one, and the choice to serve it outright or test it against the original first.

Start freeBook a demo

Switching from another stack? Talk to us.

Build with Mtrix