InfluxDB vs. Twilio Segment

InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).

Incentivized

Best suited: - Merging emails coming from: Facebook leads forms, Unbounce or landing pages forms, Google forms, any other kind of lead generation tool and bundling all that information together for a single user "profile". - Passing events generated in multiple applications by the same user (product selected in web, product discarded in cart, etc) and delivering those events into other applications (like a CRM) Less appropriate: - Reading/updating data directly from segment from a frontend application

Incentivized

• Perfect handling telemetry data.
• Low latency, near real time.
• SQL-like language makes it easier to query.

Incentivized

• Multi-platform. Segment has easy integrations in many different web, backend, and app platforms/frameworks. We use the Segment SDK in Android and iOS as well as our node.js backend.
• Segment is fairly affordable for early-stage companies that are trying out different analytics software. The "developer" plan is free and is suitable for most companies with products that have a small user base.
• The UI is great! It is extremely intuitive and easy-to-learn, and this made it take very little time to integrate this software into our analytics and marketing workflows.

Incentivized

• GUI based administrator console

Incentivized

• More and richer sources. For example, MailChimp is a source but the data you get from MailChimp is quite limited. I ended up writing my own scripts to take better advantage of MailChimp's API because Segment's integration was lacking.
• Better examples on how to set up event tracking. Pageview tracking is easy enough, but it would be nice if they had a sample app and corresponding code for it and showed you, via Git commits, how to add various kinds of events.

Incentivized

InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.

Incentivized

We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.

Incentivized

Over the period it took us to set up, we kept going back to their enablement team to help us with the setup, and they were always ready and were very helpful in the entire process. Even with their documentation, they took the time out to help us work through the process. We've never had a message/email unanswered for more than an hour on working days.

Incentivized

To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).

Incentivized

We chose Twilio Segment for the good API integration and node resources, I would use Ontraport again, particularly if I didn't have the requirements for API and development/platform integration. Certainly the set up and management is easy and seamless with both the API and the user interface to use depending on circumstances and requirements.

Incentivized

• Provided us a time series DB.
• With the SQL-like language, it is very easy to learn.
• Empowered us to keep track of our events.

Incentivized

• Segment has enabled us to get a full view of our front end activity, join it to our back-end activity, and get full visibility into our funnels and user activity.
• Segment lets us send events to ad tools with a full audit trail so all the numbers line up.
• Segment also brings data from other sources into our data warehouse, saving our data engineering time from building commodity connectors.