---
title: "Facebook Ads to Snowflake: Connector Setup and SQL"
canonical: "https://www.owox.com/blog/articles/facebook-ads-to-snowflake-data-marts"
updated: "2026-10-29"
---

# How to load Facebook Ads data into Snowflake with OWOX Data Marts

To get Facebook Ads data into Snowflake, create a connector Data Mart, sign in with Facebook, choose the Ad Insights endpoint and the fields you need, and publish. The connector creates the table in your Snowflake account, loads one row per ad per day, and refreshes it on a schedule you set.

[Snowflake](/blog/topics/snowflake) · Updated October 1, 2026 · [Vadym Kramarenko](/team/vadym-kramarenko) · 9 min read

![How to load Facebook Ads data into Snowflake with OWOX Data Marts](https://cdn.owox.com/www/content-marketing-article/facebook-ads-to-snowflake-data-marts/thumbnail/2-pk59wj.png/public)

Facebook Ads Manager answers questions about Facebook. The moment someone asks how Facebook compares with Google Ads, or what a campaign’s spend brought back in orders, the data has to leave Meta and sit next to everything else. For a team on Snowflake, that means a table in Snowflake.

This guide sets that up with the Facebook Ads [connector](/product/data-connectors) in [OWOX Data Marts](https://www.owox.com/app-signup). It covers the setup, what the table looks like once it lands, the one Snowflake detail that trips up almost everyone on the first query, and the SQL to start with.

## What you end up with

One table in your own Snowflake account, `facebook_ads_ad_account_insights`, with one row per ad per day. Each row carries the campaign, ad set and ad it belongs to and the metrics you selected: impressions, clicks, spend, reach and so on.

The connector does three jobs and no more. It calls the Meta Marketing API, writes the result into that table, and repeats on a schedule. It does not reshape or model the data. What you do with the table afterwards is SQL you write, which is the point: the logic stays yours.

## Before you start

**In Meta.** A Facebook user who can open the ad account with the role of Admin, Advertiser or Analyst, and the numeric ad account ID. You find the ID in Ads Manager under Account Overview.

**In Snowflake.** A storage of type [Snowflake](/data-storages/snowflake) connected to your project. The [storage guide](https://docs.owox.com/docs/storages/supported-storages/snowflake/) asks for the account identifier, a warehouse and either a key pair, which it recommends, or a username with a programmatic access token. The role has to be allowed to create a database, a schema and tables, because the connector creates them on the first run if they are missing.

Give the connector a small warehouse of its own with auto-suspend on. A daily load is a short job, and [Snowflake pricing explained](/blog/articles/snowflake-pricing-cost-control) shows why the warehouse it runs on decides what it costs.

## The Turning Point

OWOX Data Marts

See your first report built in real time. _15 minutes._

1.  Connect your data warehouse
2.  Pick your metrics
3.  Get a live Google Sheets report

In the time it takes to write a ticket. Then imagine never writing that ticket again.

[Book a Demo](/book-a-call)

We'll use your actual use case

## Step 1: create the Data Mart

Click **New Data Mart**, give it a title such as “Facebook Ads Insights”, pick the Snowflake storage and click **Create Data Mart**.

On the Data Setup tab, set **Definition Type** to **Connector** and choose **Facebook Ads**.

## Step 2: connect the ad account

There are two ways to authenticate.

**Continue with Facebook** is the short one. Sign in as the user who has access to the ad account and confirm. The connector keeps the grant renewed for as long as Meta keeps it valid.

**Manually** is for cases where you want your own Meta app: an access token, an App ID and an App Secret. The [credentials guide](https://docs.owox.com/packages/connectors/src/sources/facebook-marketing/credentials/) walks through creating the app. The token needs the `ads_read` and `ads_management` permissions. The connector only reads; the second permission is what Meta requires for account and ad metadata.

![Edit Connector form for Facebook Ads in OWOX Data Marts on a Snowflake Data Mart, with a Continue with Facebook button, a Manually link and an Account IDs field – sign-in is one click, with manual credentials as the fallback](https://cdn.owox.com/www/content-marketing-article/facebook-ads-to-snowflake-data-marts/screens/1.png/public)

Then enter the **Account IDs**. Use the numbers only, without the `act_` prefix. Several accounts go in one field, separated by commas or semicolons, and the signed-in user needs access to each of them.

## Step 3: choose the endpoint and the fields

An endpoint is one kind of data from the API, and **each Data Mart loads one endpoint**. For reporting on spend and results, that endpoint is **Ad Insights** (`ad-account/insights`): daily metrics for every ad.

The others are there when you need them:

*   **Ad Insights by** age and gender, country, region, device platform, publisher platform and position, product ID or link URL asset. The same metrics, split by one more dimension.
*   **Ad Insights by Ad Set** and **Ad Insights by Campaign**. Metrics aggregated at that level, with reach deduplicated the way Ads Manager shows it.
*   **Ads** and **Ad Creatives**. Names, statuses and creative details, without metrics.

If you need a breakdown and the plain insights, that is two Data Marts and two tables.

Next, select fields. The ad ID and the two date fields are always included, because they are the keys the connector uses to match rows. Everything else is your choice.

![Connector Fields panel for Facebook Ads in OWOX Data Marts showing 24 of 100 fields selected for ad-account/insights, with ad\_id, date\_start and date\_stop locked as keys – you load only the columns you will use](https://cdn.owox.com/www/content-marketing-article/facebook-ads-to-snowflake-data-marts/screens/2.png/public)

Select what you will report on and leave the rest. You can add fields later, and the connector adds the new columns to the table.

The last screen asks where to write: database, schema and table. The setup proposes a database named after the source, the schema `PUBLIC` and a table named after the endpoint. If you plan to load several ad platforms, one shared database for all of them keeps later queries shorter. The examples in this guide use `ads_owox`.

## Step 4: publish and run

Click **Publish & Run Data Mart**. The first run loads data from the first day of the previous month up to today, and can take a few minutes.

When it finishes, the Data Setup tab shows the source, the Snowflake table it writes to, and every column with its type.

![Data Setup tab of a Facebook Ads connector Data Mart in OWOX Data Marts, showing the FacebookMarketing source, the Snowflake database, schema and table it writes to, and the output schema with ad\_id, date\_start and date\_stop as keys – the table is in your account, not in a vendor’s](https://cdn.owox.com/www/content-marketing-article/facebook-ads-to-snowflake-data-marts/screens/3.png/public)

## Step 5: load history and set the schedule

Two more things turn a first load into a pipeline.

**History.** Click **Manual Run** and choose **Backfill (custom period)**. One backfill run covers at most 31 days, so a full month fits in one run. For a year of history, run the months one after another, each after the previous one has finished.

![Manual Run panel in OWOX Data Marts with Backfill selected, start and end date fields, and a note that one backfill run can cover at most 31 days – history is loaded month by month](https://cdn.owox.com/www/content-marketing-article/facebook-ads-to-snowflake-data-marts/screens/4.png/public)

**Schedule.** Without a trigger, the Data Mart does not run again. Open the **Triggers** tab, add a trigger of type **Connector Run** and choose daily, weekly, monthly or an interval, with the time zone it should follow.

![Create Scheduled Trigger form in OWOX Data Marts on the Facebook Ads Data Mart, with trigger type Connector Run, a daily schedule at 09:00 and a time zone – the load repeats without anyone starting it](https://cdn.owox.com/www/content-marketing-article/facebook-ads-to-snowflake-data-marts/screens/5.png/public)

Each scheduled run is incremental. It starts from the last date it loaded minus the **Reimport Lookback Window**, two days by default, and rewrites those days. That is how late-attributed conversions and corrected spend find their way into rows that were already loaded. If your attribution window is longer, raise the lookback in the connector’s advanced settings.

Rows are merged on the keys, so re-importing a day replaces it. It does not duplicate it.

## What the table looks like in Snowflake

In this setup the data is in database `ads_owox`, schema `PUBLIC`, table `facebook_ads_ad_account_insights`.

Three things are worth knowing before you query it.

**The names are case-sensitive.** The connector creates the schema, the table and every column with quoted names, exactly as written. In Snowflake that makes them case-sensitive, and an unquoted name is read as upper case. So this fails with “does not exist or not authorized”:

```
SELECT campaign_name, spend
FROM ads_owox.public.facebook_ads_ad_account_insights;
```

and this works:

```
SELECT "campaign_name", "spend"
FROM ads_owox."PUBLIC"."facebook_ads_ad_account_insights";
```

The database name is not quoted. Everything below it is.

**Metrics are numbers, results are text.** `impressions`, `clicks`, `spend`, `reach`, `cpc`, `cpm` and `ctr` arrive as numeric columns and `date_start` as a date. Fields that Meta returns as lists, such as `actions`, `conversions` and `conversion_values`, arrive as text holding the list, and need parsing before they can be summed.

**The grain is ad and day.** `date_start` and `date_stop` are the same day for daily data. Campaign and ad set names are repeated on every row, so no join is needed for a campaign report.

## Query the data

Both queries below were validated on Snowflake against a table loaded by the connector.

Spend, clicks and impressions by campaign and day, for the last 30 days:

```
SELECT
  "date_start" AS date,
  "campaign_name" AS campaign,
  SUM("impressions") AS impressions,
  SUM("clicks") AS clicks,
  SUM("spend") AS spend
FROM ads_owox."PUBLIC"."facebook_ads_ad_account_insights"
WHERE "date_start" >=
  DATEADD(day, -30, CURRENT_DATE())
GROUP BY "date_start", "campaign_name"
ORDER BY date, spend DESC;
```

Sum the base metrics and compute ratios from the sums. Averaging the `cpc` or `ctr` column across rows gives every ad the same weight, whatever it spent.

Facebook next to other channels, one row per day and channel:

```
SELECT
  "date_start" AS date,
  'facebook' AS channel,
  SUM("impressions") AS impressions,
  SUM("clicks") AS clicks,
  SUM("spend") AS spend
FROM ads_owox."PUBLIC"."facebook_ads_ad_account_insights"
GROUP BY "date_start"

UNION ALL

SELECT
  "stat_time_day" AS date,
  'tiktok' AS channel,
  SUM("impressions") AS impressions,
  SUM("clicks") AS clicks,
  SUM("spend") AS spend
FROM ads_owox."PUBLIC"."tiktok_ads_ad_insights"
GROUP BY "stat_time_day";
```

The second query is the start of a unified spend table. [Self-service marketing analytics on Snowflake](/blog/articles/snowflake-self-service-marketing-analytics) takes it further, and a view over the connector table is a good place to rename the columns once so nobody downstream has to think about quoting.

## From table to report

A connector Data Mart is a Data Mart like any other, so it can be reported from directly. On the **Destinations** tab you attach reports to [Google Sheets](/product/spreadsheets), Data Studio, Slack or email, each with its own columns and schedule.

![Destinations tab of the Facebook Ads Data Mart on Snowflake in OWOX Data Marts, listing Data Studio, Email, Slack and a Google Sheets report with a successful last run – the loaded table is delivered where the team reads it](https://cdn.owox.com/www/content-marketing-article/facebook-ads-to-snowflake-data-marts/screens/6.png/public)

For anything beyond the raw table, write the query you want people to read, such as the channel-by-day one above, and publish that as its own Data Mart. [Snowflake reports in Google Sheets](/blog/articles/automate-snowflake-google-sheets) covers the delivery step by step.

## When a run fails

Open **Run History** first. It shows the error Meta returned, and most of them fall into a few groups.

*   **Token errors** such as “Session has expired”. Meta invalidated the grant. Reconnect with Facebook in the connector settings.
*   **Account cannot be loaded.** The ID includes `act_`, or the signed-in user lost access to that account.
*   **One account of several fails.** Run with one ID at a time to find it.
*   **“Please reduce the amount of data”.** The request is too large. Shorten the backfill period, select fewer fields, or lower **API Page Limit** in the advanced settings.
*   **Rate limits.** Meta throttled the app or the account. Wait and rerun, and schedule less often if it repeats.
*   **Empty result with no error.** Check the same dates in Ads Manager. There may have been no delivery.

## Where to go next

The same setup works for the other sources, and every table lands in the same Snowflake account: [Google Ads](/blog/articles/google-ads-data-snowflake-owox), [Microsoft Ads](/blog/articles/microsoft-ads-snowflake-owox), [LinkedIn Ads](/blog/articles/linkedin-ads-to-snowflake), [TikTok Ads](/blog/articles/tiktok-ads-data-snowflake), [Reddit Ads](/blog/articles/reddit-ads-to-snowflake) and [Shopify](/blog/articles/shopify-data-to-snowflake).

If your warehouse is Databricks, the steps are the same and the naming differs: see [Facebook Ads to Databricks](/blog/articles/connect-facebook-ads-to-databricks). For the platform itself, start with [what Snowflake is and how it works](/blog/articles/snowflake-data-warehouse-explained).

## FAQ

## Frequently Asked Questions

Does the connector change anything in my Facebook ad account?

No. The connector only reads data. A manual access token needs the ads\_read and ads\_management permissions because Meta requires the second one for ad account and ad metadata, but the connector does not create or edit ads. The data it reads is written to tables in your own Snowflake account.

Can I get AI summaries of Facebook Ads data in Snowflake?

Yes. AI Insights in OWOX Data Marts runs on a published Data Mart and delivers a written summary to email, Slack, Microsoft Teams or Google Chat on a schedule. Point it at a Data Mart where spend is already converted from microcurrency, so the summary reads the same numbers as your reports.

How do incremental loads and the lookback window work?

Each scheduled run is incremental. It starts from the last date it loaded minus the Reimport Lookback Window, which is two days by default, and rewrites those days, so late-attributed conversions and corrected spend update rows that were already loaded. Rows are merged on the ad ID and dates, so a re-imported day is replaced and not duplicated. Run History lists every run with its status.

How can I combine Facebook Ads with other channels in Snowflake?

Load each platform with its own connector Data Mart so every table is in the same Snowflake account. Then write one query that selects date, channel, impressions, clicks and spend from each table and combines them with UNION ALL, mapping each platform's own column names. Publish that query as a Data Mart so every report reads the same definition.

Why does my query say the Facebook Ads table does not exist in Snowflake?

The connector creates schema, table and column names quoted, which makes them case-sensitive in Snowflake, and an unquoted name is read as upper case. Write the names in double quotes exactly as created, for example ads\_owox."PUBLIC"."tiktok\_ads\_ad\_insights" and "stat\_time\_day". The database name is not quoted.

What access do I need to connect Facebook Ads and Snowflake?

In Meta, a Facebook user with the Admin, Advertiser or Analyst role on the ad account, plus the numeric account ID without the act\_ prefix. In Snowflake, a storage connected with an account identifier, a warehouse and a key pair or a username with a programmatic access token. The role must be able to create a database, schema and tables, because the connector creates them on the first run.

How do I load historical Facebook Ads data?

Use Manual Run with the Backfill (custom period) option and set a start and end date. One backfill run covers at most 31 days, so a full month fits in one run. For a longer history, run consecutive periods one after another, starting each after the previous one finishes. The first run after publishing already loads data from the first day of the previous month.

How do I load Facebook Ads data into Snowflake automatically?

Create a Data Mart in OWOX Data Marts on your Snowflake storage, set its definition type to Connector and choose Facebook Ads. Sign in with Facebook, enter the numeric ad account IDs, pick an endpoint such as Ad Insights and the fields you need, then publish. A Connector Run trigger on the Triggers tab repeats the load daily, weekly, monthly or at an interval.

## Who wrote this

![Vadym Kramarenko](https://cdn.owox.com/www/webflow/6798e703afdf787334941cde_Vadym-Kramarenko.png/public)

[Vadym Kramarenko](/team/vadym-kramarenko) Growth Marketing Manager

Vadym Kramarenko is a Growth Marketing Manager at OWOX, where he drives user acquisition and product-led growth strategies. He hosts the OWOX podcast, interviewing analytics professionals about data-driven marketing, attribution, and reporting best practices. Vadym specializes in turning complex analytics concepts into practical, actionable marketing frameworks.

[LinkedIn](https://www.linkedin.com/in/vadim-kramarenko/) · [All articles](/team/vadym-kramarenko)

[Snowflake](/blog/topics/snowflake)

## Related articles

[Snowflake · Automate Snowflake Reports in Google Sheets with OWOX Data Marts · October 1, 2026](/blog/articles/automate-snowflake-google-sheets)

[Snowflake · How to Load Google Ads Data into Snowflake with OWOX Data Marts · October 1, 2026](/blog/articles/google-ads-data-snowflake-owox)

[Snowflake · How to Load LinkedIn Ads Data into Snowflake with OWOX Data Marts · October 1, 2026](/blog/articles/linkedin-ads-to-snowflake)

[See all articles →](/blog/articles)

## Links

Pages this page links to, on this site and on docs.owox.com. Where the page has a Markdown twin, its address follows the link.

- [Snowflake](https://www.owox.com/blog/topics/snowflake) — /blog/topics/snowflake.md
- [Vadym Kramarenko](https://www.owox.com/team/vadym-kramarenko) — /team/vadym-kramarenko.md
- [connector](https://www.owox.com/product/data-connectors) — /product/data-connectors.md
- [OWOX Data Marts](https://www.owox.com/app-signup)
- [Snowflake](https://www.owox.com/data-storages/snowflake) — /data-storages/snowflake.md
- [storage guide](https://docs.owox.com/docs/storages/supported-storages/snowflake)
- [Snowflake pricing explained](https://www.owox.com/blog/articles/snowflake-pricing-cost-control) — /blog/articles/snowflake-pricing-cost-control.md
- [Book a Demo](https://www.owox.com/book-a-call) — /book-a-call.md
- [credentials guide](https://docs.owox.com/packages/connectors/src/sources/facebook-marketing/credentials)
- [Self-service marketing analytics on Snowflake](https://www.owox.com/blog/articles/snowflake-self-service-marketing-analytics) — /blog/articles/snowflake-self-service-marketing-analytics.md
- [Google Sheets](https://www.owox.com/product/spreadsheets) — /product/spreadsheets.md
- [Snowflake reports in Google Sheets](https://www.owox.com/blog/articles/automate-snowflake-google-sheets) — /blog/articles/automate-snowflake-google-sheets.md
- [Google Ads](https://www.owox.com/blog/articles/google-ads-data-snowflake-owox) — /blog/articles/google-ads-data-snowflake-owox.md
- [Microsoft Ads](https://www.owox.com/blog/articles/microsoft-ads-snowflake-owox) — /blog/articles/microsoft-ads-snowflake-owox.md
- [LinkedIn Ads](https://www.owox.com/blog/articles/linkedin-ads-to-snowflake) — /blog/articles/linkedin-ads-to-snowflake.md
- [TikTok Ads](https://www.owox.com/blog/articles/tiktok-ads-data-snowflake) — /blog/articles/tiktok-ads-data-snowflake.md
- [Reddit Ads](https://www.owox.com/blog/articles/reddit-ads-to-snowflake) — /blog/articles/reddit-ads-to-snowflake.md
- [Shopify](https://www.owox.com/blog/articles/shopify-data-to-snowflake) — /blog/articles/shopify-data-to-snowflake.md
- [Facebook Ads to Databricks](https://www.owox.com/blog/articles/connect-facebook-ads-to-databricks) — /blog/articles/connect-facebook-ads-to-databricks.md
- [what Snowflake is and how it works](https://www.owox.com/blog/articles/snowflake-data-warehouse-explained) — /blog/articles/snowflake-data-warehouse-explained.md
- [See all articles →](https://www.owox.com/blog/articles) — /blog/articles.md