The words this platform uses, defined once.
Some of these terms are ours — User Barcode, Product DNA, held back. Where we invented a word, this page says exactly what it means, so nothing on the rest of the site has to be taken on trust.
User Barcode™
A pseudonymous fingerprint of how one customer decides — 24 dimensions such as occasion sensitivity, budget discipline and repeat cadence. It carries no name, address or payment detail, and it cannot be reversed into a person by us. Re-identification is your key to hold.
where it is used →Product DNA
The structured, validated attributes of one product — the facts every engine reads. A fact corrected once improves every module that depends on it, which is why catalogue work compounds.
where it is used →Product Intelligence Score
A 0–100 readiness number per product, with the missing fields named rather than implied. 84 means structured and comparable; the gap to 100 is a specific list of absent attributes.
where it is used →Decision
One request that returns a chosen option, a score and a reason. It is also the billing unit: one decision, one charge.
where it is used →Reason
The short human-readable string returned beside the score, assembled from the exact dimensions that produced it. It cannot disagree with the decision it describes because it is built from the same inputs.
where it is used →Counterfactual
The companion to a reason: what would have changed the answer. “If the budget ceiling had been higher, the premium tier wins.”
where it is used →Held back
A request that returns no recommendation because confidence fell below the floor, consent did not cover the signals, or the catalogue record was incomplete. Held-back decisions are never charged.
where it is used →Confidence floor
The minimum score at which the system is willing to answer — 0.60 by default. Raising it trades coverage for certainty; lowering it does the opposite.
where it is used →Holdout
A share of traffic deliberately shown the status quo so lift can be measured rather than asserted. Pilots run 50/50; production drops the control to 10%.
where it is used →Incremental vs influenced
Incremental is the difference against the holdout. Influenced is every outcome a decision touched. Only the first is called lift on this site.
where it is used →Engine
One service in the decision path with a fixed contract — intent, identity, context, matching, ranking, explanation, constraint, pricing, content, learning. Ten exist; which ones run for you depends on your tier and bindings.
where it is used →Binding
The link between an account and an engine. Binding adds that stage to the account’s routing table; it never grants access to another tenant’s data.
where it is used →Module
What you buy: Catalogue Intelligence, Product Intelligence Score, Content & GEO Studio, AI Visibility Monitor, Conversational Commerce, Revenue Intelligence. Modules are commercial; engines are computational.
where it is used →Surface
Where a decision is delivered — storefront, assistant, API direct, console. The same core answers all of them, which is why the answer does not change between channels.
where it is used →Overage
Decisions served beyond the tier allowance, metered at the tier rate and shown as a separate invoice line. It never interrupts serving.
where it is used →Tier
Launch, Expand or Enterprise. A tier sets included volume, the overage rate, which modules and engines are entitled, and the support commitment.
where it is used →