App Store
Connect an App Store app to Sift to pull customer reviews across every territory into one inbox, route negative ratings to the right team, and post developer replies without leaving Sift.
At a glance
| Inbound: Reviews (rating, title, body, reviewer name) | ✅ |
| Inbound: Territory of each review | ✅ |
| Inbound: App version each review was left on | ✅ best-effort enriched |
| Outbound: Post a developer reply | ✅ |
| Outbound: Update an existing developer reply | ✅ (delete + re-post under the hood) |
| Outbound: Delete a developer reply | ✅ |
| Multi-app per workspace | ✅ |
| Multi-territory ingestion | ✅ |
| Filter / route by territory or version | ✅ in the inbox |
| Auto-reply bots | ✅ |
| Reviewer responses to your developer reply | ❌ App Store API doesn't expose them |
Set it up
Go to Settings → Integrations → App Store and:
- Connect via App Store Connect: upload an API key with Customer Support access at minimum (the role required to post developer replies).
- Pick the apps Sift should monitor.
- Choose a backfill cutoff date: how far back history is pulled on first sync.
- Assign each app to a queue (optional) for routing.
What you can do
Reply to a review - Sift posts via Apple's developer-response API as the connected App Store Connect account. Edit a reply you already posted: Sift handles this as a delete-then-repost (Apple has no in-place update endpoint), but it looks like an edit in Sift and on the App Store. Delete a reply you posted.
Filter and route by territory, version, or rating - useful when the iOS team owns one set of reviews and a localization team owns another.
Trigger workflows on rating drop, specific keyword, territory - the same workflow surface you use on every other channel. Apply auto-reply bots for FAQ patterns or off-hours acknowledgements.
Backfill + ongoing sync
On first connect, Sift backfills history from the cutoff date you set during onboarding. After that, ongoing syncs poll for new reviews continuously. High-volume apps may be capped at a per-run batch size - entirely transparent in the inbox; reviews catch up over subsequent runs.
What Sift ingests
Every public review on every connected app, across every territory Apple makes available - Sift pulls them all, not just one country. Each review comes into the inbox as its own action with:
- Rating (1–5 stars)
- Title and body (either can be empty - Apple allows star-only reviews)
- Reviewer nickname
- Territory (ISO country code - useful for regional routing)
- App version the review was left on, when Apple's public RSS feed has it (not on every record)
Sift threads everything by app + review ID so a single review's history (rating, replies, updates) stays together.
Not supported today
- TestFlight beta feedback: Apple exposes this on a separate surface that Sift doesn't ingest.
- Reviewer follow-ups to your developer reply: the App Store doesn't expose those as separate ingestable events. If the same reviewer leaves a new review later, that comes through as a new action.
- Per-territory or per-version ingestion filters: Sift pulls everything; filter / route inside the inbox instead of choosing what to ingest.