Segment Reseñas y detalles del producto

lots of sources and destinations available, as well as custom sources and destinations to tailor to own needs if they currently aren't supported. Requires less dev resources than other competitors as far as im aware

Some destinations and source ownership between Segment and their partners can lead to a bit of back and forth (e.g. SDKs, missing features or bugs in functionality) with support teams.

Resolving customer identity and being able to conglomerate all activities a customer experiences in one place with Personas. Easy to set up server-side tracking as well to circumvent ad blockers and create a complete source of truth when it comes to event tracking.

UI is good for setting things up non-technically

There can be a lot of jargon and documentation for what, ultimately, is a simple thing.

Hooking up marketing journeys to customer activities, deduplicating customers, managing permissions, pipelining data

I love Segment SDK with Javascript and Debuger tools

Logs should link with debugger tool if possible

Track customer events with scalability and configurable

A very nice overlook (great interface), ease of set-up, working without problems, quick troubleshooting.

Not all needed sources, blocking of web tracking for some users.

Getting data from multiple sources into multiple destinations especially into the DWH.

User friendly, Interactive, Easy to use.

Sometimes the site take little longer to load.

We use segment for tracking with amplitude. By following users' data, we have good insights into their interests.

- Like the UI - Love the customer support - Amazing Segment Academy

- Few integrations are difficult - Hard to get support for every tool

- It is very easy to capture the events and love the easy way that how it integrates with other sources

Segment makes it easier to unify and take action on events across my tech stack. For example, I use Segment to monitor key events within Product then push those to a transactional email tool (Customer.io) for lifecycle messaging.

Implementation can sometimes take a bit of technical know-how or support from a developer.

Syncing event and lifecycle data across platforms, which is key for effective product marketing.

The number of differnt integrations it offers, the events get to the destinations very fast and it's very reliable. The debugger it's also awesome it helps a lot to know whats going on, you get feedback very fast.

The documentation sometimes it's not very accurate, you are forced to use the debugger also to know what's going on.

We use lots of tools and Segment helps a lot to integrate barely any tool related to events, and also you can change providers without changing a line of code on your app, the only problem is having the integration in segment but it's very probably it exists, continue this way

If you're a developer you will love their integrations. APIs are so intuive and the SDKs are so smooth that integrating it to your solution is a breeze. Oh, and the debugging tools make your life easier than ever.

Speeding up with the product and understanding its inner logic is easy, making sure your data is correctly streaming across all the platforms with the correct format and transformations can become a messa very quickly. Be sure to document well what you're doing so others don't get lost.

Collecting data is not that much complex. Making sure it's hitting all the tools you need in the expected format in a good timely manner, well that's a challenge. This is the one Segment helped solving also. Data consistency, correct formats, scalability are the things accomplishable using the tool.

Segment enables to easily plug and set up any analytics solution as a data destination with one API.

Integration with web reactive frameworks could be made easier.

With Segment, we can use and test as many analytics as we want without changing a single line of code — a huge time saver.

Segment has been fantastic for us to add new destinations for our data, we can trial out different analysis tools, and pick best of breed without having to integrate to each one. It has also freed up development resources because business analysts and other users can set up new destinations without being reliant on the development team.

The downside of the above is that the development team can lose site of where data is going and how it is being used. Great for business analysis, not so great for data management. I'm very happy Segment has introduced the privacy portal to help manage that data, where it is flowing and how it is used.

Having to do everything by manual integration, or developer configuration. Has massively impacted our reporting and analytics data, as well as ensuring as much data as possible is available in all platforms.

It was really easy to install, in a few clicks you can add difference sources of data and setup the destinations. We use it with our own app and also intercom, salesforce, Hubspot, aws, sisense...

With the basic plan, we can't filter on the data we want to send to the destinations. Also there is no historic of what has been sent.

Send data between different tools

Segment allows non-technical users to easily integrate tracking source data with well-known third-party services/products. This removes the dependency from tech/engineering and allows, for example, a marketing department to customize client-side integrations with marketing channels.

Not every third-party source or destination is available. Segment provides generic integrations through Functions, but this requires technical programming knowledge.

Segment helps us integrate our Tracking sample data and other source data to synchronize to our data warehouse easily. From the data warehouse, we can then perform any additional transformations as needed.

The huge catalogue of services, and the ease in connecting them

There are some advanced platforms that are missing

I can connect a new service in less than 5 minutes, and I don't have to change my code

Not provided

Not provided

Not provided

Simplicity of aggregating event data from our Frontend app as well as backend. Also, that you have a genuine Free tier for startups starting out.

Nothing comes to mind actually; the core reason we use it it is performing well on.

First and foremost, aggregating our data from multiple sources of our app to be able to see single conversion funnels on Mixpanel

Segment is really strong in the wide spectrum of sources and destinations. I like the easiness of setting up a new destination. Always everythings goes smoothly.

I would love to see at least some functions from protocols accessible also on the Team plan.

We use Segment for event tracking from our app and for forwarding the events to other applications we use. Most of the time it's really fast and easy to connect new destination.

Segment's Visual Tagger tool. Data Event feed

Visual Tagger is limited with CSS selector.

We are solving event tracking of our data. Additionally, we add properties to our user ids. Thanks to Segment, we don't have to set up ID tracking and can quickly centralize all of our data flows.

My favorite thing about Segment is the single platform to collect, unify, and connect your customer data. I don't have to ask my devs to implement new analytics tools into our product and we no longer have 5 differnet tools in the product pulling data.

The cost can be expensive for an enterprise plan.

Different departments like different tools, now we don't have to pick and choose just one.

By implementing one API, we can be free to use as many downstream tools as we wish. What's more, by standardizing on a single event API our team is forced to think critically about what events are important to be tracked, and an event in one platform means the same thing as an event in another platform. Segment also makes it easy to take the same event stream and archive it off to a data warehouse, such as Redshift or Snowflake, and create a "single source of truth."

Many downstream Segment integrations require special-casing. For example, Google Analytics does not support aliasing anonymous user ids with registered user ids. To learn this, one must read the Segment docs quite carefully

When we were small, we didn't want to burden our 2-person development team with needing to integrate against every downstream marketing and analytics tool we wanted to try. Adding segment let our developers integrate once and let our product, growth, and sales folks experiment with whatever tools they wanted to use. As we've grown, Segment has grown with us. We haven't needed to worry about event volume, or special cases: we can filter events from destinations, or add custom cloud-based logic in Segment [server-less] Functions. On Segment Functions: If you've got a particularly challenging integration challenge—in our case synchronizing Segment events with Hubspot CRM object properties—Segment also has "Segment Functions" available. We've found it quite convenient generate a single Segment event like "User Updated" and use it to trigger a Segment Function which calls back our application API to get more information, and enrich the objects in HubSpot with a single call.