Quickstart
Get your first revenue signal in under 10 minutes. All you need is a read-only API key from at least one data source.
Prerequisites
- A Stripe account (or other billing provider) with live transaction data
- A product analytics tool (PostHog, Amplitude, or Mixpanel) with event data
- Optionally: Sentry for error tracking, GitHub/Linear for ticket delivery
Step 1: Connect your billing data
Shingo needs to know where your revenue comes from. Start by connecting Stripe with a read-only restricted key.
# In your Stripe dashboard:
Developers → API Keys → Create restricted key
Permissions: Read on Charges, Subscriptions, Customers, Invoices
Key format: rk_live_...
Paste the key in the Shingo onboarding flow, or pass it via the API. Shingo will begin ingesting your billing events immediately.
Step 2: Connect product analytics
Shingo cross-references user behavior with revenue outcomes. Connect at least one analytics source.
PostHog
Project → Settings → API Key
phx_...
Amplitude
Settings → Projects → API Key
amp_...
Mixpanel
Project Settings → Service Account
mp_...
Step 3: Add error tracking (optional)
Error data makes Shingo's causal model significantly more accurate. If you use Sentry, connect it with a read-only auth token.
Settings → Auth Tokens → Create token with read-only scope
Key format: sntrys_...
Step 4: Connect delivery targets (optional)
Shingo can auto-create tickets when it finds revenue-critical issues. Connect GitHub or Linear to enable this.
GitHub
Fine-grained token with Issues + PRs permissions
ghp_...
Linear
Personal API key with write access to issues
lin_api_...
Step 5: Get your first finding
Once connected, Shingo begins ingesting historical data and building its causal model. You'll receive your first execution package within hours, containing: