System fields are platform-level fields that Improvado automatically adds to every data table. These fields provide essential metadata for identifying accounts and tracking data freshness.
Available System Fields
| Field | Description |
|---|---|
account_id | Unique identifier of the connected account |
account_name | Display name of the connected account |
__insert_date | Timestamp when the row was inserted into the table |
These fields are guaranteed to be present in all data tables, regardless of the data source or extract template.
Where System Fields Appear
Data Tables API — The Get data table details endpoint (/api/v3/data-tables/{id}) returns the complete table schema, including all system fields.
CSV exports — All CSV files generated via load orders include system fields as columns.
Where System Fields Do NOT Appear
Extract Template metadata — Endpoints like Get extract template details (/api/v3/datasources/{datasource_name}/extract-templates/{template_id}) return only provider fields — the fields that come directly from the data source API.
Recipe metadata — Similarly, recipe endpoints return only the fields defined in the recipe configuration, not system fields.
Why This Design?
The API separates two distinct concepts:
-
Provider fields — Fields that come from the data source (e.g., Facebook, Google Ads). These define the extract template or recipe structure and vary by data source.
-
System fields — Platform-level fields added by Improvado. These are consistent across all data sources and provide account context and data lineage.
Extract template and recipe endpoints describe the data structure from the provider's perspective. The Data Tables API provides the complete schema as it exists in your destination, including both provider fields and system fields.
Guarantees
account_idandaccount_nameare present in every table- These fields can be safely used in queries and integrations without hard-coding assumptions
- Use the Data Tables API to discover the full schema of any table