Question 1

What can be synced into Meta from a data warehouse?

Accepted Answer

Custom audiences, website conversions, and offline conversions. Audiences can be matched 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. Supplying more of them generally improves match rate. Conversion syncs additionally accept Meta specific identifiers such as click and browser identifiers, and login or page identifiers.

Question 2

Does the audience stay in step with my segment?

Accepted Answer

With mirror mode, yes. Add and remove modes give explicit control, while mirror removes contacts that are no longer present in the source query, so a suppression or churn segment 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 to that audience once it exists.

Question 3

Should I hash the data before sending it?

Accepted Answer

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

Question 4

Are there rate limits to worry about?

Accepted Answer

Meta's limits depend on your account and usage rather than being a fixed published number, so the connector reads the rate limit headers Meta returns and backs off automatically instead of assuming a ceiling. That means a large audience build paces itself rather than failing. Minimum usable audience size and how quickly an audience becomes usable are platform controlled and vary by account, region and match rate, so validate those in your own account rather than planning around a fixed figure.

Connect Snowflake with Facebook Ads

Connect Snowflake 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 Snowflake in Polytomic

Connect Facebook Ads in Polytomic

Create a sync between Snowflake 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 Snowflake with Facebook Ads?