Revenue
Connect Stripe and the behaviour gets a price tag.
Stripe connected, and a broken checkout is measured in dollars.
Read the connectors docs- KPI tile
- Revenue joins the range
- MRR · LTV
- Sortable visitor columns
- Weekly
- A monetization section
- Agent context
- Weigh a bug by account
Clado
Olive
Codebuff
Attensira
Assemble
Opennote
Stratify
Gatekeep- Clado
- Olive
- Codebuff
- Attensira
- Assemble
- Opennote
- Stratify
- Gatekeep
- Clado
- Olive
- Codebuff
- Attensira
- Assemble
- Opennote
- Stratify
- Gatekeep
Where it shows up
Not a separate revenue dashboard.
Revenue is context on the surfaces you already use. It appears where a number needs weighting, and stays absent everywhere it would only be decoration.
Dashboard KPI
Revenue joins visitors, sessions, and engagement in the KPI row for the selected range once Stripe is connected.
Visitor columns
MRR, LTV, plan, and subscription status become sortable columns on the roster and fields on the visitor detail.
The weekly report
The daily report agent writes a revenue and monetization section — and omits it entirely when Stripe is not connected rather than filling it with nothing.
Agent context
Agents reading sessions can weigh what they find by the account behind it, so a bug hitting your largest customers is not filed as low priority.
Prototype analysis
Revenue context is available when reasoning about a design change, so a proposal can be argued in terms of the accounts it affects.
Owner-gated
Only project owners can add, reconnect, or remove the Stripe connection.
Setup
One connector, then it is everywhere.
- 01
Connect Stripe
Settings → Features → Connectors. Stripe appears under Knowledge & Data when the environment has Stripe configured.
- 02
Sync
Pull customers and subscriptions so accounts can be matched against the visitors already in your roster.
- 03
Use it
Revenue starts appearing on the dashboard, the roster, and the report. Nothing else needs configuring.
Keep going
The rest of the platform.
Everything here reads from the same recorded session — there is nothing to stitch together between surfaces.
Stop guessing what happened.
One SDK, one afternoon. We will walk your team through it on a call and leave you with the recording of your own product.