Sources
The Sources tab of Identity Resolution lists every table BPP links to profiles. For each one it tells you whether it is up to date and, if not, what that means for the audiences and signals built on it.
A source that is not up to date keeps the profiles of its last successful update. So do the audiences and signals built on it. Nothing is lost: the source catches up at its next successful update.
Last update banner
At the top, a banner summarises the last update:
- Result: Completed, Partially completed, Waiting for review, Failed, Stopped or Cancelled.
- Sources: how many were updated, failed or skipped.
- Duration of the update.
While an update is running, the banner says so and the tab refreshes every 30 seconds.
The list of sources
Each row shows:
| Item | Meaning |
|---|---|
| Status | Whether the source is up to date; see Status of a source. |
| Outdated profile ids | A badge shown when some rows still carry profile IDs from earlier updates. They are refreshed at the next successful update. |
| Rows linked and Coverage | Rows linked to a profile, and their share of all rows. Rows without any identifier can never be linked. |
| Last update | When the source was last updated successfully. |
| Problem | One sentence on what went wrong. Hover over it to see the technical error. |
| Audiences and signals | The audiences and signals that use this source and still rely on older profiles, with links to their pages. |
Use the filter to show All, Needs attention or Up to date sources.
Status of a source
The Insights tab (in What each source contributes) and the Sources tab show the same status for a source.
| Status | Meaning |
|---|---|
| Up to date | The last update of the source completed. |
| Partial: history loading | Only the recent rows are linked so far. The rest of the history is linked by the next updates; until then, audiences and signals on this source see the recent data only. |
| Outdated | The source has not been updated recently. |
| Failing | The last update of the source failed. |
| Broken | The source failed several updates in a row and needs attention. |
| Never run | The source has not been processed yet. It will be at the next update. |
| Needs a full rebuild | The source will be read again in full at the next update. |
While an update runs, the status shows where the source is in it instead: Waiting, Reading identifiers, Linking rows to profiles, Processing (a source processed for the first time) or Rebuilding (a full rebuild). A source that is failing keeps showing its problem until the update fixes it. Up to date appears again only when the source is done.
History of a source
Click History on a row to open the history of that source:
- Sparklines of the last 30 updates: coverage, rows linked, new profiles and merged profiles.
- The table of updates, one row per update, with these columns:
- Update and Result;
- Rows read, Rows added and Rows changed;
- Profile ids refreshed;
- New identifiers, New profiles and Profiles merged;
- Coverage.
- Filters by update type, result and date range, plus Download CSV.
Update types:
| Type | Meaning |
|---|---|
| First build | The first time the source was processed. |
| Daily update | The scheduled nightly update. |
| New sources added | An update started because sources were added in the Data Source Manager. |
| Resumed after review | An update that was paused for review and then approved. |
| Data deletion | The deletion of a person's data on request. |
| Initial import | The import of the existing profiles when the source moved to the new engine. |
| Comparison run | A run on a copy, used to compare the new engine with the previous one before the switch. |
| Maintenance | A run started by Bytek for maintenance. |
Merges are counted for every source that contributed to them. A merge between an email from your CRM and a website visitor ID from GA4 appears in both sources, so merges do not add up across sources.
Actions
Only users of the ReconciliationEditor group, and Bytek administrators, see these buttons. Each one asks for confirmation.
- Run update now (top of the tab): BPP reads the new data of every source and refreshes the profiles now, instead of at the next scheduled update. It usually takes less than an hour and uses the processing budget like a daily update.
- Rebuild every source from scratch (option in the confirmation): every source is read again in full and linked with the current configuration. Use it after a source was reloaded or its data was fixed. What it means:
- It takes longer than a daily update and uses more processing budget, because it reads the whole history of every source.
- Profile IDs are kept, so the IDs already sent to ad platforms stay valid. Events already sent are not sent again; events that gain a profile in the rebuild can be sent if they are recent.
- Until it finishes, audiences and signals keep using the profiles of the last update.
- Profiles merged by mistake are not split automatically: they appear in Quarantines for a review.
- Rebuild every source from scratch (option in the confirmation): every source is read again in full and linked with the current configuration. Use it after a source was reloaded or its data was fixed. What it means:
- Force full rebuild (in the history of a source): every row of the source is read again and linked to profiles from scratch. Use it when the source was reloaded or its identifier columns changed. You can run it now or at the next update. It takes longer and costs more than a normal update.