Analytics & Metrics·Updated Aug 21, 2026
Revenue Tracking
Connect call performance to revenue outcomes and deal metrics.
Revenue Tracking Is Live
Kendo connects analyzed calls to real sales outcomes. A call can store deal size, cash collected, deal date, notes, attendance, and outcome, with optional CRM context and a linked Stripe or Whop payment.
The result flows into the call page, team analytics, payment-assignment workspace, Slack reporting, webhooks, and API-driven workflows.
Record a Deal from a Call
- 1. Open an analyzed call and choose Add deal or Update deal
- 2. Record the deal size, cash collected, deal date, outcome, attendance, and any notes
- 3. If Stripe or Whop is connected, choose a suggested payment or search by customer, amount, or date
- 4. Save the update and confirm the revenue card reflects the correct source
- 5. Correct or remove the link later if the payment belongs to a different call
Stripe and Whop
Stripe uses a restricted read-only key with Charges and Invoices read access. Kendo rejects full secret keys and cannot move money.
Whop imports company payments read-only from the connected company API key.
Kendo periodically refreshes the payment cache, ranks likely matches using date and call/deal context, and prevents one payment from being attached to two calls. Automatic matches are labeled; managers can always review or change them.
Revoked or rotated credentials show a reconnect state in Integrations. Disconnecting stops future sync without deleting the provider's payment records.
How Analytics Are Calculated
- Win rate uses calls with a recorded won or lost outcome; a linked Stripe/Whop payment or positive manual cash also counts as a winning outcome
- Cash collected sums linked payments and manual revenue collected for calls in the selected period
- Average deal size divides revenue on won calls by the number of won calls
- AI-estimated deal values are contextual forecasts and are not counted as collected cash
Use the metric help text and sample size to understand which calls contributed to each figure.
HubSpot Context
The team-scoped HubSpot beta connection reads contacts, companies, deals, pipelines, and owners to enrich matching calls. When Kendo has a confident match, the call page can show a CRM snapshot and deep links, and can prefill an empty deal form.
HubSpot enrichment is exact-or-abstain: ambiguous records remain unresolved instead of silently attaching the wrong contact or deal. Existing snapshots are not replaced with a different deal without surfacing the conflict.
The connection is read-only unless a separate workflow explicitly writes data through another system.
API and Webhook Support
Push API can create the call and optional deal data in one request using deal.dealSize, deal.revenueCollected, deal.dealDate, and deal.notes (camelCase and snake_case aliases are accepted).
Subscribe to payment.linked when collected revenue is attached to a call and deal.outcome.updated when deal or outcome information changes. Verify every delivery with the Kendo signature before processing it.
Data Quality Checklist
Revenue dashboards are only as complete as the recorded outcomes and payment links.
- Review the unlinked-payments queue regularly
- Resolve rep email aliases so calls belong to the right person
- Record both wins and losses, not only successful deals
- Avoid entering forecast value as cash collected
- Move a payment link instead of duplicating the same revenue manually