Connect data sources
Choose between third-party connectors and the Capreolus SDK for your telemetry.
Capreolus reads data from two complementary sources: third-party services you already use (App Store Connect, Sentry, RevenueCat) and the Capreolus mobile SDK. You almost always want both.
Third-party connectors
Connectors are the fastest way to backfill historical data. You add a credential once and Capreolus pulls and refreshes on a schedule. They cover store-side metrics that the SDK cannot see (release tracks, ratings, refunds).
Capreolus mobile SDK
The SDK gives you in-app telemetry that no third party has visibility into: cold-start time, battery impact, custom funnel events, and attribution. It is also what powers in-app feedback prompts.
Comparison
| Signal | Connector | SDK |
|---|---|---|
| Crashes | Sentry / Firebase | Native crash + JS errors |
| Subscriptions | RevenueCat | Restore / paywall events |
| Reviews + ratings | App Store Connect / Google Play | — |
| Cold start | — | Yes (per release) |
| Custom events | — | Yes |
| Release tracks | App Store Connect / Google Play | Detected at runtime |
Recommendation
- Day 1: connect App Store Connect, Google Play, RevenueCat.
- Day 2: ship an SDK release that calls Capreolus.start().
- Day 3: turn on Sentry or Firebase Crashlytics if you have one.