Tables Configuration
Tables Configuration — the Datasource Manager page once onboarding is complete — is where you manage the active schema after DSM v2 onboarding. It gives you access to all tables and fields currently active in BPP, letting you refine labels, descriptions, and visibility without triggering a full re-onboarding.
In DSM v2, schema structure is add-only after activation. You can edit labels, descriptions, and visibility, and add new tables via Add Tables. You cannot rename, retype, or remove existing fields.
How to access it
Open the system menu (the gear in the header) and choose Datasource Manager. The entry appears once the initial DSM Onboarding has been activated.
The page shows, from top to bottom: the Datasource & BigQuery Connection details (datasource, connection, GCP project, region, external and internal dataset), the identifier roles, the Unified User Model, the Source Tables and the Platform Generated Tables.
What you can do
| Action | Description |
|---|---|
| Edit field label | Change the display name of a field as it appears in audience and signal filters. |
| Edit field description | Add or update a short description to help users understand the field's meaning. |
| Show / hide fields | Toggle field visibility to keep the filter panel clean. Hidden fields are not deleted — they can be shown again at any time. |
| Edit the user model | Change fields, sources, priority and aggregation rules. See Editing the User Model After Activation. |
| Set identifier roles | Tell BPP whether each identifier type is an email, a device ID, a person ID or an object ID. See Identifier roles. |
Personal data
There is no PII control in DSM v2. What protects personal data is where it lives and how it leaves:
- It stays in your BigQuery project. The
_bppcopies and the identity resolution tables are written to your own datasets. BPP does not copy your identifiers into its own database. - Ad platforms receive it hashed. Google Ads, Meta Ads, Microsoft Ads and OpenAI Ads get emails and phone numbers normalized and SHA-256 hashed at send time, in the format each platform requires. A value already hashed in your warehouse is sent as it is, never hashed twice.
- External enrichment is closed for emails and phones. Columns declared as Email or Personal Phone identifiers are not shared with enrichment providers or language models. Bytek staff can open a column on request.
Earlier versions of BPP had a Requires hashing checkbox and a PII flag on each field. Both are gone.
How to save changes
After making edits, click Save changes at the bottom of the page. Changes take effect immediately — no reconciliation is required.
Identifier roles
Identifier types can have any name (mail_cliente, ga_cookie, azienda_id…), so BPP needs to know what each one is to link profiles safely. The Identifier roles section lists every identifier type of your tables, the columns it is read from, and its role:
| Role | Use it for | What it changes |
|---|---|---|
| Email addresses. | An email linked to many devices is checked for shared logins, such as a shop email used at the counter. | |
| Device / anonymous ID | Cookies, GA4 client IDs, mobile ad IDs and other browser or device IDs. | A profile made only of device IDs counts as anonymous. |
| Person ID | IDs of a person in one of your systems: CRM, account or loyalty IDs. | None of the above. |
| Object ID | IDs of objects, not of people: cases, opportunities, orders. | It never counts towards group size limits. |
BPP suggests a role from the type and column names. A suggestion reads Suggested by BPP, and a role you changed reads Set by you. When a suggestion is wrong, for example a cookie called ga_cookie shown as a Person ID, pick the right role and click Save roles. The new role applies from the next update of the profiles. To go back to the suggestion, select the suggested role again.
Only users who can edit Tables Configuration can change roles. Everyone else sees them read-only.
Adding new tables
If your BigQuery dataset has grown and you need to bring new tables into BPP, use the Add Tables flow. Click Discover New Tables on the Datasource Manager page to start the process. The same flow also picks up new columns detected on tables you've already onboarded — see Column drift on existing tables.
Editing the user model
Field names, sources, and aggregation rules from Step 3 aren't locked in after activation — see Editing the User Model After Activation.
Starting over
Start over, beside the page title, deletes the datasource and its whole configuration, so you can reconnect your warehouse and onboard again from scratch. You must type START OVER to confirm. It cannot be undone.
Warning icons on tables and fields
You may occasionally see a warning icon next to a table or field on this page. This means BPP's Schema Integrity Check has detected a mismatch between what's registered here and your live BigQuery dataset. Hover over the icon for details, and see the Schema Integrity Check page for what it means and what to do.