Ekko explains a missed opportunity through five fields so protocol teams can reason about what happened, who was affected, what message should have existed, and what impact silence created.
Trigger
What happened?
The onchain or product state that should create a user or operator message.
Affected cohort
Who needed to know?
Wallets, accounts, users, cohorts, and operators connected to the event.
Expected notification
What message should exist?
The governed message, channel, pacing, suppression, approval, and provenance context.
Counterfactual action
What would action have changed?
The user, support, revenue, retention, trust, or security outcome the team wanted to influence.
Impact
What did silence cost?
The operational or commercial risk created when the message was not sent, suppressed incorrectly, or routed too late.
Current public evaluation path
Start in the hosted app, use the public developer page for API, webhook, and PWA bridge evaluation, or contact support for rollout-specific help.