Facebook Custom Audiences

Not available yet. Facebook Custom Audiences appears in the destinations list and accepts credentials, but it cannot sync audiences. Do not plan campaigns around it. To sync an audience today, use Vibe CTV Audiences.

Facebook Custom Audiences will let you send the members of an Ours Privacy audience to a Meta ad account as a custom audience. This page covers what you can do today and what to get ready in Meta.

---

What works today

You can add the destination and save its credentials, so the setup is ready in advance. That is the extent of it.

Attaching an audience to this destination has no effect in Meta: no custom audience is created, and nothing is uploaded. The attempted sync is recorded against the audience as failed, with a message saying the destination cannot sync yet, so it will not look like a healthy sync that quietly produced nothing.

---

Meta-side prerequisites

Get these in place before you plan campaigns around the destination. Meta enforces them, so a valid credential on its own is not enough.

• Access to the Meta ad account that will own the custom audiences, with a role that lets you manage audiences.
• Custom Audience Terms of Service accepted for the business that owns that ad account. Meta blocks creating or editing a customer-list custom audience until they are signed, and they are accepted per person per business from inside one of that business's ad accounts. If you plan to use a system user token, a non-system user in the business has to accept the terms first: a system user cannot accept them on the business's behalf. Meta's Custom Audience Terms of Service page covers the edge cases for shared and on-behalf-of accounts.
• An audience large enough to be worth uploading. Meta's guidance for customer lists is at least 1,000 people, and a list that has not been refreshed in over 30 days is flagged as outdated, which can affect delivery. A daily sync keeps it current.

---

Credentials it will ask for

When you add the destination, the settings page asks for:

• Ad Account ID the Meta ad account that will own the custom audiences, found in Meta Ads Manager under Account Settings. Enter the digits only. Ours Privacy adds the act_ prefix for you.
• Access Token a system user access token with the ads_management permission, generated in Meta Business Settings. Use a system user rather than a personal token: personal tokens expire, and an expired token takes your audience syncs down with it.

---

What to expect when it ships

It will work the way the other Audience Destinations do, described on Audience Destinations: members re-sent daily, each run replacing the previous list so removals propagate on their own, and the audience's Export Name as the only label Meta sees.

Two things worth knowing now, because they affect how you name and size an audience:

• Meta's Business Tools Terms prohibit audience names that reflect or imply health information. The Export Name is what Meta displays in Ads Manager, so keep it meaningless. Ours Privacy blocks Export Names carrying health context regardless of destination.
• The matched audience in Meta will be smaller than the count in Ours Privacy. Meta reports a match score once an upload succeeds, and matches more people from a list carrying more identifiers than email alone.

This page gets updated with the setup steps and the exact sync behavior when it goes live. To be told when that happens, contact your account representative.

---

Next Steps

• Audience Destinations for how audience syncing works.
• Vibe CTV Audiences for the Audience Destination available today.
• Audience Builder to build and export audiences now.

Need help? Contact support@oursprivacy.com.