Skip to main content

A/B Testing: Results

Once an experiment (see Create An Experiment) is active and taking traffic, use these endpoints to monitor it. Both routes below live under /analytics/ and require $TENANT_HEADER in addition to $AUTH_HEADER — see Environment setup.

Experiment Results

Runs a statistical significance test (two-sample z-test on expected value, or plain auth-rate when the experiment is auth-only) between the control and variant arms.
Optional query parameters: start_ms, end_ms, min_sample_size, guardrail_threshold_pp, evaluation_margin — override the experiment’s stored thresholds for an ad-hoc window or sensitivity check.

Verdict Values

For an auth-only experiment (no cost data / multi-objective involved on either arm), the significance test collapses to a pure auth-rate z-test and cost-related fields (total_cost_saved, avg_cost_saved_bps, net_ev_bps, net_delta_bps) are null.

Experiment Transactions

Paginated per-transaction log — which arm each payment landed in and its outcome. Useful for spot-checking arm assignment or debugging a specific payment.
page_size is capped at 100. Optional start_ms narrows to a time window.

Enabling Real-Payment Interception

A newly created experiment does not affect live traffic until real-payment interception is turned on for the merchant:
See Merchant Features for the full feature-flag reference. Until this is enabled, /routing/evaluate still previews both arms for simulation purposes even though /decide-gateway traffic is unaffected.