Google reviews to Tableau
Your business already reads Tableau, so a separate reviews dashboard is a link that gets opened twice. Reviewflowz publishes an OData feed, Tableau’s built-in OData connector reads it, and every Google review arrives as an ordinary row with the site it was left at attached.
- Set up in under five minutes
- No demo required
Rating by location
Every location row arrives with a latitude and a longitude, so this is a drag and drop.
Google reviews, into the Reviewflowz OData feed, into a Tableau extract.
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
Paste one URL. There is nothing to install.
Reviewflowz publishes an OData v4 feed, and Tableau's OData connector is built in. Connect, OData, paste the service URL, and the tables appear. Choose Username and Password, paste a token you create in Reviewflowz as the user name and leave the password blank. Tableau builds an extract, eight thousand reviews finish in seconds, and stable table names keep a March workbook working in November.
The connection produces an extract. Tableau Desktop supports extracts for OData.
Location is a column, and so is its latitude
Reviewflowz writes the site onto every Google review row, beside the rating, date, language, tags and text. Locations is its own table with name, city, country, postcode, latitude and longitude, which Tableau reads as geographic roles on sight, so rating by site on a map is a drag and drop. Thirteen sites between 4.33 and 4.79 and one at 3.62 is an address.
Locations
14 rowsEvery Reviews row names its site
Reviews
7,928 rows trimmed to eight of twentyLatitude and Longitude arrive as numbers, not as a place name Tableau has to guess at, so the geographic roles are right before the map is drawn.
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.
The map says where. The blend says why.
The workbook already holds revenue per site, transactions per hour and weekend hours on the rota. Put rating on one axis and staffing on the other: the site at 3.62 runs the thinnest weekend cover in the chain, and sixty-eight of its ninety-four one and two star reviews in ninety days mention the queue. The blend happens in Tableau, where that data already lives.
Google rating vs weekend cover, by site
68 of the 94 one and two star Google reviews Bristol Harbourside took in the last 90 days mention the queue or the wait. Its weekend cover runs 18 per cent below the chain.
Google reviews arrive as a Reviewflowz OData extract. Staffing hours come from the rota export already in this workbook. Tableau blends them on site name.
Volume tracks footfall, not a release calendar
Google review volume roughly doubles at the weekend, jumps the week a campaign runs and falls off the week the car park is dug up. A monthly average flattens all three. Reviews per day on a column chart shows the Saturdays above the Tuesdays, and a site whose weekend volume drops while its neighbours hold shows up in September instead of a November report.
Google reviews per day
27 Jul to 6 Sep 2026 Sat, Sun Mon to FriSaturdays average 64 Google reviews a day and Tuesdays 27. The average of 38 sits between them and describes neither.
Read in Tableau Desktop from an extract of the Reviewflowz OData feed.
FAQs
How do Google reviews actually get into Tableau?
Through an OData v4 feed that Reviewflowz publishes. You create a connection in Reviewflowz and copy its feed URL, then in Tableau choose Connect, OData, and paste it. Set Authentication to Username and Password, put the token in the user name field and leave the password blank. Tableau lists the tables and you drag in the ones you want. There is nothing to install: the OData connector ships with Tableau.
Extract or live connection?
Extract. Tableau Desktop supports extracts only for OData sources, so that is the connection you get, and it is the right one here anyway. Review volume is small next to your transactions table, the extract builds in seconds, and a published workbook backed by an extract opens instantly for the people who only came to look at it.
Which columns arrive?
One row per review with the rating, the review date, the location name, the review profile, the reviewer name, the title, the full text, the language, the tags, the topics and the owner reply with its date. Alongside it sits a Locations table with the name, city, country, postcode, primary category and the latitude and longitude, plus your review profiles, your ratings history, a review summary and a change stream of inserts, updates and deletes.
Do we have to geocode the sites to get a map?
No. Locations carries a real latitude and longitude per site, so Tableau assigns the geographic roles itself and the map draws from the numbers rather than from a name it has to guess at. That is the difference between a map you build on Tuesday afternoon and a mapping project you scope.
How does the workbook stay current?
You refresh the extract, and how that is scheduled is a setting in your own Tableau deployment rather than something we run. On the Reviewflowz side each Google Business Profile is checked about every couple of hours, so the feed already has the new reviews by the time Tableau asks for them.
What happens when a review is edited or removed?
It reaches the feed. A reviewer who edits a one star into a four star after you fixed the thing they complained about, and a review Google takes down, both arrive as events on the change stream rather than as a silence, so the numbers in the workbook do not quietly drift away from what is on the listing.
Does the first load include our Google review history?
Yes. Connecting the Google Business Profile loads its review history, so the trend line is full from the first extract rather than filling up over the next quarter. Bear in mind that volume tracks footfall, so the history spikes at weekends and after campaigns rather than on a release schedule.
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 finding out on day three. Everything else works the way the trial suggests: you connect your Google Business Profile yourself and see your reviews in minutes.
Do I need a demo to get started?
No. You connect your Google Business Profile and create the BI connection yourself, in under five minutes. If you get stuck, support is the people who build it.
Put the site league table in the workbook they already open
Set up in under five minutes. No demo required.