Connect
Bring the whole
picture into view.
Your product data lives in different tools. Connect analytics, customer feedback, and error data to one project, so the evidence is there when you need to understand a change.
Different signals. The same checkout.
Illustrative data · Expand a record to inspect it
Your connected sources
PostHog
Product analytics
Intercom
Customer feedback
Sentry
Error data
Read from your tools.
Bring the context into adduce.
Checkout project
One body of evidence. Sources retained.
PostHogCheckout completion fell64% → 52% · weekly comparison
Previous week: 320 of 500 checkout sessions completed payment. Current week: 260 of 500. The funnel definition is the same in both windows.
A change in completion identifies a question to investigate. It does not establish why customers left.
IntercomThe total was hard to find“I got to the payment step before I could see the full price.”
An illustrative excerpt from a closed support conversation. The customer describes going back to check which plan they needed.
This is one customer’s account, not a survey of everyone who abandoned checkout.
SentryPayment requests timed outPaymentTimeout · 8 users affected
An illustrative error issue from the checkout service. The issue includes an affected-user count and a reference to the originating error record.
The error may warrant investigation. These records alone do not connect it to the customers in the other sources.
Each source adds context
The numbers. The words.
The problems behind them.
Start with the sources relevant to your question. Add another perspective as the investigation develops.
Product analytics
See what people do.
Funnels, retention, and event trends show where product behaviour changes. Bring those measurements alongside the feedback that helps you investigate them.
- PostHogLive
- AmplitudeLive
Customer feedback
Hear what gets in their way.
Support conversations and tickets bring customer language into the evidence: pain points, requests, and the context behind them.
- IntercomLive
- ZendeskBeta
Error data
See where the product breaks.
Error issues and operational signals add another perspective. Look at technical problems alongside customer experience without assuming one explains the other.
- SentryLive
- DatadogBeta
Set the scope
A connection with
a clear purpose.
Keep the sources for a product or investigation together. Configure the access each connector needs, then check what comes through.
Connections are project-scoped. The same tool can be connected separately to different projects.
- 01
Choose the project and source.
Open the project you want to understand and add a source. Connections belong to that project; you can connect more than one source of the same type.
- 02
Configure access and scope.
Enter the details requested by the connector and test the connection. Scope depends on the tool: for example, selected Slack channels or Sentry projects.
- 03
Review the first sync.
Once connected, run a sync and inspect the evidence it adds. Check sync history for completed and failed runs before relying on the latest data.
Know what is connected
Useful evidence starts
with clear boundaries.
Sync on a schedule.
Supported pull sources sync daily, with manual sync when you need an update. Initial imports and rate limits can affect how soon data appears. Sync history shows the outcome.
Read your sources.
Source ingestion reads from the tools you connect. Sending work to an issue tracker is a separate action; connecting a source does not file issues for you.
Bring conversations too.
Upload call transcripts into your project when the context comes from a conversation. Uploads follow their own processing flow rather than a scheduled connector sync.
From connection to understanding
Now the evidence
can work together.
Explore how adduce turns connected evidence into findings you can investigate and briefs your team can review.
See how synthesis works