Fivetran Platform Connector
Fivetran generates and logs several types of data related to your account and destinations:
- Log events related to connections, dashboard user actions, Fivetran API calls, and schema change data.
- Account- and destination-related metadata that includes:
- Role/membership information
- Column lineage (available for Enterprise and Business Critical accounts)
- Granular consumption information
You can use this data for the following purposes:
- Monitoring and troubleshooting of connections
- Tracking your usage
- Conducting audits
The Fivetran Platform Connector delivers your logs and account or destination metadata to a schema in your destination. We automatically add a Fivetran Platform connection to every new destination you create. The schema name we use for these automatically created connections is fivetran_metadata. By default, we configure the connection to sync once a day, but you can set a different sync frequency and change other default settings on the Setup tab of the connection details page.
We automatically add a Fivetran Platform connection to every destination, but it doesn't start syncing logs and metadata until you add a connection to your destination.
If you are an Account Administrator, you can manually add the Fivetran Platform connection on an account level so that it syncs all the metadata and logs for all the destinations in your account to a single destination. If an account-level Fivetran Platform connection is already configured in a destination in your Fivetran account, then we don't add destination-level Fivetran Platform connections to the new destinations you create.
The MAR that Fivetran Platform connections generate is free, though you may incur costs in your destination. Learn more in our pricing documentation.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | CONNECTION, RESOURCE_MEMBERSHIP, ROLE, ROLE_PERMISSION, TEAM, TEAM_MEMBERSHIP, and USER tables | |
| History mode | ||
| Custom data | ||
| Data blocking | ||
| Column hashing | ||
| Re-sync | ||
| Row filtering | ||
| API configurable | API configuration | |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
Supported deployment models
We support the SaaS and Hybrid deployment models for the connector.
You must have an Enterprise or Business Critical plan to use the Hybrid Deployment model.
Setup guide
Follow our step-by-step setup guide to manually set up your Fivetran Platform connection account-wide.
Sync overview
Most of the tables in the Fivetran Platform Connector use incremental sync so that they are updated when there is new or changed data.
For the LOG and CONNECTOR_SDK_LOG tables, new data is appended to the table. To ensure log data integrity, all connection data tables should have data present, complete, and valid following the initial sync of the relevant connection. Where the data exists, we sync the previous 7 days' worth of data prior to the date of the initial sync of the Fivetran Platform connection. This also means that when a full re-sync is triggered for the Fivetran Platform connection, the LOG and CONNECTOR_SDK_LOG tables will have 7 days' worth of historical data .
Schema information
- The
*_SCHEMA,*_TABLE,*_COLUMN,*_LINEAGE, and*_CHANGE_EVENTtables are available only on the Enterprise and Business Critical plans. - The
SOURCE_TABLEtable stores metadata for all tables that have ever been synced to your destination — including both currently enabled and disabled tables. - The
*_CHANGE_EVENTtables contain only creation and modification events. Deletion events are not supported yet.
This schema applies to all Fivetran Platform connections.
If your Fivetran Platform connection was created before May 12, 2025, you may see some additional tables or columns, which have been deprecated:
CONNECTORtable - This table has been deprecated and replaced byCONNECTIONtable.connector_namecolumn in theINCREMENTAL_MARtable - This column has been deprecated and replaced byconnection_name.connector_idcolumn in all applicable metadata tables - This column has been deprecated and replaced byconnection_id.
Using Fivetran Platform Connector with its data models
You can use our Fivetran Platform Connector along with the Fivetran Platform Connector data model, with each of the model tables storing specific type of data.
You can also set up our free, pre-built Quickstart models. We create these models automatically using the logic in the Fivetran Platform dbt Package. They prepare the data from the Fivetran Platform Connector into analysis-ready models that cover spend, connection performance and status, and metadata and data lineage. If you are an advanced dbt user, you can use the package for increased flexibility.
Error logs
These logs contain information about errors that connections encounter. You can track events, such as a failure or an authentication error from the logs.
The following table lists the errors with a SEVERE severity level:
| SEVERITY | EVENT_TYPE | PROPERTY_NAME | VALUE |
|---|---|---|---|
| SEVERE | status | status | FAILURE |
| SEVERE | status | status | FAILURE_WITH_TASK |
| SEVERE | error | type | dynamically obtained from response |
| SEVERE | error | type | open_file |
| SEVERE | error | type | null_primary_key |
| SEVERE | error | type | authentication_error |
| SEVERE | error | type | permission_denied |
Destination queries
You can query the data in your destination using simple SQL queries. For example, to track schema and table changes in your destination, query the LOG table for the following events:
create_schemacreate_tabledrop_tablealter_table
To learn more about the queries you can use, see our Sample Queries page.
To learn more about the tables generated by Fivetran Platform Connector, see our Table Reference page.
Sample query format
SELECT * FROM project_id.schema_name.table_name
In this example,
project_idis your destination's project ID. To find the project ID, on your Fivetran dashboard, go to the Destination section.schema_nameis the destination schema name you chose while configuring your connection. The default isfivetran_log.table_nameis the name of the table you want to query. For example,LOG.