06:00 UTC
Google Play Store
Selected accounts
Configured job
MySQL
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Google Play Store
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 downloads, installs, revenue, and install rate by application.
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.
Connect Google Play Store as a Catchr source. Add your existing MySQL database, create a datastream, and configure a job that writes the selected fields to the "apps" table.
Select concrete Google Play Store fields such as Active Subscriptions, Amount, Canceled Subscriptions, and Day of the month. You can rename the chosen columns, preview the result, and write them to MySQL tables such as apps, app versions, and downloads.
Catchr first processes the historical range configured for Google Play Store. Later runs update the "apps" table using the saved frequency and rolling import window.
Catchr uses the selected partition field to refresh the relevant Google Play Store period inside "apps". Leaving it blank changes the job to append-only behavior.
With Google Play Store data, a MySQL query can summarize downloads, installs, revenue, and install rate by application. A MySQL view comparing Active Subscriptions and Amount can feed agency dashboards or downstream BI models.
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}
