Integrations & setup
Start with approved billing and product behavior. We help you connect the right sources, map the customer identity, and validate the evidence that will support your first useful analysis.
Connect. Map. Validate.
Our two-hour target covers a guided setup with supported sources, the necessary access ready, and a clear mapping between your product and Stripe customers.
Historical data preparation, custom integrations, and model learning can take longer. We agree the scope before the session.
Start with the essentials
Two complementary inputs help connect who the customer is, what they pay for, and whether the product is still delivering value.
Approved customer, subscription, and payment context. The connector retrieves billing information without charging, refunding, or changing subscriptions.
Meaningful activity and the feature paths that deliver value, explicitly linked to the correct customer and source.
Who brings what
The best setup starts with a shared understanding of what customers came to achieve and where that behavior is recorded.
Your product owner brings the core workflows, activation milestones, and the questions the team wants to investigate.
Your developer prepares the supported Stripe and product-data paths and explains how product users map to Stripe customer IDs.
Review the proposed event meaning, mappings, and access. Your team approves the setup before governed activation.
Check source freshness, identity, available history, and complete behavior coverage before treating a connection as ready.
Two different milestones
A source can be connected before every customer has enough history for a supported assessment. Revioli keeps those states distinct.
The supported source is available within the approved scope.
Mappings, freshness, and complete records establish what is usable.
New behavior and eligible later outcomes add to the model’s context.
Scope before setup
Tell us about your billing structure and data sources so the first connection covers the right part of your business.
The current supported forecast path is scoped to one USD licensed, per-unit recurring price on an eligible subscription. Metered, tiered, and multiple-subscription cases require a scope review. Connecting data and qualifying it for a forecast are separate steps.
Start with approved activity that represents value. Your team reviews the proposed tracking, and sensitive fields and unnecessary free text should be kept out of the behavioral evidence path.
Tell us which systems you use. We’ll confirm a supported connector or agreed import path before planning the implementation. A tool mentioned as a form example does not imply a native connector.
A description of your product, your billing structure, and the workflow you want to understand. Credentials and customer records belong in the supported onboarding path, not the public form or email.
A useful first connection
Bring your existing systems and the customer journeys that matter. We’ll agree the scope together.