Skip to main content

SensorTower API

info

The SensorTower API connector syncs selected Sensor Tower market, app metadata, review, keyword, featured, usage, and sales estimate endpoints into Extract.

Source Setup Guide​

To connect SensorTower API to Extract, provide a SensorTower Auth Token from Sensor Tower API Settings.

The source can be saved and authenticated before report configs are added. During login, Extract validates the token with Sensor Tower's API usage endpoint and does not require app IDs.

Report Configs​

Report configs define which apps and countries Extract should request from Sensor Tower. Each config should have a stable Config Name because the name is added to extracted rows and is used by stream keys.

Each report config supports:

  • Config Name: Stable label for the requested app group.
  • iOS App IDs: Comma-separated App Store numeric IDs, for example 389801252.
  • Android App IDs: Comma-separated package names, for example com.instagram.android.
  • Countries: Optional comma-separated Sensor Tower country codes, for example US,GB,DE. Leave empty to use Sensor Tower defaults for endpoints where country is optional.
  • iOS/Unified Categories: Optional multi-select Sensor Tower category IDs for Creative Gallery Top streams. Leave empty to use 0 (Overall).
  • Android Categories: Optional multi-select Sensor Tower category IDs for Creative Gallery Top streams. Leave empty to use all (Overall).
  • Date Granularity: Used by sales estimate streams. Supported values are daily, weekly, monthly, and quarterly.

Supported Countries​

CodeCountry
AEUnited Arab Emirates
ARArgentina
ATAustria
AUAustralia
BEBelgium
BRBrazil
CACanada
CHSwitzerland
CLChile
CNChina
COColombia
CZCzech Republic
DEGermany
DKDenmark
ECEcuador
ESSpain
FRFrance
GBUnited Kingdom
GRGreece
HKHong Kong
IDIndonesia
ILIsrael
INIndia
ITItaly
JPJapan
KRSouth Korea
LULuxembourg
MXMexico
MYMalaysia
NGNigeria
NLNetherlands
NONorway
NZNew Zealand
PAPanama
PEPeru
PHPhilippines
PLPoland
PTPortugal
RORomania
RURussia
SASaudi Arabia
SESweden
SGSingapore
THThailand
TRTurkey
TWTaiwan
UAUkraine
USUS
VNVietnam
ZASouth Africa
warning

unified_app_ids may still appear in older saved configs, but the current connector now uses it for unified streams such as unified_ad_intel_creatives. Add iOS, Android, and/or unified app IDs as needed.

warning

Some Sensor Tower endpoints require country input. Review streams (ios_get_reviews and android_get_reviews) require at least one country in the report config.

Connection Setup Guide​

Once SensorTower API is connected to a destination, configure:

  • Connection Pull Schedule: Determines how frequently data is extracted.
  • Backfill (Days): Re-requests recent date windows so updated Sensor Tower data replaces previously pulled rows.
  • Destination Settings: Destination-specific settings such as target schema or dataset.
  • Schema Migration Policy: Controls how Extract handles schema changes.

Connector Notes​

  • Extract redacts the Sensor Tower auth token from request error logs.
  • Streams backed by app-specific endpoints only run when the matching iOS or Android app IDs are configured.
  • Streams that do not require app IDs, such as custom_field_list, custom_fields_values, featured_today_stories, and trending_searches, can run without report configs.
  • Sensor Tower API access is plan-dependent. A 401 Not authorized response usually means the token is valid but the account is not entitled to that endpoint or app/report type.
  • Removed unsupported streams include Sensor Tower sales report, acquisition buyers, retained installers, uninstalls, source metrics, unified sales reports, downloads by source, tags for apps, user apps, and unified apps.

Supported Streams​

App Metadata​

  • ios_apps
  • android_apps
  • ios_unified_apps
  • android_unified_apps
  • ios_top_in_app_purchases

App History and Versions​

  • ios_app_history_summary
  • android_app_history_summary
  • ios_app_update_timeline
  • android_app_update_timeline
  • ios_version_history
  • android_version_history

Reviews and Ratings​

  • ios_get_reviews
  • android_get_reviews
  • ios_get_ratings
  • android_get_ratings

Keywords​

  • ios_get_current_keywords
  • android_get_current_keywords
  • trending_searches

Featured Content​

  • featured_today_stories
  • ios_featured_creatives
  • android_featured_creatives
  • ios_ad_intel_creatives
  • android_ad_intel_creatives
  • unified_ad_intel_creatives
  • ios_ad_intel_creatives_top
  • android_ad_intel_creatives_top
  • unified_ad_intel_creatives_top
  • ios_featured_impacts
  • android_featured_impacts

Usage​

  • ios_usage_demographics
  • android_usage_demographics
  • ios_usage_retention
  • android_usage_retention

Sales Estimates​

  • ios_sales_report_estimates
  • android_sales_report_estimates

Custom Fields​

  • custom_field_list
  • custom_fields_values

Data Streams​

android_app_history_summary​

Loading ....

android_app_update_timeline​

Loading ....

android_apps​

Loading ....
Loading ....
Loading ....

android_get_current_keywords​

Loading ....

android_get_ratings​

Loading ....

android_get_reviews​

Loading ....

android_sales_report_estimates​

Loading ....

android_unified_apps​

Loading ....

android_usage_demographics​

Loading ....

android_usage_retention​

Loading ....

android_version_history​

Loading ....

custom_field_list​

Loading ....

custom_fields_values​

Loading ....
Loading ....

ios_app_history_summary​

Loading ....

ios_app_update_timeline​

Loading ....

ios_apps​

Loading ....
Loading ....
Loading ....

ios_get_current_keywords​

Loading ....

ios_get_ratings​

Loading ....

ios_get_reviews​

Loading ....

ios_sales_report_estimates​

Loading ....

ios_top_in_app_purchases​

Loading ....

ios_unified_apps​

Loading ....

ios_usage_demographics​

Loading ....

ios_usage_retention​

Loading ....

ios_version_history​

Loading ....
Loading ....