Step 1 — Classify Tables
Classify Your Tables
Every table BPP found in your dataset needs to be one of two things: a record of who your users are, or a record of what they did. That single choice drives the rest of the wizard — which tables you mark identifiers in, which build the user model, and which need a timestamp.
Copilot has already classified everything. You are reviewing its work, not doing it from scratch.
The row
Each row shows the table name, the source dataset, and how many fields it has. On the right:
- an AI classified or AI excluded badge, when the current state is still Copilot's proposal
- an Event / User control
- Mark as unused
Event or User
User tables have one row per person — a CRM contact list, a customer table, a loyalty membership. Event tables have one row per action, each stamped with a time — orders, page views, sign-ins.
The distinction is not cosmetic. Only user tables feed the user model in Step 3, and only event tables can later be used to build signals.
Excluding a table
Mark as unused removes a table from the configuration entirely. Use it for anything that is not about people: a product catalogue, a currency table, a lookup of shipping zones.
Excluding a table does not delete or alter anything in BigQuery. It only tells BPP not to read it.
An unused table shows neither Event nor User as selected, and is counted separately in the footer. If you exclude something by mistake, click Mark as used to bring it back — its previous classification is still there.
The AI badge
The badge marks a row you have not touched. Change the classification, or include a table Copilot excluded, and the badge disappears — so what remains badged is exactly what is still Copilot's judgement rather than yours.
Copilot excludes a table when it can find nothing in it that identifies a person: no identifier-shaped column, no email, no ID. Such a table has nothing to contribute to a user model and no way to attach an event to anyone. If it is wrong about that, one click overrules it.
Footer
The footer tracks progress — n of {total} tables classified — alongside counts of Event, User and unused tables.
Gate
Classify all tables to continue. Every table must be Event, User, or explicitly unused.
A table you classify as Event should have at least one date, datetime or timestamp column, because a signal built on it will ask you to nominate one. If it has none, you will need to come back here and classify it as User instead, or add a timestamp column in your warehouse.