Provable · the receipt

Live demo — site × scenario × rendering

Proves: each variant is injected onto the live-cloned page where it maps, carrying the data it used and its surface policy. Open one to drill into its receipt.

Scenario B · identity key: Email + name + your CRM history

Matched to your CRM + an append — all eight segment families are live.

available data: CRM lifecycle / LTVpage & email behaviourdeclared goalPDL: title / historybroker income (buy)

B1 Welcome-back resume ↑ reactivation

Maps to Hero · data used 1 CRM: first bought in 2023 · First-party (CRM / behaviour) · say 2 last-viewed item · First-party (CRM / behaviour) · allude 3 lifecycle: customer · First-party (CRM / behaviour) · say

say + allude. Drill into the receipt →

B2 Tailored-offer module ↑ paid_conv

Maps to Offer / CTA · data used 1 declared name · Declared by the visitor · say 2 price-page visits · First-party (CRM / behaviour) · allude 3 modeled income · Broker append · hold

say + allude; income HOLD (steers, never shown). Drill into the receipt →

B3 Prestige / peer hero ↑ lead_to_app

Maps to Hero · data used 1 PDL seniority · Enrichment (PDL) · allude 2 PDL industry · Enrichment (PDL) · allude

enrich · allude. Drill into the receipt →

Blocked variant · Bx · Income-recite (ungated) · maps to Offer / CTA

“On a $190K income, Gauntlet AI is an easy yes, Maya.”

HOLD — blocked by surface policy; the bandit cannot pull it. It would win on engagement, but it relies on a hold fact, so it is kept out of the action pool — the optimizer can never select it. Open it, greyed →