Skip to content
Book a demoStart free
Connectors

Appfigures connector

Set up the Appfigures connector in Kaivo: authentication, configuration, the 11 BigQuery tables it syncs, and answers to common questions.

Appfigures connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Appfigures data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your marketing and sales data instead of moving it.

Sync your Appfigures app store data into BigQuery with Kaivo to analyse downloads, revenue, and ratings across your apps.

CategoryMarketing & Sales, Tech
AuthenticationAPI key
SetupSelf-service

Getting started with the Appfigures connector

Section titled “Getting started with the Appfigures connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Appfigures account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your API Key.

Field Description
API Key

When you set up the connector, you provide:

Field Description
Search Store
App store to include in reports (e.g. apple, google_play).

| | Start Date |

Any data before this date will not be fetched.

| | Group By |

Dimension used to group report data.

|

Kaivo syncs 11 tables from Appfigures into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

data_categories (9559 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
_12__active BOOL
_12__device STRING
_12__hidden BOOL
_12__id FLOAT64
_12__name STRING
_12__store STRING
_12__storefront STRING
_42__active BOOL
_42__device STRING
… and 9549 more columns

Repeating fields are split into their own tables, listed here with their column counts.

  • data_categories___12__subcategories (4 columns)
  • data_categories___42__parent__subcategories (4 columns)
  • data_categories___42__subcategories (4 columns)
  • data_categories___43__parent__subcategories (4 columns)
  • data_categories___43__subcategories (4 columns)
  • data_categories___44__parent__subcategories (4 columns)
  • data_categories___44__subcategories (4 columns)
  • data_categories___45__parent__subcategories (4 columns)
  • data_categories___45__subcategories (4 columns)
  • data_categories___46__parent__subcategories (4 columns)
  • data_categories___46__subcategories (4 columns)
  • data_categories___47__parent__subcategories (4 columns)
  • data_categories___47__subcategories (4 columns)
  • data_categories___48__parent__subcategories (4 columns)
  • data_categories___48__subcategories (4 columns)
  • data_categories___49__parent__subcategories (4 columns)
  • data_categories___49__subcategories (4 columns)
  • data_categories___50__subcategories (4 columns)
  • data_categories___51__subcategories (4 columns)
  • data_categories___52__subcategories (4 columns)
  • data_categories___53__subcategories (4 columns)
  • data_categories___54__subcategories (4 columns)
  • data_categories___55__subcategories (4 columns)
  • data_categories___56__subcategories (4 columns)
  • data_categories___57__subcategories (4 columns)
  • data_categories___58__subcategories (4 columns)
  • data_categories___59__subcategories (4 columns)
  • data_categories___60__subcategories (4 columns)
  • data_categories___61__subcategories (4 columns)
  • data_categories___62__subcategories (4 columns)
  • data_categories___63__subcategories (4 columns)
  • data_categories___64__subcategories (4 columns)
  • data_categories___65__subcategories (4 columns)
  • data_categories___66__subcategories (4 columns)
  • data_categories___67__subcategories (4 columns)
  • data_categories___68__subcategories (4 columns)
  • data_categories___69__subcategories (4 columns)
  • data_categories___70__subcategories (4 columns)
  • data_categories___71__subcategories (4 columns)
  • data_categories___72__subcategories (4 columns)
  • … and 1251 more subtables
products_mine_search (6 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
metadata__resultset__count FLOAT64
metadata__resultset__page FLOAT64
metadata__resultset__total_count FLOAT64
metadata__resultset__total_pages FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Repeating fields are split into their own tables, listed here with their column counts.

  • products_mine_search__results (4 columns)
reports_ads (10 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
clicks FLOAT64
ctr STRING
ecpm STRING
fillrate STRING
impressions FLOAT64
requests FLOAT64
requests_filled FLOAT64
revenue STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
reports_adspend (9 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
clicks FLOAT64
cost STRING
cpa STRING
cpc STRING
ctr STRING
impressions FLOAT64
installs FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
reports_ratings (17 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
average STRING
five_star_percent STRING
four_star_percent STRING
negative FLOAT64
neutral FLOAT64
new_average STRING
new_negative FLOAT64
new_neutral FLOAT64
new_positive FLOAT64
… and 7 more columns

Repeating fields are split into their own tables, listed here with their column counts.

  • reports_ratings__breakdown (4 columns)
  • reports_ratings__new (4 columns)
reports_revenue (17 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
ads STRING
business STRING
edu STRING
gross_business STRING
gross_edu STRING
gross_iap STRING
gross_returns STRING
gross_sales STRING
gross_subscriptions STRING
… and 7 more columns
reports_sales (43 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
app_downloads FLOAT64
app_returns FLOAT64
app_returns_amount STRING
app_revenue STRING
business_downloads FLOAT64
business_revenue STRING
downloads FLOAT64
edu_downloads FLOAT64
edu_revenue STRING
… and 33 more columns
reports_subscriptions (35 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
activations FLOAT64
active_discounted_subscriptions FLOAT64
active_free_trials FLOAT64
active_grace FLOAT64
active_subscriptions FLOAT64
active_trials FLOAT64
actual_revenue STRING
all_active_subscriptions FLOAT64
all_subscribers FLOAT64
… and 25 more columns
status (6 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
avatar_url STRING
email STRING
id FLOAT64
name STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
usage (39 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
api_requests__history__history___2024_08_08_t00_00_00_z FLOAT64
api_requests__history__history___2024_08_09_t00_00_00_z FLOAT64
api_requests__history__history___2024_08_10_t00_00_00_z FLOAT64
api_requests__history__history___2024_08_11_t00_00_00_z FLOAT64
api_requests__history__history___2024_08_12_t00_00_00_z FLOAT64
api_requests__history__history___2024_08_13_t00_00_00_z FLOAT64
api_requests__history__history___2024_08_14_t00_00_00_z FLOAT64
api_requests__history__history___2024_08_15_t00_00_00_z FLOAT64
api_requests__history__history___2024_08_16_t00_00_00_z FLOAT64
… and 29 more columns
users (23 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
account__auto_import BOOL
account__company STRING
account__id FLOAT64
account__is_premium BOOL
account__last_import STRING
account__name STRING
account__plan STRING
account__plan_id FLOAT64
active BOOL
… and 13 more columns

Repeating fields are split into their own tables, listed here with their column counts.

  • users__entitlements (4 columns)

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Appfigures supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Appfigures?

Section titled “How long does the initial sync take for Appfigures?”

It depends on how much history is in your Appfigures account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Appfigures’s schema changes?

Section titled “What happens when Appfigures’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Appfigures, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Appfigures instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Appfigures connector in Kaivo and all of its synced data is deleted with it.

Combine reports_revenue and reports_sales to track app store income over time and by product.

Join reports_ads and reports_adspend to compare ad cost against the revenue it drives.

Use reports_ratings to watch how app sentiment shifts after releases.

Use reports_subscriptions to follow recurring revenue and churn across your apps.

Use Appfigures data in your AI and BI tools

Section titled “Use Appfigures data in your AI and BI tools”

Once Appfigures data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Appfigures data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Appfigures connector pricing and plan details.