Exports
Exports are how BPP pushes your audience and signal data to connected ad platforms. Every time an audience or signal syncs, BPP records the run and tracks it through to completion or failure.
Export types
| Export type | Driven by | What it does |
|---|---|---|
| Audience Export | Audience | Uploads a user list (Customer Match, Custom Audience) to an ad platform. |
| Signal Export | Signal | Sends conversion events to an ad platform for attribution and bidding. |
How exports are triggered
Exports run automatically. When you enable an audience or signal (set it to Ready), BPP sets up a daily automated sync job for it. The default schedule runs daily, and each run is recorded as a sync history entry.
You can also trigger a run manually from a Signal or Audience page with Run Export. To test an export without sending data to your destinations, enable Preview Mode in the run dialog — see Preview Mode.
Export destinations
Every export goes to a specific destination — a combination of a connection and a configuration (e.g., a specific Google Customer Match list, a Meta Custom Audience, or a Google Ads Conversion Action).
An audience or signal can have multiple destinations. Each destination runs independently — if one fails, the others are not affected.
Monitoring
Monitoring works at three levels of depth:
- Destination status — on the audience or signal detail page, the Destinations tab shows each destination's current status (Ready, Running, Complete, Error), its last sync date, records processed, and any error message.
- Execution History — every run, grouped by execution, with one row per destination push inside it. Available as a tab on the record, or as a workspace-wide page.
- Destination analysis — what the platform itself reports back about the data BPP pushed: Conversion Analysis for signals, Audience Analysis for audiences.
The distinction between the second and the third matters: Execution History tells you what BPP delivered, while the analysis tells you what the destination platform did with it. A run can be Complete and still have low reconciliation on the platform side.