Question 1

What can be synced into Google Ads?

Accepted Answer

Customer Match user lists and conversions, including a test conversions target for validating a setup before it affects bidding. Audiences match on email, phone, mobile advertising identifier, or a third party user identifier, and on an address built from first name, last name, country code and postal code. Conversions additionally accept click and session identifiers such as gclid, gbraid and wbraid alongside the personal identifiers.

Question 2

Can the audience track my query exactly?

Accepted Answer

That is what mirror mode does. Add and remove give explicit control, while mirror makes the list match the source query, so someone dropping out of the segment is removed rather than lingering. One caveat worth confirming: mirror is not available when the newer Data Manager API is enabled on the connection, so check which API path your connection uses if exact parity matters.

Question 3

How often should an audience sync run?

Accepted Answer

Less often than people assume. Audiences rarely need to be fresher than daily, and each run consumes cluster compute shared with your reporting, so a tight schedule buys little and costs contention. Put the connecting user in an appropriate workload management queue, use a tracking field so repeat reads stay small, and select only the identifier columns you map rather than the whole customer table.

Question 4

How soon can an audience be used?

Accepted Answer

Not immediately, which catches people out. Google's own processing of a user list can take up to 48 hours, and the execution stays in a processing state during that window rather than reporting completion. That is platform side rather than something the sync controls. Minimum usable audience sizes and match rates also vary by account and placement, so validate against your own account rather than assuming a fixed threshold.

Question 5

How do I connect Redshift to Google Ads?

Accepted Answer

Connect Redshift with cluster details, credentials and an S3 staging bucket, over an SSH tunnel if the cluster is private, and connect Google Ads with OAuth, then select the accounts you want to sync. Build a model in Redshift returning the identifiers for your segment, choose a Customer Match list or a conversions target, and pick whether the sync adds, removes or mirrors. Send plain email addresses and phone numbers, since hashing is handled for you.

Connect Redshift with Google Ads

Connect Redshift and Google Ads with Polytomic

Mirror keeps lists exact

Hashing handled for you

Conversions from real outcomes

Trusted by businesses worldwide

Step-by-step integration guide

Connect Redshift in Polytomic

Connect Google Ads in Polytomic

Create a sync between Redshift and Google Ads

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 Redshift with Google Ads?