GLOSSARY

What is a decision layer?

A decision layer is the part of a marketing stack that chooses, per visitor and in real time, which experience a page renders. It sits between traffic and site, scoring in-session behavior and selecting among authored variants. It is distinct from the content supply chain, which produces the variants but does not choose between them.

The half of the problem most tools skip

Most "AI personalization" tooling competes on the supply-chain half: generating variants faster, keeping brand voice consistent, routing assets to channels. That work is upstream and batch — it happens on your schedule, in bulk, before any visitor arrives. The decision is the other half: runtime and per-visitor, in the few hundred milliseconds after someone lands, with one shot to get it right. A warehouse full of beautifully produced variants converts nobody if nothing is choosing between them intelligently in the moment.

Properties of a real decision layer

Four tests. It decides at runtime, per visitor — not by executing pre-written audience rules on a schedule. It works on anonymous traffic, since most visitors are anonymous and a decision layer that needs a resolved identity forfeits the majority of its decisions. It is deterministic — same behavior in, same experience out, no model improvising in a path that runs thousands of times an hour. And it measures itself against an always-on holdout, so the lift it produces is proven rather than asserted.

The evaluation question that separates decision layers from supply-chain tools: where does the decision happen, and when? "We generate the variants and you wire them into your existing system" means the deciding is still your problem.

QUESTIONS PEOPLE ASK

Is a decision layer the same as an A/B testing tool?

No. An A/B testing tool splits traffic randomly to learn which variant wins on average, then everyone gets the winner. A decision layer chooses deliberately per visitor, based on that visitor's in-session behavior, so different visitors see different experiences by design. Testing tells you which single experience is least bad for everyone; a decision layer stops asking one experience to fit everyone.

Does a decision layer need a CDP?

No. A decision layer scores the current session's behavior — pages, scroll, dwell, sequence — which requires no unified customer profile and no identity resolution. A CDP serves cross-session, known-customer use cases like lifecycle email; putting one on the critical path of an in-session decision adds latency and an implementation project without improving the decision.

Should an LLM make decision-layer decisions?

No. The live decision runs thousands of times an hour with revenue attached; it should be deterministic, reproducible, and free of inference cost. Language models belong upstream — drafting variants, configuring segments, analyzing results — where their output is reviewed before it reaches a visitor. In the runtime path, a probabilistic model adds cost, unpredictability, and a standing evaluation burden.

KEEP GOING
Your "AI personalization" stack is solving the wrong half of the problemWhat is an agentic experience layer?The AXO decision layer
See the agentic experience layer on your own traffic.
One tag, live in about 15 minutes.
Start free trial →
MORE FROM THE GLOSSARY