Google reviews to Qlik

Through an OData v4 feed that Reviewflowz publishes. Qlik has its own OData connector: it is built into Qlik Cloud, and it ships in the Qlik Web Connectors package for client-managed Qlik Sense and QlikView. You create a connection in Reviewflowz and copy its feed URL, create an OData connection in Qlik and paste it, then authenticate with basic authentication using the token as the user name and a blank password. The entity sets then appear as tables you select. Nothing is installed on either side.

Six. Reviews is one row per review with the rating, the review date, the location, the language, the tags, the reviewer, the title and the full text. Alongside it: ReviewProfiles (your listings, one per platform per site), Locations (name, city, country, coordinates), RatingsHistory (what the platform itself reported), ReviewSummary (a monthly rollup) and ReviewChanges (a stream of inserts, updates and deletes). Reviews associates to ReviewProfiles on ReviewProfileId, and ReviewProfiles to Locations on LocationId.

On Qlik’s schedule, which is the one you already run for everything else. Reviewflowz does not push into Qlik and there is nothing to trigger from our side. For an incremental reload, ReviewChanges is the mechanism: keep the highest change id you loaded, page everything above it on the next run, and re-read the reviews it names. We do not claim Qlik folds a filter into the feed request the way Power Query does, because Qlik does not document that.

A few lines, and they are the same few lines every time. Each entity set has its own field called Id, and Qlik associates tables on identically named fields, so you rename them as you load: Id as ReviewProfileId on ReviewProfiles, Id as LocationId on Locations. Leave them alone and Qlik will build a synthetic key across three unrelated Id fields, which is the classic way a Qlik model goes wrong. Renaming them is the whole of the work.

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.

Yes. Connecting the listing loads its review history, so the trend line is full from the first reload rather than filling up over the next quarter. That matters more here than on most platforms, because Google review volume tracks footfall: without last year to select against, you cannot tell a bad month from a busy one.

It is for a different job. Reviewflowz reporting answers the questions everyone asks every month. Qlik is where you go when one of those answers raises a question nobody planned for, and you want to follow it through location, language and week without stopping to ask for a report.

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.