App Store reviews to Power BI
Power BI knows your installs, your revenue and your crash rate. It does not know what anyone said. Reviewflowz publishes an OData feed, so every App Store review arrives as an ordinary row with its score, its storefront and its language attached.
- Set up in under five minutes
- No demo required
App Store reviews As written All my offline maps vanished
“Updated last night and the downloaded folder is empty. Nothing on the ridge but a grey screen.”
Australia storefront 7 September 2026
Power BI Reviews | Score | Country | Language | Tag | Review text |
|---|---|---|---|---|
| 1.0 | Australia | English | Offline maps | Updated last night and the downloaded folder is empty. Nothing on the ridge but a grey screen. |
The text cell is clipped for width here. The column holds the whole review.
They love how easy we've made it
10 000 Slack notifications
Online Pet Supplies Retailer
6000 reviews routed to Zendesk
European Bank
Monitoring 12 platforms
Marketing Software Company
100 000 reviews across 97 tours
Tour operator in Iceland
4500 locations monitored
Luggage Storage & Lockers
5000 AI replies generated
Sushi Restaurant Chain
Power BI's built-in OData connector reads it
Reviewflowz publishes an OData v4 feed. In Power BI choose Get data, OData feed, paste the URL and pick your tables. Nothing to install and no Power Query M to write. Paste a token from Reviewflowz as the user name and leave the password blank. Scheduled and incremental refresh both work, and a change stream carries edits and deletions into the model.
App Store reviews Reviewflowz Get data OData feed
OData v4
$filter=ReviewDate ge RangeStart and ReviewDate lt RangeEnd
ReviewDate is a datetimeoffset, so Power Query folds the window into the feed.
The column your model does not have
Your model knows installs, revenue and crash rate. It does not know what anyone said. Each App Store review arrives as a row with the score, date, storefront, language, reviewer, title and full text, with tags already filled. Beside it sit your ratings history and review profiles, so one report charts the store rating over eighteen months and the reviews that moved it.
App Store reviews Reviewflowz OData v4 feed Power BI Refresh in Power BI and the words arrive with the numbers.
Try it Free for 14 days
Your review history imports the moment you connect, so there is something to reply to from the first minute.
One storefront that looks nothing like the others
Apple files every review under a storefront, and Reviewflowz writes it onto every row, so country is a real dimension in your model. A crash drops every market together. A translated string that no longer fits its button drops one. Seven storefronts between 4.4 and 4.8 and Japan at 1.9 is a ticket with an owner. Build the visual once and every refresh feeds it.
App Store reviews 12,480 rows
Power BI
Average rating by storefront
Apple files every review under a storefront, so country is a column.
Seven storefronts move together. One that drops on its own is a localisation problem, not a crash.
Ordinary DAX over an ordinary table
A rolling 28 day average rating is a CALCULATE and a DATESINPERIOD. The share of one and two stars is a DIVIDE. Reviews per thousand installs is a measure across two tables you already have. No plugin and no proprietary metric language. When somebody asks where a number came from, the answer is a row with a date, a country and the sentence a person wrote.
App Store reviews Power BI Rolling rating 28d =
CALCULATE(
AVERAGE( Reviews[Score] ),
DATESINPERIOD(
'Date'[Date], MAX( 'Date'[Date] ), -28, DAY
)
)+0.4 vs the previous 28 days
FAQs
How do App Store reviews actually get into Power BI?
Through an OData v4 feed that Reviewflowz publishes. You create a connection in Reviewflowz and copy its feed URL, then in Power BI choose Get data, OData feed, and paste it. Authenticate with the token as the user name and a blank password. Power BI’s navigator lists the tables and you load the ones you want. There is no custom connector to install and no Power Query M to write.
Which columns arrive?
One row per review with the app, the platform, the title, the full text, the score, the review date, the reviewer’s nickname, the country, the language and the tags, alongside tables for your ratings history, your review profiles and a change stream of inserts, updates and deletes. The App Store Connect API does not return an app version with a review, so there is no version column.
Does the report refresh on its own?
Yes. Power BI’s scheduled refresh pulls from the feed on whatever cadence you set, and incremental refresh works as well because the review date is a datetimeoffset the feed can filter on. On the Reviewflowz side each App Store listing refreshes about every couple of hours, so the feed is already current when Power BI asks.
Can we chart rating by app version?
No, and nobody honestly can. The App Store Connect API does not return an app version with a review, and Reviewflowz does not invent one, so a rating-by-build measure would be fiction. Mark releases on the date axis instead: reviews cluster in the days after a ship, so the shape is there. The storefront is on every row, so market-level analysis is real.
Does the first load include our App Store history?
Yes. Connecting an App Store listing loads its review history, so the trend line is full from the first refresh rather than filling up over the next quarter. After that the feed carries what changed.
Which plan includes the BI feed?
The BI feed is a Premium feature and it is not part of the free trial, so budget for that rather than discovering it on day three. Everything else works the way the trial suggests: you connect an App Store listing yourself and see your reviews in minutes.
Do I need a demo to get started?
No. You connect your App Store listing and create the BI connection yourself, in under five minutes. If you get stuck, support is the people who build it.
Stop pasting App Store screenshots into the deck
Set up in under five minutes. No demo required.