Revenue
Revenue is the console suite for what your organization sells and for how EdgeKit answers when your site asks what a user gets. It holds two EdgeKit products and a set of shared screens:
- EdgeKit Paywall is the decision engine. You author features, the outcomes they return and the meters they count, and your site asks for a feature by name.
- EdgeKit Subscriptions is the catalog. You set up the products a grant gives access to, the offers you sell them through and the capabilities a product includes, and your site sells them.
- Shared holds the screens both use: segments, experiments, the fact registry and the decide log.
The screens
Section titled “The screens”The suite opens on Revenue › Dashboard, your organization’s console home. It shows the latest entries in your deployment log and, where available, traffic to your sites over the last 30 days.
The Catalog group belongs to EdgeKit Subscriptions:
- Revenue › Catalog › Products
- Revenue › Catalog › Offers
- Revenue › Catalog › Capabilities
The Billing provider group, marked Prototype in the console, also belongs to EdgeKit Subscriptions. Its four screens are read-only. See Read your billing provider’s records.
The Decision Engine group holds three EdgeKit Paywall screens:
- Revenue › Decision Engine › Features
- Revenue › Decision Engine › Outcomes
- Revenue › Decision Engine › Meters
The rest of the Decision Engine group is Shared:
- Revenue › Decision Engine › Experiments
- Revenue › Decision Engine › Segments
- Revenue › Decision Engine › Facts
- Revenue › Decision Engine › Observability
How a decision reads the suite
Section titled “How a decision reads the suite”Your page or your server asks decide for one or more features by name. For each feature, EdgeKit reads facts about
the request, the user and the grants they hold, walks the feature’s canvases in order and returns one outcome. Your
site switches on the outcome’s id.
Each screen supplies part of that answer. A product says which sites a grant covers, a rule in a canvas tests facts, segments, experiment arms and meters, and the outcome is what the winning rule returns. Facts lists everything a rule may test, and Observability shows what was answered.
Draft and deployed configuration
Section titled “Draft and deployed configuration”Everything you author in Revenue is part of your organization’s draft, including products, offers, capabilities, features, outcomes, meters, segments and experiments. Requests are answered from the deployed document, so a change reaches your sites after the next deploy, not when you save it. The exception is what a user’s grants say: decisions read a product’s sites, slug and rank, and an offer’s audience, as saved. See Versions.
What users and systems produce does not wait for a deploy: users, grants, records synced from your billing provider and meter counts are written as they happen.
Who can change it
Section titled “Who can change it”| Role | Read every Revenue screen | Author catalog and decision records | Read the decide log |
|---|---|---|---|
| Owner | Yes | Yes | Yes |
| Admin | Yes | Yes | Yes |
| Developer | Yes | Yes | Yes |
| Editor | Yes | No | Yes |
| Member | Yes | No | Yes |
Deploying is a separate permission. See Who can stage and deploy.