Shared
EdgeKit Paywall and EdgeKit Subscriptions both build on four screens in the Decision Engine group:
- Revenue › Decision Engine › Segments holds named tests. A rule that needs the same test as another names the segment instead of repeating it. See Segments.
- Revenue › Decision Engine › Experiments splits devices or users into arms. A rule tests which arm the caller is in. See Experiments.
- Revenue › Decision Engine › Facts is the fact registry: every fact a rule may test, and where its value comes from. See Facts.
- Revenue › Decision Engine › Observability is the decide log: every decision EdgeKit answered for your organization, and every decide request it refused. See Observability.
Segments and experiments are decision records, like features, outcomes and meters. Facts and Observability are read-only.
Where segments and experiments are read
Section titled “Where segments and experiments are read”A segment or an experiment changes nothing until something names it:
- a rule in one of a feature’s canvases, which is where most are read (see EdgeKit Paywall);
- an experiment’s targeting;
- another segment.
A canvas entry may name a segment only if that segment reads no meter and no experiment arm. A product’s coverage reads content facts only, so it never names a segment or an experiment.
Rules every decision record follows
Section titled “Rules every decision record follows”- Names. Lowercase letters, digits and hyphens, starting with a letter or a digit, at most 200 characters. A
name is unique across every decision record, so a segment cannot share a name with an experiment, a feature, an
outcome or a meter. The screen flags a taken name before you save, and a save that reuses one is refused with
"<name>" is already taken by another decision record. - New records are left out. A new segment or experiment starts with Next deploy set to Left out. Set it to Included before you create it, or select Include in deploy on its screen when it is ready, then stage and deploy. Leave out of next deploy takes it back out.
- Saving changes the draft. Requests read the deployed document, so an edit, a rename or a delete reaches your sites at the next deploy. Leaving a record out is a draft edit too: it keeps answering until that deploy. See Versions.
- References are checked when you stage. Staging fails while a rule names a segment or an experiment that is deleted or left out of the next deploy, or an arm its experiment does not declare. Renaming a record does not rename the rules that name it, so change those rules in the same deploy.
Who can change them
Section titled “Who can change them”Owner, Admin and Developer can create, edit and delete segments and experiments. Editor and Member can read them. Every built-in role can read Observability. See Who can change it.
Questions about these screens are answered in the Shared FAQ.