Fivetran Data Movement Platform
FivetranExternal reviews
803 reviews
from
and
External reviews are not included in the AWS star rating for the product.
I wish Census had existed years ago
What do you like best about the product?
Census just works. It's so simple to create a new sync that we're don't need to rely on data engineers to start moving data to the tools used by other teams: Salesforce, Hubspot, Google Sheets...
What do you dislike about the product?
We're missing a sandbox environment, where we can create and test syncs without actually updating the data in the platform. A sandbox mode would be great to isolate environments effectively in our data stack.
What problems is the product solving and how is that benefiting you?
We are able to send data to the tools used by other teams with a very low effort. As a data engineer, in the past, I had to create custom scripts to sync tables in our data warehouse with our CRM, and now it just takes 5 minutes to start sending data to other platforms. We don't need to care about state management, breaking changes in the APIs, maintaining custom scripts...That's saving our team a lot of time.
Great for moving data out of Snowflake
What do you like best about the product?
I like the ease of use in inserting a SQL query and creating a mapping from Snowflake to the destination.
What do you dislike about the product?
I disliked the limit on the number of destination fields. With 3 syncs we had already used 89/100 destination fields
What problems is the product solving and how is that benefiting you?
Sending data from data warehouse to a marketing platform to pinpoint specific campaigns
Robust, fast and debuggable reverse ETL
What do you like best about the product?
It is really good with both: developing fast solutions (for example, sending a batch of data to a destination) and also with building robust, long-lasting models.
They have a dbt integration, API inspector for traceability, sync logs to check what went well and what went wrong, and honestly, an amazingly user-friendly interface!
They have a dbt integration, API inspector for traceability, sync logs to check what went well and what went wrong, and honestly, an amazingly user-friendly interface!
What do you dislike about the product?
Nothing really, they are always a step ahead with the modern data stack
What problems is the product solving and how is that benefiting you?
Sending data to different marketing tools, Mixpanel for analytics, Salesforce, creating audiences on Facebook and Google, etc.
The benefit is to have a healthy data flow across different tools and have 1 source of truth (the datawarehouse)
The benefit is to have a healthy data flow across different tools and have 1 source of truth (the datawarehouse)
Does what it is supposed to
What do you like best about the product?
Easy to setup and good support from census
What do you dislike about the product?
It is quite expensive. Could have better integration with git
What problems is the product solving and how is that benefiting you?
Reverse ETL, syncing data back to other systems
Census Continues to be the BEST Reverse ETL tool to get data where we need it!
What do you like best about the product?
The user interface is simple, yet powerful and as a result - you can move FAST! In the last year, we've been able to replace several engineering-built processes with Census to get Data from BQ to a variety of tools across the business. If your a business that needs to get more complex with DBT and Census Segments, etc, the UX scales very well to support that. The team did a great job and technical and nontechnical team members alike will easily be able to do what they need!
What do you dislike about the product?
Pricing in the last year has come up quite a bit, but it is the best tool on the market - so I guess you have to pay to play. As a business, you'll still save hundreds of thousands a year on not having to hire devs and additional data analysts...
What problems is the product solving and how is that benefiting you?
We've deprecated a backend salesforce driver and completely sync our business critical user data into SF. We also use Census to pipe data into Segment, Zendesk, and soon our accounting tools.
Recommendations to others considering the product:
Do it!
A very easy-to-use interface for your data pipeline needs
What do you like best about the product?
I use the service for putting data into Salseforce. It is very easy to use and provides an excellent messaging service when there are errors in the data transfer. This is very useful for debugging.
What do you dislike about the product?
The per field billing option is not the best for us given we have a low number of rows, however, every company needs a billing model of some kind. Other than this I have no other complaints.
What problems is the product solving and how is that benefiting you?
pumping data into Salesforce. This saves on the task of writing and maintaining this pipeline ourselves. This is from out data warehouse BigQuery. I have no other uses at current.
Like that infomercial rotisserie - you just set it and forget it
What do you like best about the product?
Census takes what the analytics team does out of static dashboards and into tools that the rest of the company uses, allowing us to actually deliver on the promise of being "data driven".
What do you dislike about the product?
At the moment, I just wish there were more destinations.
What problems is the product solving and how is that benefiting you?
We have an internal dataset that tells us very specific info about all of our accounts. We can push that data into Salesforce for example, so when a salesperson reaches out to a prospect they can say "did you know x, y, and z?", and it's hyper-targeted but automated, making for a much more powerful outreach.
Excellent tool for reverse etl
What do you like best about the product?
Is easy to navigate, set connectors, and have new syncs. Also, you can set alerts when a sync fails
What do you dislike about the product?
So far, nothing dislikes me. I think it has a very wide variety of connections
What problems is the product solving and how is that benefiting you?
We have sent back data from our DWH to our tools, allowing us to use cross-data into our tools without the need of going to look it directly in the DWH.
Sync data between all our tools with ease
What do you like best about the product?
- It is very easy to set up a sync pipeline in Census. I can send data to a new tool (Salesforce, Zendesk, GoogleAds) in less than 1 hour and I don't need to worry about it anymore. Before I had to write pipelines in airflow or prefect and check daily if everything was running smoothly.
- Support team is responsive and helpful.
- Support team is responsive and helpful.
What do you dislike about the product?
- Census is improving quickly but some simple features are missing. For example, it is hard to modify a sync once it is created. Very often, the only way to do this is to duplicate manually the existing sync.
- For big initial syncs, Census can be quite credit-consuming on Snowflake.
- For big initial syncs, Census can be quite credit-consuming on Snowflake.
What problems is the product solving and how is that benefiting you?
- Sending data to operational tools such as Salesforce and GoogleAds is quick and reliable.
- Monitoring syncing between different tools is easy.
- Even people with very light coding skills can use it and debug it.
- Monitoring syncing between different tools is easy.
- Even people with very light coding skills can use it and debug it.
Easy to setup, hard to configure
What do you like best about the product?
Decreases engineering time to create a sync from our data warehouse to 3rd party services. Very nice that Census enforces service-specific best practices and handles deduplication of append events. With Census we can empower our non-engineers to handle data syncs that would otherwise be unaccessible to them. The documentation for specific syncs is also fantastic.
What do you dislike about the product?
There is not much in the way of observability into the syncs you create. They often silently reject data and the alerting is very minimal and doesn't cover these cases. Additionally, many connections are still in active development - for example Facebook CAPI. It does not offer custom event properties and we also encountered a bug after our sync was already live. While there is much less engineering work required to set up a sync, there is still work and for a new destination it roughly took the same amount of time as if we built it ourselves.
What problems is the product solving and how is that benefiting you?
We are sending data from BQ to our ad platforms. We're solving the problem of needing to delegate this specific task to our engineering department. In this we were successful. Now we are able to hand off this project to our marketing team, who will be able to reference the syncs we have so far to create new syncs for new ad data that we would like to optimize on.
Recommendations to others considering the product:
Inquire about the specific service that you plan to use Census to integrate to. The more information Census has in their docs on a particular service, the easier your time will be setting up a sync with that service.
showing 551 - 560