Question 1

What Facebook Ads data can I load into Redshift?

Accepted Answer

Structure and numbers. Structure gives you ads, ad sets, campaigns, ad creatives, images and videos. Numbers come as ten daily ad level insight tables: a base table plus breakdowns by action type, country, platform and device, impression device, age, gender, age with gender, and publisher platform. Metrics span spend, impressions, reach, frequency, clicks, CPC, CPM, CTR, conversions, conversion values and video watch measures.

Question 2

How are sort and distribution keys handled on ad tables?

Accepted Answer

Tables Polytomic creates use DISTSTYLE AUTO with the Polytomic identifier column as both distribution and sort key. That is a sensible default, though for breakdown tables you will often want the report date as the sort key since almost every query filters on it. If you tune an existing table yourself, an ordinary incremental run or a truncate style resync keeps your keys. A rebuild drops and recreates the table, which replaces them, so custom keys need reapplying afterwards.

Question 3

How are late Facebook conversions corrected in Redshift?

Accepted Answer

By reading recent days again and merging over the old rows. Insight reports save their position on the report date, read day by day up to yesterday, then reread the last seven days by default. That can be raised, and the code supports up to 28 days to match how long Meta keeps revising. Anything restated beyond your window will not refresh on its own, so set the lookback against your longest attribution window rather than the default.

Question 4

Why does my Facebook Ads history stop after about a year?

Accepted Answer

Because Meta caps reporting history at roughly 13 months, and that limit is at the source rather than anything Polytomic applies. The practical response is to start syncing sooner rather than later. Once a day has loaded and passed the lookback window it stays in your tables permanently, so the cluster ends up holding a longer record than Meta itself will serve. Teams that wait a year to set this up cannot recover the year they skipped.

Question 5

Why load Facebook Ads into a data warehouse?

Accepted Answer

Because spend only means something next to what it produced. Meta reports on Meta, so it cannot tell you which campaigns brought customers who stayed or which audiences earned the best margin. ETL puts ad data beside CRM and billing data so those become ordinary joins, and it gives you a daily record that stops moving rather than a dashboard quietly reattributing history underneath you.

Sync Facebook Ads to Redshift

Sync Facebook Ads to Redshift with Polytomic

Ten insight breakdowns

Sort and distribution keys

Throttles under Meta limits

Or sync Redshift to Facebook Ads

Trusted by businesses worldwide

Step-by-step integration guide

Connect Facebook Ads in Polytomic

Connect Redshift in Polytomic

Create a sync between Facebook Ads and Redshift

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Facebook Ads with Redshift?