The right version for each visitor, in real-time.
qbrix works out what works for each kind of visitor, and applies it to the request in front of it. No segments built in advance, no overnight job, no profile to look up.
Optimize the experience of each visitor. Let qbrix continuously optimize the customer
experience for each of your segments.
One experiment, many answers — qbrix picks the right one per visitor.
Say what you know. Nothing more.
Whatever you already have on the request — their device, whether they have been here before, what is in the basket — travels with the call. Nothing is set up beforehand, and nothing has to be kept in sync.
# whatever you already have on the requestresult = client.agent.select(experiment_id="checkout-cta",context={"id": user_id,"properties": {"device": "mobile", "returning": True, "cart_value": 84.00},},)# nothing declared in advance, nothing kept afterwards
You never have to name a segment.
You never tell qbrix that evening mobile shoppers are a group. It works out which combinations of what you send actually change the answer — including ones you would not have thought to look for.
Three properties, twelve kinds of visitor — and you listed none of them. It is not limited to these twelve either: a basket of 49 and a basket of 51 are not two boxes, they are two numbers.
There is no profile to build.
qbrix keeps no copy of your visitors. What you send arrives with the request, makes that one decision, and goes into the event record — kept for ninety days, and then gone.
It works before you know anything about them.
A logged-out first-time visitor has no history and nothing worth sending. They still get a decision — the best one qbrix has for someone it knows nothing about. Send more when you have more.
{ }You know nothing at all. They landed from a search result.
{ "device": "desktop" }One thing. It is enough to change the answer.
{ "device": "desktop",
"returning": true,
"cart_value": 212.00 }Now you have three things, and none of them came from a profile.
You are never waiting to have better data before you can start. Add a property the day you have one.