Connect billing so revenue joins AI visits
Connect your billing system, add a shared group_id so revenue matches visits, verify one test customer, then switch to a production connection. A test connection never captures live revenue.
billing paths: Stripe or Chargebee, and in-house billing
ThriveStack docs, checked Nov 15, 2026the shared field that joins revenue to product and marketing data
ThriveStack docs, checked Nov 15, 2026places to confirm data: Developer Tool and Diagnostics Report
ThriveStack docs, checked Nov 15, 2026needs its own production connection, not the test one
ThriveStack docs, checked Nov 15, 2026Revenue joins visits through one shared field.
ThriveStack matches revenue to visits with a shared group_id. Your billing system must carry the same value as your product and marketing data. Without it, revenue and AI visits stay in two places.
Two ways to connect billing, as of Nov 15, 2026
| Path | Who it is for | What the assistant does | How you verify |
|---|---|---|---|
| Stripe or Chargebee | Teams on Stripe Billing or Chargebee | Adds group_id metadata to customer create and update calls, and writes a one time script for existing customers | New sign up shows group_id in billing metadata and matches product data |
| In-house billing | Teams with their own invoices and subscriptions | Pushes subscriptions, invoices and transactions through the Revenue API, using a key with the Revenue APIs scope | Create a test record and see it in the Developer Tool |
Connect billing in four steps, then go live.
- 1
Connect your billing provider
Open the Revenue setup page and pick Subscription management for Stripe or Chargebee. This is needed for MRR, ARR, churn and expansion. Transactions and invoices are optional.
- 2
Run the prompt in your billing repo
Review what the assistant changes and ask it to fix any errors. If billing logic spans several services, run the prompt in each repo.
- 3
Verify the data
Check revenue events in the Developer Tool, Revenue tab. Check connection status in the Diagnostics Report.
- 4
Go to production
Create a new connection that points to your live account. The test connection does not capture live revenue.
When it works, MRR, ARR, churn, expansion and contraction reports become available, and revenue is joined with product usage at the account level. You also get an email that lists logged revenue events and any issues. For how revenue maps back to AI visits, read the revenue and pipeline lesson and the CRM lesson.
ThriveStack citedby runs your prompt panel across 10+ AI engines, reads server-log crawler hits, matches human visits to signups and reports AI-sourced and AI-influenced pipeline.
Connect billing so revenue joins AI visits, answered.
Which billing systems work?
The docs give a guided path for Stripe and Chargebee, and a Revenue API path for in-house billing.
Why do I need group_id?
It is the shared value that lets ThriveStack connect revenue to the same account in your product and marketing data.
How do I know it works?
Run a sign up, then check that group_id appears in billing metadata and matches product data. Then confirm events in the Developer Tool.
Sources for this lesson
Steps come from the ThriveStack docs, checked Nov 15, 2026. The docs give no per step times, only "minutes" overall.