Manage Audiences

Audience list

From the Audiences list view you can see all audiences in your workspace, along with:

• Target — one icon per destination platform. Hover an icon for the destination's details and current status, with a plain-language explanation when something went wrong (see Reading a status). An icon with a warning marker flags a destination whose last sync completed but rejected a significant share of its users.
• N° of User — current estimated audience size.
• Last Sync — when the last sync ran.
• Active — whether the audience is enabled.
• Status — current state of the audience (Draft, Ready, Running, Complete, Partial Complete, Error, Suspended).

Available actions

Edit

Open an audience to change its name, filter conditions, destination settings, or enabled status.

Changes take effect on the next scheduled sync. If you change the identifier mapping significantly, the next sync will re-upload the full audience list to the destination.

Enable / Disable (Suspend)

Toggle the Enabled switch to start or pause scheduled syncing.

• Enabling a Draft or Suspended audience activates the daily sync schedule. If the audience doesn't yet have a list on the destination platform, BPP creates it automatically.
• Disabling a Ready audience pauses syncing. The audience list already on the destination platform is not removed — it stays there until you delete the audience.

Duplicate

Clone an audience to use as a starting point for a new segment. The copy is created in Draft status. Rename it and adjust the filters before enabling.

This is the safest way to test new filter criteria without touching a live, running audience.

Delete

Deleting an audience stops all future syncs and removes it permanently. BPP also calls the destination platform to delete the remote audience list (e.g., removes the Customer Match list from Google Ads or the Custom Audience from Meta).

If you want to preserve the configuration for future use, use Suspend instead of Delete.

Monitoring syncs

At the top of an audience's detail page, next to the name, the status badge describes the audience as a whole. Click it to jump to the run that explains it in Execution History. Below the subtitle, a row of small pills counts the destinations by status — for example 1 Error · 2 Complete — so you can see at a glance whether every destination is in the same state.

The detail page has three tabs:

• Configuration — the audience's name, filter conditions, and size.
• Destinations — one row per destination, with its User Data Coverage, the audience size reported by the platform over the last 30 days (Audience size · 30d, the analysis cell), and its Status. Click a destination's status to open the run that produced it in Execution History.
• Execution History — every run of this audience, grouped by execution. See Execution History.

Use Run Now on the detail page to trigger a run outside the schedule (5 per hour per audience).

Going deeper than the status

A destination reporting Complete means BPP delivered the list — not that the platform can use it. Click a destination's analysis cell to open Audience Analysis, which reads the list back from Google or Meta: match rate, the sizes the platform will actually serve, whether the list is eligible or has been closed, and why records were rejected.

Handling errors

When an audience destination shows Error status, or Complete with a warning icon:

1. Hover the status. The tooltip explains in plain language what happened and what to do — see Reading a status. Show technical details reveals the original error message; Copy for support copies it, with its category and time, ready to paste into a support request.
2. Common causes:
   • The identifier fields mapped to the destination have many empty values (low coverage).
   • The connection credentials have expired — re-authenticate the connection.
   • Consent is not set to Granted for the destination.
   • The remote audience list was deleted directly on the ad platform — re-enable the audience to recreate it.
3. Fix the underlying issue. The next scheduled sync will retry automatically.