Outcomes
Outcomes
- Sync revenue/refund outcomes into scorecards.
- Capture conversion evidence without requiring a browser session.
- Expose provider-spend reconciliation posture to operators.
Workflow
Make revenue evidence part of the next decision.
Nina treats revenue, refund, conversion, and publication outcomes as learning signals that should affect future product-class and channel choices.
commerce operatorsgrowth teamsAI workflow owners
Proof points
Proof points
- Store revenue/refund outcome endpoints feed evals and memory.
- Conversion webhooks support direct secret and timestamped HMAC signatures.
- Provider spend settlement can surface matched, variance, and unmatched posture.
Operator checklist
What a serious implementation should verify
- Attach product class and channel to evidence ids.
- Sanitize webhook/evidence metadata before retention.
- Track refunds as negative learning signals.
- Review spend variance before scaling paid execution.