Audience Export
An Audience Export uploads your customer segment to an ad platform as a user list for targeting. The platform receives the list and uses it to match users in its own database for campaign targeting.
How it works
- BPP applies your audience's filter conditions to find the matching customers.
- BPP looks up the identifier fields configured for the destination (e.g., email address, phone number).
- BPP normalises and securely hashes PII fields (email, phone, name) before sending.
- The hashed list is uploaded to the destination platform via its API.
- The sync result (records processed, records failed, timestamp) is saved to Sync History.
What identifier types are supported
Ad platforms match your uploaded users against their own databases using the identifiers you send. BPP supports:
| Platform | Identifiers |
|---|---|
| Google Ads Customer Match | Hashed email, hashed phone |
| Meta Ads Custom Audiences | Hashed email, hashed phone, hashed first name, hashed last name |
| Microsoft Ads Customer Match | Hashed email, hashed phone |
Providing multiple identifiers for the same destination improves the match rate. The Audience Preview panel shows what percentage of your filtered audience has each identifier available — check this before enabling the audience.
Automatic audience creation on the platform
- First sync — BPP creates the remote audience list on the ad platform automatically (e.g., a Google Customer Match list or a Meta Custom Audience). You do not need to create these manually.
- Subsequent syncs — BPP updates the existing list with the current user set.
- When you delete the audience from BPP — BPP also deletes the remote list from the ad platform.
Scheduling
Audience syncs run daily by default. The audience must be in Ready status (enabled) for syncs to run.
Partial syncs
If some users in the audience fail to upload (e.g., a missing identifier or a platform-side rejection), the destination moves to Partial Complete status. The users who uploaded successfully are still included in the remote list — a partial failure does not cancel the whole sync.