Home > Destinations > Azure SQL > Branch

Connect Branch to Azure SQL

Connect Branch 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 Branch API pipeline.

Used by the world's leading companies

Export Branch data to Azure SQL

Catchr handles extraction, normalization, and loading automatically.

Centralize

Centralize Branch data in Azure SQL

Bring all your Branch 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 Branch so every dashboard, model, and report works with fresh information.

Analysis

Unify Branch with the rest of your business data

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

Branch metrics and dimensions available in Azure SQL

Access 19 metrics and 89 dimensions from Branch connectors including Cost, Click, Impression, Install, Open, Commerce Event, Date, Last Attributed Touch - Campaign, Last Attributed Touch - Channel, Last Attributed Touch - Advertising Partner Name, Country, Name and many more...

19

Metrics availables

89

Dimensions availables

Connect Branch to Azure SQL in minutes

Move your data from Branch 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 Branch account

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

Client A · Connected sources
5 sources ready
Branch 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 Branch mobile acquisition performance in SQL.

This example summarizes spend, installs, revenue, and cost per install by acquisition campaign.

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

Connect more table to your Branch 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.

Where do I configure a Branch export to Azure SQL?

Connect Branch as a Catchr source. Add your existing Azure SQL database, create a datastream, and configure a job that writes the selected fields to the "ads" table.

Which parts of Branch can be exported to Azure SQL?

Select concrete Branch fields such as Cost, Days from Last Attributed Touch to Event, Days from Last CTA View to Event, and Day of the month. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as apps, campaigns, and ad groups.

How does Catchr process a large Branch backfill into Azure SQL?

Catchr first processes the historical range configured for Branch. Later runs update the "ads" table using the saved frequency and rolling import window.

How are overlapping Branch import windows handled in Azure SQL?

Catchr uses the selected partition field to refresh the relevant Branch period inside "ads". Leaving it blank changes the job to append-only behavior.

What can I analyze with Branch data in Azure SQL?

With Branch data, an Azure SQL query can summarize spend, installs, revenue, and cost per install by acquisition campaign. A Azure SQL view comparing Cost and Days from Last Attributed Touch to Event can feed agency dashboards or downstream BI models.

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.