Question 1

Which reports and resources can be pulled?

Accepted Answer

The dated performance reports covering campaigns, ad groups, ads, keywords, search terms, geography, demographics and conversion actions, plus the underlying resource objects such as campaigns, ad groups, budgets, labels and conversion action definitions. Reports carry the metrics, resources carry the structure and naming that make those metrics readable, so most teams take both and join them in the data warehouse.

Question 2

How do incremental reads work?

Accepted Answer

Dated reports are queried on the date segment, one day at a time, with a configurable lookback that defaults to eight days. Recent daily rows are reread and upserted on every run rather than written once and left alone. Non report objects, and any report without a date segment, are read in full each time, which is cheap because those tables are small. Both happen inside the same ETL run.

Question 3

Are conversion restatements picked up?

Accepted Answer

Yes, provided they land inside the lookback. Google attributes conversions after the fact, so a day's numbers keep moving for a while after that day ends. The eight day default covers most attribution windows. If your conversion actions have a longer window, widen the lookback, because a restatement that arrives outside it will not be refreshed automatically and the day will stay wrong in the data warehouse until a full resync.

Question 4

Does Polytomic set sort keys and distribution keys on the tables it creates?

Accepted Answer

For tables it creates, yes. Redshift tables are created with DISTSTYLE AUTO, using the Polytomic identifier column as both the distribution key and the sort key. If you have tuned an existing table with your own keys, an ordinary incremental run or a truncate style resync preserves them. A rebuild that drops and recreates the table replaces them with the generated definition, so custom keys would need reapplying afterwards.

Question 5

Why move Google Ads data into a data warehouse?

Accepted Answer

Because spend only means something next to what it produced. The Google Ads interface reports on itself, so tying a campaign to closed revenue, retention or lifetime value means joining ad data to CRM and billing data. ETL into a data warehouse makes that a SQL problem instead of a spreadsheet export problem, and keeps a daily history you can trust rather than one that quietly reattributes underneath you.

Sync Google Ads to Redshift

Sync Google Ads to Redshift with Polytomic

Eight day default lookback

Reports and resources

Manager accounts supported

Or sync Redshift to Google Ads

Trusted by businesses worldwide

Step-by-step integration guide

Connect Google Ads in Polytomic

Connect Redshift in Polytomic

Create a sync between Google 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 Google Ads with Redshift?