Execution History
Execution History is the record of every sync BPP has run. One entry per run; inside it, one row per destination push that run performed.
That grouping is the thing to understand first. A single audience or signal run pushes to every destination configured on it, and each destination can succeed or fail independently. Execution History shows the run as one line with its overall outcome, and expands to show what happened at each destination.
Where to find it
Two places, showing the same data through the same filters:
- The Execution History tab on an audience, signal, or Profiles Sync detail page — scoped to that one record.
- The standalone run history page — every run of that kind across your workspace: Audience Sync History, Signals Run History, Profiles Sync History.
You can reach the standalone page from the list view's row actions, or from an audience's or signal's analysis view via Open Execution History.
The summary
A four-part header describes the runs currently in range, so you don't have to add up a table to know how things are going.
| Figure | What it shows |
|---|---|
| Success rate | Share of runs in range that completed without errors, with the completed-run count underneath. |
| Runs in range | How many runs the current filters match, over the resolved date range, plus the total number of destination pushes those runs performed. |
| Items processed | Records successfully pushed, out of how many were attempted, with the failed count underneath — tinted red only when it is non-zero. |
| Last run | How long ago the most recent run in range executed, with its exact timestamp. |
Below it, a status distribution bar breaks the runs down by outcome, with a legend and counts.
Runs and destination pushes are different counts, and both are shown deliberately. One run pushing to three destinations is 1 run and 3 destination pushes. A success rate is per run; item counts aggregate across pushes.
Filtering
Search matches the record name or the execution reference — the identifier of the underlying job execution. Paste a reference from a support conversation and you land on that exact run.
Status chips filter by outcome, each showing its own count:
| Chip | What it means |
|---|---|
| Complete | The run finished and every destination push succeeded. |
| Partial | The run finished, but at least one destination push failed. |
| Error | The run failed. |
| Running | A run is currently in progress. |
Profiles Sync has no Partial chip: a Profiles Sync run pushes to a single destination, so it has no partial outcome.
Connection Type narrows to a platform — Google Ads, Meta Ads, and so on. Not available on Profiles Sync, where the destination never varies.
Previews shown / Previews hidden controls whether Preview Mode runs appear in the list. They are included by default; hide them when you are auditing what actually reached a platform and rehearsals are just noise.
More filters are available behind the advanced filter link, including the date range.
Reading a run
Each row shows Status, Name, how many Destinations the run pushed to, the Execution Date, and Items — sortable by date and by item count.
Expand a run to see one row per destination, on the same grid: its own status, the destination name and type, its processed/total item count, and a Preview badge if that push was a rehearsal. Where an export file was produced, a Download CSV action appears on the destination row; download links are short-lived, so click again if one has expired.
A destination push carries its own status, which is also what the destination card on the detail page shows:
| 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. |
Reading your results
- Complete with some failures is normal — the majority pushed successfully and some records were individually rejected (e.g., an invalid email format). Expand the run to see which destination, and open the destination's analysis for the rejection reasons.
- Error means the whole push failed before or during delivery — typically a connection issue, API error, or configuration problem. Fix the underlying cause; the next scheduled run retries automatically.
- Items processed vs attempted gives the effective coverage for that push. A consistently low ratio is a data quality problem worth investigating, not a transient one.
- The platform accepting a push is not the platform recording it. Execution History reports what BPP delivered. To see what the destination actually did with it, use Conversion Analysis for signals or Audience Analysis for audiences.
Retry behaviour
BPP does not retry a failed run mid-cycle. The next scheduled daily run attempts 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 retries all the same events on the next run — nothing is lost.
Running on demand
Use Run Now on an audience, signal, or Profiles Sync to trigger a run outside its schedule. Manual runs are rate-limited to 5 per hour per record, and Preview Mode runs count toward the same limit.