Connectors
Store reviews
Collect and answer the reviews of your app in the App Store and Google Play in Limenia — what you set up in App Store Connect, the Play Console and optionally GitHub.
The store reviews connector pulls the written reviews of your app from the App Store and Google Play into an inbox in the Limenia dashboard (Reviews). Moderators answer them there, group bug reports into tickets and, optionally, turn tickets into GitHub issues.
Note: Store reviews are the ratings of your app in the app stores. They have nothing to do with pre-moderation reviews (
POST /v1/reviews). Store reviews do not use the/v1API and send no webhooks to your backend; there is no code to write.
The connector needs a plan that includes store reviews. An admin or owner sets it up per app: tab Connectors → Store reviews. The dashboard shows every step with copyable commands.
What it does
- Collecting: Limenia polls both stores every 15 minutes (neither store pushes reviews) and runs a daily full pass to catch edits. Fetching starts after the first successful Test connection and covers the last 30 days (Google Play: 7 days). Admins can trigger Retrieve now once every 5 minutes per store.
- Google Play delivers only reviews with text, of the production track, written or changed in the last 7 days. Older reviews cannot be imported, and an outage of more than 7 days leaves a gap.
- App Store returns no star-only ratings and no reviews of tvOS apps.
- Inbox: filter by app, status, period, store, stars, category, language, version and ticket. Reviews are separate items, not reports or cases, and are not part of the DSA case flow.
- Answering: a moderator writes a reply (from scratch, from a template, or from a suggestion of the optional AI), sees the final text and sends it, one review at a time. Limenia never sends replies automatically.
- Checks before sending (always, no override): not empty, within the store’s length limit (Google Play 350 characters; App Store 1,000 by default), no HTML, no links except to the allowed link domains of the app (up to 10), no e-mail addresses or phone numbers, no request for a better rating, no incentive linked to a rating and no promise of a refund.
- After sending: Apple reviews replies for up to 24 hours before publishing them. Replies written directly in the store console are shown as such. Deleting replies is not supported; a new reply replaces the current one.
- Spam and abuse: there is no API to report reviews to the stores. The dashboard links the store console and suggests a reason text.
- Tickets: with the optional AI, bug reports of an app are grouped into tickets (title, summary, count, affected versions, stores, average stars, urgency). Moderators can also create, merge and split tickets by hand.
- Optional AI: the owner can switch on AI suggestions for store reviews. They classify each review (bug report, feature request, complaint, praise, question, spam or abuse, other), detect urgency and draft a reply in the language of the review. Classifications count against the monthly AI quota of the plan. Without AI, the inbox, templates, your own replies and manual tickets still work.
App Store setup
- The Account Holder of your Apple developer team must have requested access to the App Store Connect API once.
- In App Store Connect open Users and Access → Integrations and create an API key only for Limenia with the role Customer Support. Download the
.p8file; Apple allows the download only once.- A team key (default) sees all apps of the team; Limenia only queries the app you enter. Alternatively use an individual key of a user who sees only this app; it has no issuer ID and stops working when that user is removed.
- Do not use an Admin key, and do not share the key with other tools: they would share Apple’s rate limit.
- Enter in the dashboard:
- the Apple ID of the app (numeric, from App Information; not the bundle ID),
- the type of key (team or individual),
- the key ID (10 characters),
- the issuer ID (team keys only, shown above the key list),
- the
.p8file (upload or paste).
- Press Test connection. It reads one review. It cannot prove the right to reply; a missing right shows up when the first reply is sent.
The key is stored encrypted, never shown again and can be replaced at any time.
Google Play setup
You use a service account in your own Google Cloud project. Limenia provides none.
-
Enable the Google Play Android Developer API in your project:
gcloud services enable androidpublisher.googleapis.com --project=PROJECT_ID -
Create a service account. It needs no role in the project:
gcloud iam service-accounts create limenia-reviews --project=PROJECT_ID --display-name="Limenia Reviews" -
In the Play Console open Users and permissions and invite the service account for this app only, with the permissions View app information (read-only) and Reply to reviews. Nothing more is needed. Only an account admin of the Play Console can invite; an invitation can take up to 36 hours to take effect.
-
Create a JSON key and upload it in the dashboard together with the package name (e.g.
com.example.app):gcloud iam service-accounts keys create limenia-reviews-key.json \ --iam-account=limenia-reviews@PROJECT_ID.iam.gserviceaccount.comNewer Google Cloud organisations block key creation with the policy
iam.managed.disableServiceAccountKeyCreation; relax it for this one project only. -
Press Test connection. Typical errors: invalid key, permission missing or app not shared yet, API not enabled, app not found.
Without a key file: instead of uploading a key, you can let Limenia impersonate your service account. Give the Limenia service account shown in the dashboard the role Service Account Token Creator (roles/iam.serviceAccountTokenCreator) on your service account (not on the project), prove ownership with the project label limenia-tenant=<your tenant ID in lower case> and a custom role limeniaReviewsConnector with resourcemanager.projects.get bound to the same Limenia account, and enter the service account e-mail together with the package name. The dashboard shows the exact commands. Organisations that restrict roles to their own domain (iam.allowedPolicyMemberDomains) must allow this for the project.
Both stores
- A store app can belong to only one Limenia app.
- Switching off pauses fetching and sending and keeps the access data. Disconnecting deletes the stored key and stops everything at once; stored reviews, drafts and tickets remain until their retention ends.
- Google allows 200 reads per hour and 2,000 replies per day per app, shared with your other tools; Limenia stays below that and waits when it gets close. Apple allows 3,600 requests per hour per key.
GitHub (optional)
Moderators can turn a ticket into a GitHub issue, one ticket at a time. Closing the issue sets the ticket to done, reopening it sets it to open again.
- An admin opens Reviews → Settings → GitHub → Connect with GitHub and installs the GitHub App Limenia Moderation on selected repositories. It asks for Issues: read and write and Metadata: read-only, nothing else.
- Sign in to GitHub to confirm the installation belongs to you. If an organisation owner must approve the installation, link it after the approval with Link existing installation.
- Choose the target repository per app. A public repository needs an explicit confirmation, because issue texts become public.
Issues contain the ticket title, the AI summary (marked as such), counts per store, versions, period, average stars, urgency and a link back to Limenia. They never contain names of reviewers, device details, verbatim review texts or store review IDs. Only GitHub.com is supported. GitHub stores data in the USA; Limenia sends data there only when you create an issue.
Data protection
- Names and nicknames of reviewers are never stored. Limenia stores stars, title, text, language, country (App Store), app version and device class (Google Play) and timestamps.
- The AI, if switched on, receives stars, title, text, store, app name and your reply hints, never names, device data or IDs.
- Reviews are not linked to user files.
- Retention: by default 183 days (owner setting, 30 to 730 days), counted from the review or the last reply sent.
- Objection: an admin can delete a single review with Delete (objection). Limenia then blocks it from being imported again. The review stays in the store.
- The App Store Connect API and the Google Play Developer API are run by Apple and Google. As the tenant you are the controller for the reviews; mention the processing in your privacy policy. See Data protection.