Step 4 — Event Mapping

Map Your Event Tables

Every event table's fields need labelling so they make sense to the people who use them. Step 4 is where you review and refine the event tables you classified in Step 1. User tables do not appear here.

No timestamp picker

note

Earlier versions of this step asked you to nominate a timestamp column for every event table. That picker has been removed. The timestamp is now chosen per signal (and per feature) when the event table is actually used — see Manage Signals — not during onboarding.

Because the timestamp is no longer fixed here, you don't need to decide up front which column means "when this happened". If a table has several plausible candidates (created_at, updated_at, shipped_at), that choice is made later, in the context of the signal that consumes the table — and different signals on the same table can legitimately use different columns.

A column can be called anything. Earlier versions of BPP required a column literally named event_date; that requirement is gone, and nothing needs renaming in your warehouse.

tip

A table you classify as Event in Step 1 should still have at least one date, datetime or timestamp column — the signal you build on it will ask you to pick one. If a table has none, classify it as User or mark it unused.

User IDs

Each card lists the table's identifiers as read-only chips — {field} · {ID type} — with the note Locked — defined in Step 2 · User Identifiers.

They are shown for confirmation, not editing: this is your chance to notice that an event table has no way to reach a user before you activate. To change them, go back to Step 2.

Other fields

The rest of the table's columns are listed with their Label, Description and a Visible toggle. The identifier fields are excluded — they are already accounted for above.

• Label and Description are what people see when building audiences and signals. Copilot drafts both; a column called evt_typ_cd is far more useful to a colleague as "Event type".
• Visible is on by default. Hiding a field keeps it in the data but out of the filter lists, which is worth doing for internal keys and columns nobody will ever filter on. It changes nothing about what is stored, and can be changed later in Tables Configuration.

Gate

Review every event table before you can continue. There is no timestamp requirement on this step anymore.

Continue to Step 5 →