What do you dislike about Integrate.io?
Lack of built-in connectors makes the DE create rest API - check if pagination is available- check if it can handle the API limits - for example, if the API can handle 100 campaign ids for 1 API call. Still, since xplenty doesn't have append array logic, it`s 1 API call per 1 campaign id, so because of this, API limits are very quickly achieved, which is a huge drawback.
Any new version that is in the builtin components - I am the one who always has to notify xplenty, or we won't have an API that is working - happens all the time with FB (some endpoints work only for each latest version, such as creative data- event data etc...).
doesnt have oauth or jwt system to fetch credentials.
bq destination doesnt have partition and or cluster logic which is a huge downside.
cant handle big data.... we built our own etl, elt , reverse etl etc.. data pipe lines using airflow, airbyte, docker, Kubernetes, python , dask, pyspark etc...we manage it all due to lack of confidence in the product and the history or bugs that is always duplicates the data by X amount some times up to 10000X, trying to show that there is a bug falls on deaf ears though the customer service is good since we do get answers quickly just no one comes back to us and wants to say yes we have a bug.
if my api returns 10m records and by bq has (ONLY WHEN THE PACKAGE FAILS) suddenly 10B records- this is a bug no matter how you sugar coat it.
apis that returns csv logic or file logic are just to hard to do in xplenty, until we have that logic even from support , (most of the times it is just to bugged)and until we get an answer - we just write code and done in less than a day - prod grad
also it is not possible to create hourly logic or lower ( even 3 times a day updates) due to very high prices- we use python in such cases.
so no we won't recommend this to big data or pre big data, though for small data and usage - yes it is a great tool. Review collected by and hosted on G2.com.
