Revenue · Source connector

SensorTower API ELT Connector

Extract brings SensorTower API revenue data into data warehouses and databases for analysis with the rest of your business data. Teams use it to reconcile revenue, monitor yield, and investigate performance changes. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.

View setup guide

Use cases

What teams use this connector for

Revenue reconciliation

Compare SensorTower API revenue with finance and internal performance records to investigate discrepancies.

Yield and inventory analysis

Use SensorTower API data to monitor yield, inventory, and monetization performance over time.

Performance anomaly detection

Refresh SensorTower API performance views on a flexible schedule to identify unexpected revenue changes.

Flexible reporting cadence

Refresh SensorTower API reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.

Warehouse and database analysis

Use Extract to make SensorTower API revenue 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
`android_ad_intel_creatives`	Fields include _singular_extract_timestamp, ad_formats, ad_type, app_id.	Full refresh
`android_ad_intel_creatives_top`	Fields include _singular_extract_timestamp, ad_formats, ad_type, app_id.	Full refresh
`android_app_history_summary`	Fields include _singular_extract_timestamp, date, negative, positive.	Full refresh
`android_app_update_timeline`	Fields include _singular_extract_timestamp, app_info, category, contains_ad.	Full refresh
`android_apps`	Fields include _singular_extract_timestamp, active, advisories, app_id.	Full refresh
`android_featured_creatives`	Fields include _singular_extract_timestamp, category, country, country_name.	Full refresh
`android_featured_impacts`	Fields include _singular_extract_timestamp, countries, features, types.	Full refresh
`android_get_current_keywords`	Fields include _singular_extract_timestamp, app, keyword_type, rank.	Full refresh
`android_get_ratings`	Fields include _singular_extract_timestamp, app_id, average, breakdown.	Full refresh
`android_get_reviews`	Fields include _singular_extract_timestamp, app_id, content, country.	Full refresh
`android_sales_report_estimates`	Fields include app_id, country, date, report_config_name.	Incremental
`android_unified_apps`	Fields include _singular_extract_timestamp, android_apps, android_publisher_ids, canonical_app_id.	Full refresh
`android_usage_demographics`	Fields include _singular_extract_timestamp, app_id, average_age_total, baseline_data__female_0.	Full refresh
`android_usage_retention`	Fields include _singular_extract_timestamp, app_data, baseline_data, disabled_app_ids.	Full refresh
`android_version_history`	Fields include _singular_extract_timestamp, after, app_info, before.	Full refresh
`custom_field_list`	Fields include _id, _singular_extract_timestamp, authorized, custom_columns_only.	Full refresh
`custom_fields_values`	Fields include _singular_extract_timestamp, global, name, values.	Full refresh
`featured_today_stories`	Fields include _singular_extract_timestamp, country, date, stories.	Full refresh
`ios_ad_intel_creatives`	Fields include _singular_extract_timestamp, ad_formats, ad_type, app_id.	Full refresh
`ios_ad_intel_creatives_top`	Fields include _singular_extract_timestamp, ad_formats, ad_type, app_id.	Full refresh
`ios_app_history_summary`	Fields include _singular_extract_timestamp, date, negative, positive.	Full refresh
`ios_app_update_timeline`	Fields include _singular_extract_timestamp, advisory, advisory__added, advisory__after.	Full refresh
`ios_apps`	Fields include _singular_extract_timestamp, active, advisories, app_id.	Full refresh
`ios_featured_creatives`	Fields include _singular_extract_timestamp, category, country, country_name.	Full refresh
`ios_featured_impacts`	Fields include _singular_extract_timestamp, countries, features, types.	Full refresh
`ios_get_current_keywords`	Fields include _singular_extract_timestamp, app, keyword_type, rank.	Full refresh
`ios_get_ratings`	Fields include _singular_extract_timestamp, app_id, average, breakdown.	Full refresh
`ios_get_reviews`	Fields include _singular_extract_timestamp, app_id, content, country.	Full refresh
`ios_sales_report_estimates`	Fields include app_id, country, date, report_config_name.	Incremental
`ios_top_in_app_purchases`	Fields include _singular_extract_timestamp, app_id, duration, iap_id.	Full refresh
`ios_unified_apps`	Fields include _singular_extract_timestamp, android_apps, android_publisher_ids, canonical_app_id.	Full refresh
`ios_usage_demographics`	Fields include _singular_extract_timestamp, app_id, average_age_total, baseline_data__female_0.	Full refresh
`ios_usage_retention`	Fields include _singular_extract_timestamp, app_data, baseline_data, disabled_app_ids.	Full refresh
`ios_version_history`	Fields include _singular_extract_timestamp, after, app_info, before.	Full refresh
`trending_searches`	Fields include _singular_extract_timestamp, value.	Full refresh
`unified_ad_intel_creatives`	Fields include _singular_extract_timestamp, ad_formats, ad_type, app_id.	Full refresh
`unified_ad_intel_creatives_top`	Fields include _singular_extract_timestamp, ad_formats, ad_type, app_id.	Full refresh

Schema

Data model at a glance

android_ad_intel_creatives

_singular_extract_timestampstring
ad_formatsarray
ad_typestring
app_idstring
breakdown__datejson
breakdown__dimensionsjson
creativesjson
first_seen_atstring

android_ad_intel_creatives_top

_singular_extract_timestampstring
ad_formatsarray
ad_typestring
app_idstring
app_info__app_idstring
app_info__canonical_countrystring
app_info__entity_typestring
app_info__humanized_namestring

android_app_history_summary

_singular_extract_timestampstring
datestring
negativeinteger
positiveinteger
versionjson

android_app_update_timeline

_singular_extract_timestampstring
app_infojson
categorystring
contains_adstring
contains_ad__afterboolean
contains_ad__beforeboolean
content_ratingstring
countrystring

android_apps

_singular_extract_timestampstring
activeboolean
advisoriesstring
app_idstring
app_view_urlstring
apple_watch_enabledstring
bundle_idstring
canonical_countrystring

android_featured_creatives

_singular_extract_timestampstring
categorystring
countrystring
country_namestring
creativesjson
downloadsinteger
downloads_sharenumber
feature_downloadsjson

+2 more

No verified relationships are available in this schema preview.

Connector pairings

Popular destinations

Commonly paired with SensorTower API in Extract workflows.

Why Extract

Why Extract for SensorTower API

Rust-native performanceUse Rust-native data movement to refresh SensorTower API reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
Full run transparencyInspect SensorTower API API activity, execution steps, and timing in Extract's run-level logs when data needs review.
ELT + Reverse ETL in oneCombine SensorTower API data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.

Setup

Auth method	SensorTower Auth Token
Estimated setup time	Est. 10–20 min with access ready; excludes initial sync and approvals
Incremental sync	Full refresh or partition extraction, depending on stream and configuration
Historical backfill	Backfill (Days) reprocesses the configured number of recent days
Sync frequency	15 min, hourly, daily, or custom

View the full setup guide

FAQ

Frequently asked questions

How does Extract handle incremental and full SensorTower API 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 full refresh, partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.

Can I backfill historical SensorTower API data with Extract?

Historical coverage for SensorTower API: Backfill (Days) (backfill): The backfill setting revisits and updates data from the past X days, ensuring the most current and accurate information replaces any previously pulled data. Use the setup guide and run details to confirm the available source records and selected settings.

How can teams monitor SensorTower API data quality and freshness?

Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect SensorTower API 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 SensorTower API?

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 SensorTower API data model look like in the destination?

The Available streams table describes the datasets Extract can read from SensorTower API. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.