Twilio Segment vs. Visitor Queue

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

We have been using Visitor Queue for a while now. To be honest, we have not seen anything wrong or difficult to use or that can be improved Providing a discount for the startups would be the only thing that we can ask or add Other than that we are pretty satisfied

• 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

• Allows you to have more than one website being tracked
• Makes it easy to integrate with other platforms
• Gives you proper tracking information

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

• The companies identified were a mixture of ISPs and companies
• It did not capture as many companies as other products
• That's about it. Not much more I can add.

Incentivized

we are still early stage and costs are a little bit high and we need to have a bigger team to optimize the outcome

it was pretty straight forward and easy to use with small teams

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

we had no problems in getting support

the training was ok, we knew the basics and we didnt need intensive training.

It was easy to implement and we did not have any issiues

I'm not sure these are "official competitors" (or alternatives) to Segment, but we use them in parallel for different goals. We use Datadog for logging and monitoring and we use Mixpanel to perform data analysis based on the data we gather using Segment (and other sources). I don't think we ever evaluated any other service vs. Segment. I think we got a recommendation on Segment, liked it and decided to use it (and we're happy with it since).

Incentivized

I evaluated Lead Forensics. It's very similar to Visitor Queue but more expensive and I would say the only thing that seems to be a bit better is their dashboard is more comprehensive/visual.

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.

• We did not select the tool.
• It was in the top 3 of solutions we looked at
• Again, we had a unique requirement and it didn't fit

Incentivized