App Store reviews to Google Sheets

A sheet that fills itself. Every App Store review lands as a row with its country, its language and its tags, so the release post-mortem is ready before the meeting rather than during it.

Set up in under five minutes • No demo required

Fjord · App Store reviews Synced 4 min ago
E H J N
1 Overall Score Review Date Country
2 The map worked above the treeline. 5.0 7 Sep 14:02 Australia
3 Route planning is quick and clear. 4.0 7 Sep 13:41 Canada
4 日本語で山の名前を入力できません。 1.0 7 Sep 12:58 Japan
5 Höhenlinien gut lesbar bei Sonne. 5.0 7 Sep 11:20 Germany
6 Battery use is fair on a long day. 4.0 7 Sep 09:47 United States
7 Since 4.2 search rejects Japanese. 1.0 7 Sep 08:12 Japan
8 Baixei os mapas, funcionou offline. 5.0 6 Sep 22:35 Brazil
Reviews Score by country
  • chewy
  • qonto
  • brevo
  • jins
  • filmin
  • lugg

One country that looks nothing like the others

Apple files every App Store review under a storefront, and Reviewflowz writes that storefront into every row as the country. Pivot Score by Country and a localisation bug stops being a feeling and becomes a line: seven territories between 4.4 and 4.8, and Japan at 1.9.

That shape is the diagnosis. A crash reads as every country dropping together. A broken keyboard layout, a payment method one bank rejects, a translated string that no longer fits its button, reads as one country falling while the rest do not move. Which country tells you which team to call.

The language of each review sits beside its country. Reviewflowz detects it from the text, so a German review left on the Swiss storefront still pivots the way you expect, and the sheet keeps every review in the alphabet it was written in.

Build the pivot once. Every sync feeds it, and the answer is a tab you open, not an export you rerun and reformat. The post-mortem for the next release is the same tab with a different week selected.

Fjord · App Store reviews

Rows: Country Values: AVERAGE of Score, COUNTA of Review ID

Country is Apple's storefront. Language sits beside it, detected from the review text.

Row A B C
1 Country AVERAGE of Score COUNTA of Review ID
2 Australia 4.4 96
3 Brazil 4.5 88
4 Canada 4.8 121
5 France 4.6 154
6 Germany 4.7 241
7 Japan 1.9 420
8 United Kingdom 4.5 197
9 United States 4.6 612
10 Grand Total 4.0 1,929
Reviews Score by country

Watch the release, not the summary

App Store reviews do not arrive evenly. They pile up in the hours after a release and the days after a featuring, and a broken build shows up as a run of one-stars in a few territories before your crash reporter agrees. When the rows are in a sheet that updates itself, the rollout is something you watch rather than something you hear about.

Reviewflowz checks the App Store every two hours by default, every ten minutes on the high-frequency setting, and syncs the sheet every half hour. On release day that means the first bad rows are on screen while the engineers are still at their desks, not in the next morning’s summary.

A chart on the sheet is a chart of the release. Reviews per day, split by rating, with Tuesday’s ship date marked. You can see the red band appear on Tuesday afternoon and shrink again after the hotfix on Friday. Nobody built a dashboard for that. Somebody inserted a chart.

The same sheet settles the argument afterwards. Was 4.2 actually worse, or did it feel worse because three people forwarded the same review? Count the rows.

Fjord · App Store reviews Synced 6 min ago

Reviews per day

27 Aug to 7 Sep 1 to 2 stars 3 stars 4 to 5 stars
0 100 200 300 400 27 28 29 30 31 1 2 3 4 5 6 7 4.2 shipped 4.2.1 hotfix

The ship marks are yours. The sheet knows dates, not versions.

Reviews Score by country Checks every 2 hours · syncs every 30 min

Tagged before anyone reads it

Every row lands with a Tags column filled. Reviewflowz reads the review in whatever language it was written in and files it under the themes your users actually raise: offline maps, battery, subscription price. A Japanese one-star about search and an English one about the same thing land on the same tag.

So a pivot on Tags is the complaint list, by week. The tag that did not exist three weeks ago and holds 386 reviews this week is the release note nobody wrote, and nobody had to read 386 reviews to find it.

Tags fill in as reviews arrive and the row updates when the tag does, so a pivot built on the Tags column stays right on its own. Your history gets the same treatment, including the reviews from before you had an account.

The same column routes. A filter view where Tags contains “Search input” is the thing you send to the engineer who owns search, and it keeps itself current until the tag stops appearing.

Fjord · App Store reviews Reviews
Tags contains “Search input” 386 of 18,420 rows
Overall Tags
7 山の名前が検索欄に入力できません。 1★ · Japan · 2026-09-07 14:02 Search input
24 Bergnamen kann ich nicht mehr eintippen. 2★ · Germany · 2026-09-07 11:36 Search input
58 Cannot type a mountain name into search. 2★ · United States · 2026-09-07 09:14 Search input Route planning
93 日本語を入れると文字が消えます。 1★ · Japan · 2026-09-06 21:58 Search input
140 Não dá para digitar o nome da serra. 1★ · Brazil · 2026-09-06 18:40 Search input
“Search input” · reviews per week
Three weeks to today
0 0 386

The sheet is right when you open it

An export is a file somebody remembers to make. This is a Google Sheet in your Drive that Reviewflowz keeps right. A new App Store review is a new row at the top of the sheet within half an hour of Reviewflowz seeing it, so the sheet is current when you open it, whoever opens it, on a Sunday.

Rows change when the review changes. A reviewer who edits their one-star into a four-star after your fix ships moves that row from 1.0 to 4.0, in place. A review Apple removes from the store loses its row. The sheet never holds a version of the truth the App Store no longer does.

