Connectors
Pull reviews and tickets from the App Store, Intercom, and Zendesk automatically.
Connectors pull feedback from where it already lives — no engineering, no widget. Sentriment syncs every 15 minutes, deduplicates, and runs each item through the same pipeline as live feedback. Connect them under Sources in the dashboard. Sales and renewal calls take a different door: see Sales calls for uploads, the transcript API and the Granola connector.
Connecting is forward-only: from that moment on, every new conversation, ticket or review flows in automatically. Your history doesn't come along uninvited — bringing it in is a deliberate step, described below.
Backfilling history
#Every connected source has a Backfill history action on its card. Pick how far back to go (presets from 3 months to 2 years, or any date), and Sentriment asks the provider how many items that is — you see "~1,240 conversations since 12 Mar 2026" before anything moves. Confirm, and the import runs in the background: the card counts up as items land, and you can leave the page and come back to it. Sales calls work the same way but show you the actual list of calls with a per-call estimate instead of a single count, see Sales calls.
The items count on a connector card is everything that source has brought in: new items from the automatic sync plus everything a completed backfill imported. Duplicates are never counted twice.
Backfilled items are treated as history, not news: they score user health, join themes and count in totals, but they never trigger alerts, never register as spikes, and never reopen a resolved theme. Re-running a backfill is safe — items you already have are never duplicated.
Note
Imported history draws from your one-time 1,000-item import allowance first (shared with CSV imports), then your plan's monthly volume. If the plan runs out of room mid-backfill, the import pauses exactly where it stopped and resumes on upgrade — nothing is skipped or lost.
App Store
#Point it at your app and its storefront, and Sentriment ingests your reviews: star rating and country ride along as metadata, so you can slice themes by rating or region. Reviews are pseudonymous, so App Store feedback stays anonymous by design.
Finding your app
Open your app on apps.apple.com and paste the address: apps.apple.com/us/app/your-app/id1234567890. The field accepts the whole link, Apple's id1234567890 form, or the digits on their own, and it reads the storefront out of the link for you. The same number is the Apple ID on the App Information page in App Store Connect.
Reviews are per storefront, so us and de are different sets. One Apple-imposed limit: the public feed only exposes roughly the 500 most recent reviews, so an App Store backfill imports what is still available rather than a date range, and the backfill panel says exactly how many.
Intercom
#Connect with an access token (Settings → Developers in Intercom). Sentriment reads conversations, joins each to the contact's email, and analyses the message body. A contact you've never seen becomes a shadow user — the moment your app identifies that email, their chats merge into their real profile.
Zendesk
#Connect with your subdomain, an agent email, and an API token. Sentriment reads tickets and sideloads each requester so it can join tickets to your users by email. If you sync your own user IDs into Zendesk, enable “requester external_id is our user ID” at connect time for a direct join — no email needed.
Granola (sales calls)
#Connect with a Granola API key and your company domains, and every call Granola finishes is read once, within minutes. A call is not one piece of feedback, so it takes a different path from the sources above: each transcript is read once and only the customer's own words are kept, which is why calls have their own guide. Setup, the filters that decide which calls are read, the history import and what is never stored are all on Sales calls. Granola's API needs their Business or Enterprise plan; on any other plan the CSV export and the transcript API cover you.
Identity from support tools
#This is where email pays off
Support tools are exactly why identifying users by email matters. With email flowing from your app and your help desk, a customer's tickets and in-app feedback land on one profile with one health score. Without it, they fragment into separate “users”.
Each connector has a “create users from contacts” toggle if you'd rather ingest the text without building user profiles from support contacts. The ignore list under Settings → Identity keeps your own staff and shared inboxes out of the user list.