Home > Destinations > Azure SQL > App Store Connect

Connect App Store Connect to Azure SQL

Connect App Store Connect to Azure SQL and export selected accounts, metrics, and dimensions to your Azure SQL project.

Configure the historical window, destination table, and recurring schedule without maintaining a App Store Connect API pipeline.

Used by the world's leading companies

Export App Store Connect data to Azure SQL

Catchr handles extraction, normalization, and loading automatically.

Centralize

Centralize App Store Connect data in Azure SQL

Bring all your App Store Connect data into your warehouse and make it available for analytics, machine learning, and internal applications.

Data freshness

Keep your AzureSQL tables up to date

Automatically sync new data from App Store Connect so every dashboard, model, and report works with fresh information.

Analysis

Unify App Store Connect with the rest of your business data

Join marketing, finance, CRM, and product data inside the same warehouse.

App Store Connect metrics and dimensions available in Azure SQL

Access 14 metrics and 157 dimensions from App Store Connect connectors including Impressions, Tap, Product Page View, Downloaded Count, Install Count, Review Rating, App Name, Date, Downloaded Source Type, Downloaded Territory, Downloaded Device, Engagement Campaign and many more...

14

Metrics availables

157

Dimensions availables

Connect App Store Connect to Azure SQL in minutes

Move your data from App Store Connect to Azure SQL with a simple setup. Once connected, Catchr handles the ingestion automatically so your warehouse stays up to date without manual work.

Step one

Connect your App Store Connect account

Authenticate your App Store Connect account securely in Catchr. No custom scripts, API maintenance, or engineering work required.

Client A · Connected sources
5 sources ready
App Store Connect 3 advertising accounts Connected
Google Ads 2 advertising accounts Connected
Google Analytics 4 1 web property Connected
HubSpot 1 CRM portal Connected
Step two

Choose the AzureSQL destination

Enter the Azure SQL server host, database, and login details. Catchr verifies the destination before any marketing data is exported.

Destination / Azure SQL Required fields
Host Required
catchr-reporting.database.windows.net
Username Required
catchr_loader
Password Required
••••••••••••
Database Required
marketing_reporting
Step three

Keep your AzureSQL tables updated

Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your AzureSQL table.

Export job / Azure SQL Example
Schema Destination
dbo
Table Per job
meta_ads_daily
Recurring schedule Choose a cadence
Every 6 hours
Daily · 06:00
Weekly · Mon
Export readySelected fields · configured history
Every 6 hours

Review 30-day App Store Connect app growth performance in SQL.

This example summarizes downloads, installs, revenue, and install rate by application.

App Store Connect.sql
BigQuery SQL
30-day window
SELECT
  app_name,
  SUM(downloads) AS downloads,
  SUM(installs) AS installs,
  SUM(revenue) AS revenue,
  SAFE_DIVIDE(
    SUM(installs),
    SUM(downloads)
  ) AS install_rate
FROM `your_project.marketing_raw.app_store_connect_app_daily`
WHERE date >= DATE_SUB(
  CURRENT_DATE(),
  INTERVAL 30 DAY
)
GROUP BY app_name
ORDER BY downloads DESC;
Illustrative SQL — adapt it to the fields and schema selected in your export. Standard SQL

Connect more table to your App Store Connect data

Open the dedicated route for each platform. Its field catalog, reporting grain, historical constraints, and warehouse use cases should be specific to that source.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Before you schedule the job.

Answers about AzureSQL setup, available source data, schedules, table updates, and SQL use cases.

Can Catchr send App Store Connect records directly to Azure SQL?

Add App Store Connect in Sources and connect the existing Azure SQL database in Storage. A datastream defines the route, while the job loads the chosen fields into "app versions".

How much control do I have over App Store Connect fields in Azure SQL?

Select concrete App Store Connect fields such as Engagement Count, Impressions, Page View, and Day of the month. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as apps, app versions, and downloads.

How should I configure recurring App Store Connect imports in Azure SQL?

Define the first App Store Connect fetch, run frequency, and lookback window in the "app versions" job. Each scheduled run replaces data inside the configured period.

How do I prevent duplicate App Store Connect rows in Azure SQL?

Use a supported date field to partition "app versions". Recurring App Store Connect runs can then update the selected window instead of adding another copy of the same period.

How can a team use App Store Connect data after it reaches Azure SQL?

With App Store Connect data, an Azure SQL query can summarize downloads, installs, revenue, and install rate by application. Model Engagement Count and Impressions in SQL, then expose the result to dashboards, internal tools, or recurring client reports.

Does my Azure SQL database need to exist before I connect it?

Yes. Connect an existing Azure SQL  database first. The Catchr job creates and populates the destination table you configure inside that database.

Can I load several marketing sources into the same Azure SQL  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.

Still have a question ? 

Our teams is always here to responds to any question you could have about our data connector.