Custom Tables
Tables that you have not mapped to a data type yet, and how to map them to events, users, groups or ad data.
Last reviewed September 15, 2026
A custom table is a table in your warehouse that does not have a data type yet. Custom is not a data type. It is a temporary state. Map each custom table to a data type in time.
A custom table does not join people, groups or ad data, and identity, metrics and destinations do not use it.
When a Table Is Custom
- You connected a BigQuery source or uploaded a CSV file, and you did not map the table yet.
- The shape of the table does not match events, users, groups or ad data yet.
- You look at raw warehouse data before you decide how it fits the Data Model.
Map a Custom Table to a Data Type
- Open the source in Data → Integrations → Sources.
- Open the Data tab and click Add object. For a file upload, open the Semantic Mappings tab and click Map a table.
- Select the table.
- In Data type, select Events, User Properties, Group Properties or Ad Data.
- For Group Properties, select the Group type, for example
vendo_productorvendo_company. - Map the source columns to the fields of that data type.
- Click Create mapping.
- Run a sync.
Vendo then uses the table like any other table of that data type. It is part of identity resolution, Data Studio models and destinations.
Choose the Data Type
| If one row of the table is | Select | See |
|---|---|---|
| An action at a point in time | Events | Events |
| A person | User Properties | Users |
| A company, product, deal or other reference record | Group Properties | Groups |
| The ad performance of one day | Ad Data | Ad Data |
Related
Last updated on