Connect your product’s data
Choose a source and check what Hub has actually received.
Who this guide is for
- Who this is for
- An owner connecting a source, or a member checking available reports.
- What you can do
- You can identify the source, period and limits of the data in a report.
On this page
Start with the question you need answered
- Select the product and open Connections or its Settings page. Decide whether you need events, money, search data or errors.
- Open the relevant service and follow its form. An owner connects external data sources. PostHog supports the cloud regions and self-hosted servers over HTTPS only.
- Wait for connection verification, then open the product’s data. Saving a token does not by itself establish that measurements have arrived.
- Check the source, period and last import result. For missing data, verify the provider project, token permissions and available dates instead of treating an unknown value as zero.
Know what each source provides
- The SDK and HTTP event ingestion supply product behavior data. Available reports depend on privacy mode and the data received. Sending payments from your own server requires a separate ingestion endpoint and key; product events do not automatically become revenue.
- PostHog and Amplitude import daily event counts for the period before event collection began in Hub. These imports do not bring across users, retention or a complete activity history.
- Stripe supplies payments and subscription history; MRR and churn need the relevant history. Agent costs remain separate from product revenue.
- Search Console and Yandex Metrica supply website data. Google sign-in does not connect Search Console. SEMrush adds estimates from an external service rather than measurements of your own site.
- RuStore supplies the average rating and rating count, without installs or revenue. Choosing App Store or Google Play in a profile does not connect the store account; ready-made connectors for those stores are not available yet.
Check product errors with Sentry
Open Sentry in Connections. For Sentry Cloud, enter the organization and project slugs from your Sentry URL and a token with project:read and event:read. Hub verifies access before saving it. This connection does not support self-hosted Sentry.
The product’s section on the Sentry connection page shows up to 20 unresolved issues active within the last 14 days, with recent issues first. Follow an issue link for details in Sentry. Its event count is Sentry’s value for that issue, not a total for those 14 days. Hub does not import individual events or stack traces.
If a connected source has no useful data yet
Check its state and last import in Connections, then the report’s date range. Fix permissions or configuration at the provider and retry the import. Do not include a token when sharing an error report.