1. Home
  2. Data Integration Tools
  3. Vertify Reviews
  4. User Review of Vertify
Connecting databases - still one of Marketing's biggest challenges
February 28, 2019

Connecting databases - still one of Marketing's biggest challenges

Michael Florin | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with VertifyData

We are using VertifyData to organize the flow of data between Salesforce and Marketo. Specifically entities which are not synced natively. As our Salesforce structure is extremely customized, and we needed a specific representation of these Custom Objects in Marketo we were relying on a third party tool to help us achieve that.
  • Ease of use - I don't want to say that data integration platforms couldn't still be easier to use, but given the complexity of the matter, I think VertifyData is doing a great job of being understandable, consistent and logical.
  • Reliability of service - once you leave the setup phase behind you, the data movement machine runs in the background without any noise or interruption.
  • I think the UI could get a refresher. It looks a little old-school and I sometimes get lost in the navigation.
  • I saw some inconsistencies on the scheduler, most likely caused by time zone differences. One dialogue reflected the user's time zone, the next server's time zone.
  • Can't quantify. VertifyData helped us create workflows we pretty much couldn't live without.
  • TIBCO Cloud Integration (including BusinessWorks and Scribe)
We were using Scribe for similar tasks but with different connectors. And it served us well, so absolutely no hard feelings here. But when it came to creating complex workflows, we instantly understood Vertify's approach better. Data lookup and transformation e.g. are pretty easy in Vertify and ease of use was definitely what we were looking for.
Marketo, Litmus, Integrate
We are moving and have moved tens of millions of records, and in initial load phase we sometimes struggled. Errors were returned from the endpoints, but after we've moved past that phase, we have never experienced any issues. Definitely no measurable impact on the adjacent systems.
Creating a mapping between source and target while also using lookups and transformations is not trivial. And VertifyData solved this reasonably well, at least all users in my organization understood it pretty quickly.
I would recommend it, as VertifyData exactly fit our use case. I can't speak for all use cases and all connectors - naturally - but the ones we are using and have explored so far, work perfectly well. Also, being a person myself that is not fluent in SQL or JSON or API language in general, I was still able to create all workflows our company needed myself. Which I consider a huge benefit.