Facebook Custom Audiences
Sync an Ours Privacy audience to Meta as a Custom Audience with your own Meta OAuth app and selected SHA-256 hashed identifiers.
Facebook Custom Audiences sends the members of an Ours Privacy audience to a Meta ad account. Ours Privacy creates one Custom Audience for each attached audience and replaces its membership during the daily sync.
Before you start
- A Meta ad account where the connected user can manage Custom Audiences.
- Meta Custom Audience terms accepted for the business that owns the ad account.
- Your own Meta app with the Marketing API permission required to manage audiences.
- The Ours Privacy production redirect URI,
https://app.oursprivacy.com/integrations, added to your Meta app's valid OAuth redirect URIs.
Set up the destination
- In Destinations, add Facebook Custom Audiences.
- Enter your Meta App ID and Meta App Secret. Ours Privacy does not use an Ours-owned OAuth app for this destination.
- Select Connect Meta Ads and complete the Meta sign-in flow.
- Enter the Meta Ad Account ID that will own the Custom Audiences. Enter digits only.
- Choose the identifier groups you authorize Ours Privacy to send. Every group starts off.
- Save and publish the destination.
Ours Privacy stores the app secret as a secret setting and does not display it again after save. Reconnect the destination if Meta revokes the connection or its permissions change.
Identifier choices
You choose whether to send each of these groups:
- Phone
- Name and location: first name, last name, city, state, postal code, and country
- Date of birth
- Gender
Each enabled value is normalized for Meta and hashed with SHA-256 before upload. Members with no usable enabled identifier are skipped. Meta never receives your audience conditions or internal audience name.
Sync behavior
Ours Privacy evaluates attached audiences daily and replaces the prior Meta membership, so people who no longer match are removed on the next successful run. The Custom Audience is labeled with the audience's Export Name.
Meta can take time to process uploads, and its matched audience count can be lower than the delivered count in Ours Privacy. Check Meta Ads Manager for the platform-side match and delivery status.
Keep the Export Name neutral. It is visible in Meta Ads Manager and must not describe health information, financial status, or another sensitive characteristic.
Next Steps
- Audience Destinations for how audience syncing works.
- Syncing to destinations to attach this destination to an audience.
- Audience Builder to build and export audiences now.
Need help? Contact support@oursprivacy.com.
How is this guide?