Reviewflowz creates the spreadsheet in your Google Drive and writes one tab, Reviews. Nothing to build, no script to keep alive, no Zap that stops working the day a column moves. The tab carries a notice that it is managed by Reviewflowz and warns anyone about to type into it.

One click sends your whole review history into the sheet, so the trend line starts full rather than filling up over the next quarter. Connect on Tuesday and by Tuesday afternoon you can pivot three years of App Store reviews.

Fjord · App Store reviews Reviews tab · the spreadsheet Reviewflowz made in your Google Drive
  1. New row inserted at row 2

    Newest App Store review first, in the sheet within half an hour.

    5.0 Offline maps saved us Australia · 2026-09-07 14:02
  2. Row 34 updated in place

    The reviewer edited their review after Friday’s hotfix. Same row, new values.

    1.0 4.0 直りました、ありがとう Japan · 2026-09-07 11:48
  3. Row 48 removed

    Apple took the review off the store, so it leaves the sheet too.

    1.0 Crashes on launch United States · 2026-09-05 08:12

Checks the App Store every 2 hours · syncs the sheet every 30 minutes

Every 10 minutes on the high frequency setting. Nobody has to remember anything.

The Monday numbers are a sheet, not a task

Add a daily, weekly or monthly recap and Reviewflowz appends one line per app per period to a report sheet: new reviews, their average rating, reply rate, reply delay, total review count and the rating the App Store shows. Every morning the sheet is one row longer.

That is the table somebody rebuilds for the Monday deck, except nobody rebuilds it. Point a chart at the sheet and the slide updates itself. Point Looker Studio at it and the dashboard does. The week 4.2 shipped is eight rows where the new-review rating falls from 4.5 to 3.6 and climbs back, while the rating the App Store displays moves 4.6 to 4.5. The recap knew on the Wednesday; the public number caught up the following week.

Share it the way you share any sheet. The product manager, the agency, the engineer who owns search, the founder who wants the number and nothing else: none of them needs a Reviewflowz login to read it, and Google’s own sharing decides who can.

The review rows and the daily line come from the same account and the same profiles, so the number on the slide and the reviews behind it never disagree.

Fjord · Daily recap
One row appended every morning by Reviewflowz
Row A C D E H
1 Date New New rating Reply rate Platform rating
2 31 Aug 208 4.5 92% 4.6
3 1 Sep 4.2 shipped 296 4.0 90% 4.6
4 2 Sep 372 3.6 88% 4.6
5 3 Sep 331 3.7 91% 4.5
6 4 Sep 4.2.1 hotfix 268 4.0 93% 4.5
7 5 Sep 233 4.3 94% 4.5
8 6 Sep 218 4.4 95% 4.5
9 7 Sep 211 4.5 94% 4.5

Column H is what the App Store shows. It moved 4.6 to 4.5 while column D told you on the Wednesday.

Daily report Chart

Choose what lands in the sheet

Sync every App Store review from every app you ship, or narrow it. Each App Store listing is a review profile in Reviewflowz, and a sync takes one profile or several. The app’s name is on every row, so one sheet for Fjord and Fjord Pro still pivots by app.

Per app, pick the countries. Leave it empty and every storefront the app sells in is tracked. Pick Japan and Germany and only those rows arrive, which is how a localisation team gets a sheet of just its markets without a filter anyone has to maintain.

Add a rating filter: three stars or less for the sheet the support lead reads, five stars for the one marketing mines for quotes. There is a switch for reviews with text only, so a bare star rating with nothing written under it never takes a row. Two syncs from the same app to two sheets is fine.

Setup is the same at one app or eight: connect the App Store listing, click Connect Google Sheets and sign in with Google, pick the apps, switch it on. Under five minutes, and the first rows are in the sheet on the next sync.

Google Sheets sync On
Apps
Fjord Fjord Pro + Add app
Countries Leave empty to track all countries
Japan Germany France United States + 6 more
Rating
All ratings 3 stars or less 5 stars
Reviews with text only Skip rows with an empty review
To
Fjord · App Store reviews Change

Reviewflowz created this spreadsheet in your Google Drive

Checks the App Store every 2 hours · syncs every 30 minutes Send all past reviews

The post-mortem is ready before the meeting.

Set up in under five minutes. No demo required.

Is this a one-off export or a live sync?

A live sync. New App Store reviews appear as rows at the top of the sheet, edited reviews update their row, and reviews removed from the store lose their row. Nobody re-runs anything. Reviewflowz syncs the sheet every 30 minutes.

Which columns does the sheet have?

One row per review with the review id, the app, the platform, the title, the full text, the score, a link, the review date and time, the language, the reviewer’s nickname, the country, the tags and Apple’s review id. Apple does not attach the app version to a review, so the Version column stays empty for App Store reviews, and the sheet does not carry your developer reply.

Does the first sync include our App Store history?

Yes, on a paid plan: one click loads every past review into the sheet, so the trend line is full from day one. During the free trial the sheet receives new reviews as they arrive and history loads once you subscribe.

Can I edit the sheet, or add formulas to it?

Add tabs. Pivots, charts, formulas and Looker Studio all read the Reviews tab fine, and because new rows go in at the top, a pivot built on whole columns stays right. The Reviews tab itself is managed by Reviewflowz: it warns you before a manual edit and may overwrite one on the next sync.

What happens when a reviewer edits their review after we fixed the bug?

The row updates in place with the new rating and text, so the pivot moves with it. When Apple removes a review from the store, the row is deleted on the next sync.

Do I need a demo to get started?

No. You connect your App Store listing and pick Google Sheets yourself, in under five minutes. 14 day free trial, no credit card.