Field Selection & Aliases
Choose the fields that land. Name them for business.
When a new ad channel joins the report, it can offer a hundred fields under technical names like date_start. In a Connector Data Mart, you tick only the fields to store and give each one an alias, a name the business understands. The column in your warehouse keeps its original name. Documentation
Why OWOX
Marketing wants a new ad channel in next week's cross-channel report, and it can offer a hundred fields under technical names like date_start. Store them all, and business users wade through unused columns and ask you what each one means. In a Connector Data Mart, you pick the fields that land and name each one for business.
- The fields the connector needs to tell rows apart stay ticked, however few fields you choose.
- Only the fields you tick are stored in your warehouse; the alias is set on the Data Mart, so the stored column keeps its name.
- Google Sheets headers and Data Studio's field list show the alias, not the technical field name.
- Ask Claude or ChatGPT about spend through OWOX, and it receives each field's alias and description, not just a name like date_start to guess at.
A source returns every field. Your reports need a few.
Store everything a source returns and you keep and query columns nobody uses. Ship them under technical names like date_start and ad_id, and business users guess what a column means or ask you. Either way, the question comes back to the Data Owner.
THE DATA OWNER
Tick the fields, then name them
In the connector setup, pick the data you want, such as ad insights, then tick only the fields to store. The few fields the connector needs to tell rows apart stay ticked. After the first run, give each field a business-friendly alias on the Output Schema tab, where the Data Mart lists its fields.
You decide which columns reach your warehouse.
THE BUSINESS USER
Columns named the way the business talks
Reports carry only the fields the Data Owner imported, under the aliases the Data Owner gave them. In Google Sheets the alias is the column header, Data Studio shows it in the field list, and AI assistants connected to OWOX read it too.
The warehouse keeps the original names. The report shows business ones.
A field list, not a pipeline to maintain — In a hand-built pipeline, the field list and the column names live in code you maintain. Here the Data Owner ticks fields in the setup, the data is stored only in your warehouse, and the alias is set on the Data Mart, so the stored column keeps its name.
For Data Owners
Decide what lands before the first run
Fields are chosen in the connector setup, before anything is written to your warehouse. Aliases come after the first run, once the Data Mart lists the fields it imported.
Worked example: Facebook Ads Ad Account Insights
Facebook Ads Ad Account Insights offers 100 fields. Tick campaign_name, spend, impressions and clicks; the ad ID and the start and end dates stay ticked, because the connector tells rows apart by them. Publish & Run creates a table with just those columns in your warehouse.
The fields the connector needs stay ticked
The connector tells one row from another by a few fields, such as an ID and a date, so those stay ticked however few fields you choose. On some connectors, a setting you chose earlier changes which fields those are.
A field list ready for aliases
After the first run, the Data Mart lists every field with its name, data type and description. Add a business-friendly alias to each one, or let Metadata Autofill draft them for you to review.
For Business Users
Pick from columns that make sense
You see the fields the Data Owner chose to import, under the names the Data Owner gave them, not a raw export.
The alias is the header
In a Google Sheets report, the column header shows the field's alias. If the Data Owner removes the alias, the header goes back to the field name.
Same names in Data Studio
The aliases and descriptions set on the Data Mart are what Data Studio's field list shows, so a dashboard and a spreadsheet built on the same Data Mart use the same column names.
Same names for AI assistants
Claude or ChatGPT connected to OWOX read aliases and descriptions as business meaning, so a field the Data Owner has named is one they are less likely to misread.
Compare plans
Pay as you go
Top up only when you have a decision to make. No subscription loop.
$0.30 / run
Start freeEverything business needs
Only the columns you chose
The connector stores the fields you ticked, so your warehouse holds and queries those columns, not everything the source returns.
Required fields stay ticked
The fields the connector needs to tell rows apart stay ticked, however few fields you pick.
Aliases without renaming storage
The alias is set on the Data Mart. The stored column keeps its field name, and reports show the business one.
Described after the first run
The first run lists every field you imported with its name, data type and description.
Frequently asked questions
What do I need to bring?
A connected warehouse and access to the account you import from, such as an ad account. You pick the data in the connector setup, tick the fields and run it. OWOX keeps none of your data: the rows are stored only in your warehouse. OWOX stores the setup: the field list, the aliases, the credentials and the run history.
Which fields always stay ticked?
The few fields the connector uses to tell one row from another, such as an ID and a date. For Facebook Ads Ad Account Insights they are the ad ID and the start and end dates. They stay ticked so the data loads correctly.
Does an alias rename the column in my warehouse?
No. The table in your warehouse keeps the connector's field names. The alias is set on the Data Mart and is what reports show.
Where do business users see the alias?
As the column header in a Google Sheets report and in Data Studio's field list. AI assistants connected to OWOX read aliases and descriptions too.
Do I need to write code?
No. You tick fields in the connector setup and type an alias next to each field on the Data Mart. In your own import script, the field list and the column names live in code you maintain. Here OWOX maintains its built-in connectors, and the stored column keeps its name.
Can one Data Mart import several kinds of data from a source?
No. Each Data Mart imports one kind of data, such as Facebook Ads ad insights or ad creatives, with its own field list and its own table. Create another Data Mart for each.
Every claim has a receipt.
Real things real customers said — each quote pinned to a specific claim, straight from the quotes database.
“AI, by the nature of the models, will hallucinate. And because of that, you need something which will create guardrails to ensure that there are no hallucinations, that you can trust your data.”
“We had six or seven different channels and no single source of truth — it was almost impossible, a lot of guesswork.”
“We regained time. And time is the one resource that never comes back.”
- 0.36.0Hiding a calculated metric no longer fails the save on a Data Mart with a joined formula
- 0.36.0Long field descriptions wrap in the Output Schema
- 0.35.0A hidden column no longer reads as a broken schema
- 0.34.0Configure disconnected joined fields
- 0.30.0Output schema edits no longer get silently reverted
Import only the fields your reports use
Create a Connector Data Mart, tick the fields, publish and run, then add aliases on the Data Mart.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.

