In our documentation.
Talk to your product specialist or submit a support ticket indicating the source you need and your request will get routed to the correct person. The more requests we get for a source, the higher we prioritize building the new connectors.
See a list of supported warehouses here.
As fast as every five minutes.
Yes, you can adjust the load time to run as frequent as every five minutes and as infrequent as every 24 hours.
While frequent data loads will give you more up-to-date data, there are a few reasons you wouldn’t want to load your data every five minutes, including:
- Higher API usage may cause you to hit a limit that could impact other systems that rely on that API. - Higher cost of loading data into your warehouse. - More frequent delays, resulting in increased delay notification emails. For instance, if the data source generally takes several hours to update but you choose five-minute increments, you may receive a delay notification every sync. We generally recommend setting the incremental loads to every hour to help limit API calls.
No. Support can provide an update in progress upon request, but it will not include an estimated time of completion.
If you just set up your trial, it could take anywhere from a couple of hours to a couple of days to complete the historical sync depending on the size of your data source. If it has been several days, please submit a support ticket and we will look into it.
Most ad sources complete a historical sync in less than a day. However, the amount of data in the source and API rate limits may cause this to vary.
Our pipelines are configured to handle new fields or tables added to your source gracefully, so you don’t need to make manual adjustments in the UI. We constantly monitor and stay ahead of API changes or deprecations so you don’t need to think about it.
No, the Fivetran team will update the connector. Fivetran is fully managed, including managing your destination schema in addition to staying ahead of API changes for all connectors. This is one of our core philosophies.
Yes, Fivetran can currently schedule SQL-based transformations to run in your destination on either a regular configured schedule or when new data loads. We also support integration with dbt (data build tool) to run your models.
We take security very seriously. Learn more here.
In Google Cloud Services in the EU or on AWS in the US depending on setup. You can view our architecture here.
In rest and in transit. Learn more here.
Yes, you can block both specific tables and specific columns. This is especially helpful for sensitive information such as personally identifiable information (PII).
Yes. Learn more here.
Fivetran can only access your data with your approval.
No, all data is removed within 24 hours. Learn more here.
Yes. At Fivetran we take data privacy seriously. Read more here.
Yes, you can connect your logging system to Fivetran. Learn more here.
Find details on Fivetran audit tables here.
For customers that run a lot of campaigns, we’ve seen syncs take more than 24 hours for AdWords and Facebook. In order to make the process faster, we only sync the most recent two years of data automatically. If you would like to see more history, submit a support ticket. Do remember, however, that these bigger historical syncs can take days and incremental updates will be paused in the interim.
Fivetran pricing is volume based. You will be charged based on what you use, defined as the number of monthly active rows (MAR). The number of MAR is variable based on the data sources you connect and your specific business. Please contact us to receive help with a quote or use this blog resource to determine the cost yourself.
Submit a support ticket here.
It is defined as the number of distinct primary keys synced via the Fivetran plan calculated on a per-account basis. We only count rows once per Billing Period, even if they sync multiple times.
Usage of Fivetran is charged on the basis of credits, which are converted to monthly active rows as determined by the Service Consumption Table.