06:00 UTC
Google Play Review
Selected accounts
Configured job
MySQL
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Google Play Review
3 advertising accounts
Connected
Google Ads
2 advertising accounts
Connected
Google Analytics 4
1 web property
Connected
HubSpot
1 CRM portal
Connected
Connect your existing MySQL database with its host, port, username, password, and database name. Then create the datastream that defines where the selected source data should go.
Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your MySQL table.
This example summarizes review volume and average rating by location over the last 30 days.
Open the dedicated route for each platform. Its field catalog, reporting grain, historical constraints, and warehouse use cases should be specific to that source.
Answers about MySQL setup, available source data, schedules, table updates, and SQL use cases.
Start with a connected Google Play Review source and an existing MySQL database. Create a datastream between them, then configure the accounts, fields, schedule, and "ratings" table.
Select concrete Google Play Review fields such as Average Rating, Helpful Votes, Rating, and Day of the year. You can rename the chosen columns, preview the result, and write them to MySQL tables such as review sources, locations, and reviews.
Set an initial fetch period for Google Play Review, then choose the frequency and lookback window for the job writing to "ratings". Catchr rewrites that selected period on each run.
The partition field tells Catchr which Google Play Review rows in "ratings" belong to the period being refreshed. If you omit it, every run appends records rather than updating them.
With Google Play Review data, a MySQL query can summarize review volume and average rating by location over the last 30 days. A query built around Average Rating and Helpful Votes can support trend reviews, account comparisons, and operational reporting.
Yes. Connect an existing MySQL database first. The Catchr job creates and populates the destination table you configure inside that database.
Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.
Our teams is always here to responds to any question you could have about our data connector.
Connect your accounts, choose the fields, then schedule the data your team needs in MySQL.
.svg){kind=logo}
.png){kind=logo}
