Quickstart · Source connector
Google Play ELT Connector
Extract brings Google Play quickstart data into data warehouses and databases for analysis with the rest of your business data. Teams use it to build recurring reporting and compare business activity across systems. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.
View setup guide
Use cases
What teams use this connector for
Business performance reporting
Use Google Play data to monitor recurring activity and investigate meaningful changes over time.
Cross-system analysis
Combine Google Play data with customer, finance, and operational metrics for consistent reporting.
Data quality monitoring
Compare Google Play record totals and reporting periods to identify incomplete or unexpected data.
Flexible reporting cadence
Refresh Google Play reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.
Warehouse and database analysis
Use Extract to make Google Play quickstart data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Connector data
Available streams
| Stream | Description | Sync mode |
|---|---|---|
earnings | Fields include _file, _line, _modified, amount_buyer_currency. | Incremental |
estimated_sales | Fields include _file, _line, _modified, base_plan_or_purchase_option_id. | Incremental |
korean_play_balance_funded | Fields include _file, _line, _modified, order_charged_date. | Incremental |
reviews_overview | Fields include _file, _line, _modified, app_version_code. | Incremental |
stats_crashes_app_version | Fields include _file, _line, _modified, app_version_code. | Incremental |
stats_crashes_device | Fields include _file, _line, _modified, daily_anrs. | Incremental |
stats_crashes_os_version | Fields include _file, _line, _modified, android_os_version. | Incremental |
stats_crashes_overview | Fields include _file, _line, _modified, daily_anrs. | Incremental |
stats_gcm_app_version | Fields include _file, _line, _modified, app_version_code. | Incremental |
stats_gcm_carrier | Fields include _file, _line, _modified, carrier. | Incremental |
stats_gcm_country | Fields include _file, _line, _modified, country. | Incremental |
stats_gcm_device | Fields include _file, _line, _modified, date. | Incremental |
stats_gcm_language | Fields include _file, _line, _modified, date. | Incremental |
stats_gcm_message_status | Fields include _file, _line, _modified, date. | Incremental |
stats_gcm_os_version | Fields include _file, _line, _modified, android_os_version. | Incremental |
stats_gcm_overview | Fields include _file, _line, _modified, date. | Incremental |
stats_gcm_response_code | Fields include _file, _line, _modified, date. | Incremental |
stats_installs_app_version | Fields include _file, _line, _modified, active_device_installs. | Incremental |
stats_installs_carrier | Fields include _file, _line, _modified, active_device_installs. | Incremental |
stats_installs_country | Fields include _file, _line, _modified, active_device_installs. | Incremental |
stats_installs_device | Fields include _file, _line, _modified, active_device_installs. | Incremental |
stats_installs_language | Fields include _file, _line, _modified, active_device_installs. | Incremental |
stats_installs_os_version | Fields include _file, _line, _modified, active_device_installs. | Incremental |
stats_installs_overview | Fields include _file, _line, _modified, active_device_installs. | Incremental |
stats_promotional_content | Fields include _file, _line, _modified, conversion_rate_28_day_rolling. | Incremental |
stats_ratings_app_version | Fields include _file, _line, _modified, app_version_code. | Incremental |
stats_ratings_carrier | Fields include _file, _line, _modified, carrier. | Incremental |
stats_ratings_country | Fields include _file, _line, _modified, country. | Incremental |
stats_ratings_device | Fields include _file, _line, _modified, daily_average_rating. | Incremental |
stats_ratings_language | Fields include _file, _line, _modified, daily_average_rating. | Incremental |
stats_ratings_os_version | Fields include _file, _line, _modified, android_os_version. | Incremental |
stats_ratings_overview | Fields include _file, _line, _modified, daily_average_rating. | Incremental |
stats_store_performance_country | Fields include _file, _line, _modified, country_or_region. | Incremental |
stats_store_performance_traffic_source | Fields include _file, _line, _modified, date. | Incremental |
stats_total_store_performance_country | Fields include _file, _line, _modified, _singular_extract_timestamp. | Incremental |
stats_total_store_performance_traffic_source | Fields include _file, _line, _modified, _singular_extract_timestamp. | Incremental |
subscriptions_country | Fields include _file, _line, _modified, active_subscriptions. | Incremental |
Schema
Data model at a glance
earnings
_filestring_lineinteger_modifiedstringamount_buyer_currencynumberamount_merchant_currencynumberbase_plan_or_purchase_option_idstringbuyer_countrystringbuyer_currencystring
estimated_sales
_filestring_lineinteger_modifiedstringbase_plan_or_purchase_option_idstringcharged_amountnumbercity_of_buyerstringcountry_of_buyerstringcoupon_valuenumber
korean_play_balance_funded
_filestring_lineinteger_modifiedstringorder_charged_datestringorder_charged_timestampintegerorder_numberstringplay_balance_currencystringplay_balance_funding_amountnumber
reviews_overview
_filestring_lineinteger_modifiedstringapp_version_codeintegerapp_version_namestringdeveloper_reply_date_and_timestringdeveloper_reply_millis_since_epochintegerdeveloper_reply_textstring
stats_crashes_app_version
_filestring_lineinteger_modifiedstringapp_version_codeintegerdaily_anrsintegerdaily_crashesintegerdatestringpackage_namestring
stats_crashes_device
_filestring_lineinteger_modifiedstringdaily_anrsintegerdaily_crashesintegerdatestringdevicestringpackage_namestring
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with Google Play in Extract workflows.
Why Extract
Why Extract for Google Play
- Rust-native performanceUse Rust-native data movement to refresh Google Play reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect Google Play API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine Google Play data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.
FAQ
Frequently asked questions
How does Extract handle incremental and full Google Play syncs?
An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Stream schemas define partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.
Can I backfill historical Google Play data with Extract?
Historical coverage for Google Play: Rolling monthly reprocessing of Google Play files that may be updated retroactively; this does not define the initial historical import. Use the setup guide and run details to confirm the available source records and selected settings.
How can teams monitor Google Play data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Google Play API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.
How often can Extract sync data from Google Play?
Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.
What does the Google Play data model look like in the destination?
The Available streams table describes the datasets Extract can read from Google Play. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.