Question 1

What can be synced into Meta?

Accepted Answer

Custom audiences, website conversions and offline conversions. Audiences match on a wide set of identifiers including email, phone, an external identifier, first and last name or a first initial, date of birth, gender, city, state, postal code, country, and mobile advertising identifier, and supplying more of them generally improves match rate. Conversion syncs additionally accept Meta specific click and browser identifiers and login or page identifiers.

Question 2

Should I hash identifiers in Redshift first?

Accepted Answer

No, send normalised plaintext and let the connector hash it. Personal identifiers for audiences and conversions are hashed on the way out, and pre-hashing in your SQL is actively discouraged, because inconsistent normalisation before hashing is one of the main causes of poor match rates. Since normalisation determines how many people actually match, leaving it to one consistent implementation is the safer choice.

Question 3

Does the audience stay in step with the segment?

Accepted Answer

With mirror mode, yes. Add and remove give explicit control, while mirror removes contacts no longer present in the source query, so a suppression or churn audience stays accurate rather than accumulating people who should have left. One sequencing detail: a newly created audience initially exposes add only, and remove and mirror become available on subsequent syncs once the audience exists.

Question 4

What should I watch on the Redshift side?

Accepted Answer

Cluster contention rather than a query bill. Audience models tend to touch large event or customer tables, so select only the identifier columns you map, use a tracking field where the audience grows rather than churning wholesale, and align the sort key with it. Put the connecting user in a suitable workload management queue, since Polytomic does not set one. Meta's own limits are account dependent, and the connector reads its rate limit headers and backs off.

Question 5

How do I connect Redshift to Facebook 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 Meta with OAuth or your own system user token. Then model the audience in Redshift, mapping as many identifiers as you reasonably have since match rate improves with more of them, choose a custom audience or conversions target, and pick add, remove or mirror. Send normalised plain values rather than hashing in SQL.

Connect Redshift with Facebook Ads

Connect Redshift and Facebook Ads with Polytomic

Mirror removes who dropped out

Many identifiers to match on

Website and offline conversions

Trusted by businesses worldwide

Step-by-step integration guide

Connect Redshift in Polytomic

Connect Facebook Ads in Polytomic

Create a sync between Redshift and Facebook 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 Facebook Ads?