How Commerce Gate reports metrics

Source, scope and freshness

The site reads Decionis's public metrics endpoint, which supplies the totals, a privacy flag, commerce-surface names and when they were generated. The site does not rebuild the ledger or audit those totals.

The response is cached for five minutes. If the source is unavailable, the last response can stay visible with its timestamp; without usable figures, the band is hidden. Check the 'as of' date before reusing a number; documentation review dates are separate from it.

• Decionis public metrics source

  Product-reported aggregate data and generation timestamp, not an independent customer study.

Governed decisions: cumulative ledger evaluations

The count reads protocol_transaction_ledger_decisions, falling back to totalDecisions. It counts every evaluation recorded to date across the Decionis platform, favorable or not, and is not limited to Commerce Gate orders.

One order can have several evaluations, so the count is not unique orders, active customers, settled transactions or billable actions. The site uses the ledger's own counting rules and adds no deduplication of its own.

Transaction value, exposure and reporting periods

Transaction value is the amount on the action being checked, so it describes exposure before anything completes. A sum of checked actions is not a sum of settled sales.

The money tile reads restrained_spend_usd_30d: the USD value on rejected, held or escalated decisions in the last 30 days. It covers that window only, while the governed-decision count runs to date; no all-time value total is published.

Exposure shows only when privacy_threshold_met_30d allows it and there is a usable positive amount, rounded down to whole dollars. Otherwise it is left out, never shown as zero. The source owns currency conversion and valuation; the site converts nothing.

Commerce surfaces with recorded decisions

Surface names come from the source's surface_names_by_domain.commerce list: the commerce surfaces where decisions were recorded, across environments. The site keeps the source's names and order, minus empty or duplicate names.

A recorded surface does not prove a current store connection, a public release or that the platform can stop actions. Use integration status and the capability matrix for those.

Public metrics are separate from billing

A billable governed action is one checked commerce action while enforcement is on. Shadow Mode is never billed. The Walmart ship and cancel actions your operator confirms are logged but not metered; a Walmart refund checked against your policy is a governed action.

Your plan's included actions and overage rate set your bill, and your workspace's usage records reconcile it. The public ledger count is not an invoice counter.

• Governed-action plans and overage rates

  Published pricing and billable-action definitions.

How evidence is labelled

Product-reported data names its source, population and reporting period. Illustrative examples show how a policy might work, not customer results. Platform facts cite the platform's own documentation. A customer result needs a named source who agreed to it and an explained measurement; an estimate states its assumptions.

Rejected, held or escalated exposure is not savings: Shadow Mode stops nothing, and a held action may later be approved. Showing prevented loss or real savings would need execution, financial and comparison evidence these totals do not include.