Export Status

BPP tracks every sync run in Sync History. Each record represents a completed (or failed) sync for an audience or signal destination.

Destination status

Each audience destination and signal destination has its own current status:

Status	What it means
Ready	Configured, enabled, and waiting for the next scheduled run.
Running	A sync is currently in progress.
Complete	Last run completed successfully. All records were processed.
Partial Complete	Last run completed but some records failed (e.g., a missing identifier for some users). Successful records were still pushed.
Error	Last run failed. No records were pushed. Check the status message for details.

Sync History

Sync History records every completed or failed sync with the following information:

Field	What it shows
Entity Name	The audience or signal that was synced.
Sync Type	Audience or Signal.
Destination Name	The connection used (e.g., "Google Ads — Main Account").
Connection Type	Google Ads, Meta Ads, API Endpoint, etc.
Status	Complete or Error.
Items Total	Total records attempted (users for audiences, events for signals).
Items Processed	Successfully pushed records.
Items Failed	Records rejected or not sent.
Max Event Date	Latest event timestamp among processed records (signal syncs only).
Execution Date	When the sync completed.
Status Message	Error description if the sync failed.

Reading your results

• Complete with some failures is normal — it means the majority of records pushed successfully but some were individually rejected (e.g., an invalid email format). Review the status message for the specific rejection reasons.
• Error means the entire run failed before or during the push — typically a connection issue, API error, or configuration problem. Fix the underlying issue; the next scheduled run will retry automatically.
• Items Processed vs Items Total gives you the effective coverage rate for that run. A consistently low ratio may indicate a data quality issue worth investigating.

Retry behaviour

BPP does not retry a failed run mid-cycle. The next scheduled daily run will attempt to process the data again.

For signal syncs, the latest event date marker only advances on a successful or partial-complete run. If a run fails entirely, BPP will retry all the same events on the next run — nothing is lost.

Filtering Sync History

You can filter Sync History by:

• Sync type (audience or signal).
• Connection / platform.
• Status (Complete or Error).
• Date range.