Segment Reviews & Product Details

Honestly, I don't have to think about Segment much beyond the initial instrumentation in our product. It's integration into rich UX experiences like Amplitude and Looker make it a great tool to work with.

The handoff to Amplitude can be a bit wonky at times. Filtering out, or filtering in new events can take a long time.

Without Segment, we'd have to instrument multiple tools in our product. With it's rich integrations, we're able to instrument once, and deliver data where we need it most.

To access events and data from the majority of the services we use to receive reports, Segment offers native connectors. This includes payments, health metric instrumentation etc

Not as such but it sometimes can be cumbersome and difficult to integrate tools

Tracking significant events, integrating with other platforms for product analytics, and providing raw events directly to our Datalake for data availability on looker and amplitude.

Easy to use, computed traits, granular routing of data to the right place

Could be easier to find some of the functions (debugging, etc)

It allows us to route the right data to the right tools in a super easy way.

The ability to one-click install new destinations and have all my data there.

I've seen Segment get blocked by ad-blockers / cookie-blockers, that's the only downside I can think of.

Having multiple tools and not having to go through a painless implementation process with each.

How easy it is to navigate within the platform itself and to connect data between tools. The Personas feature is particularly useful and the capabilities keep expanding on a consistent basis.

While it saves a lot of time to not integrate with all the tools because Segment does that, it is rather expensive. Support could be a bit more proactive to make sure the implementation is done correctly.

Integrating with different marketing tools without having to worry about moving data and syncing it to all the martech stack tools we have.

- Works very well as a "data hub" to ingest data and forward data off to other sources (marketing tools, analytics, data warehouse) - Does a lot of things well out of the box. Data teams can be productive without needing help from engineers - Scales well as your company grows

- With the event debugger, you can only view events in real time. You can't inspect events from the past - Data governance is difficult to manage. The protocols product doesn't really help much. No good solutions for managing data quality in your events - Expensive and has vendor lock-in, hard to change once you've investing in setting up the instrumentation

Makes event instrumentation much easier for product companies. For Saas teams, the account management feature are good, events can be associated with groups and not just individuals

It helps us to streamline the event tracking process (via connections) and manage user segments (audiences) from a central place. Thus, it enables us to create a single source of truth for our customer data.

The connections have predefined limits. Within those limits, you can do a lot of things. However, sometimes it might be helpful to adjust some behavior via the UI in order to make things more useful for company-specific use cases. One example would be the user id that is used to connect to external tools. Most of the time this is fixed. It would be nice to adjust that. Another thing is, that Segment Personas is only available in the business plan. It would be super helpful to have this available in the team plan as well.

- Streamlined even tracking process. Everything is piped through Segment -> we have a single event tracking library we need to use - A single view of the customer that can be defined within Segment personas that can be synced to other downstream destinations. This gives us a common understanding and definition of user segments throughout the company.

Getting data in, routed and out to destinations is super easy while giving the flexibility you need. Also the PID management is great.

Full data reseidency in the EU should be a standard option across all plans. This can eventually be a dealbreaker.

Control over data collection and unification while changing tools. Also great to have a data pipeline for you dev environment.

real data stream, event tester, easy configuration of new sources and destinations

A lot of PII coming in, it would be more helpful to understand why events fail or have issues. I noticed recently that we had 20k events fail last month in my monthly summary. It would have been great to get some automated messages there.

start up mode = moving fast, all the time. Segment is easy to configure and let's us do all of our marketing analytics.

Segment is great for being able to both visualize and control the flow of customer data throughout your various integrations

Support Agents are often unhelpful when reporting feature gaps

We wanted to know the full picture about the customer and centralize their data for use in various integrations

I used Segment for our product, and it is easily the best tool to capture the customer/user data. It is simple, organized, and helpful in integrating with multiple data sources.

I really can't think of any at the moment. I guess more resources differentiating each type of calls could be added to Segment University so anyone using Segment get clarified.

We captured customer data using segment that helps organize them better. Connects to/fro multiple sources.

Easy to read documentation/walkthrough. Robust UI JS library. Full-fledged dashboard to understand customer behavior.

Lack of tutorials. Lack of mentions in leading UI/JS conference.

Understanding customer behavior, and tracking for bugs/errors that slipped into prod.

Segment offers so many plugins and connections with valuable software for many different industry types.

It was not particularly easy to learn, but once you get used to the UI configuration, it becomes second nature.

We are bringing data from multiple sources into one platform with Segment acting as the middleware for this execution.

We can track user traits and behavior on our platform instantly, and we can integrate this data across a variety of cloud-based platforms! We pair this data with information collected from our user-created content database to create a visual landscape of how users are engaging with our platform.

I would love to see Segment's testing tool capture more than just the last few minutes of activity --- it would be great to have a version of the tools that provides a searchable log so that we can review our metrics in more detail.

We use Segment to view events on our platform that we cannot otherwise view from our standard platform tools. We can combine information about our customers across multiple systems and learn more about their needs.

The ability to integrate with all our 3th party softwares

Client side integrations lack some features compared with cloud integrations

Unification of tagging plans through a single point for tracking information

The UX interface is very friendly. Segment is easy to customize depending on your business requirements, and it has a lot of integrations.

There is nothing I could think of right now.

Collection of the data is really easy to do with Segment.

The fact that you can connect data sources & destinations in less than a minute is just plain crazy.

In terms of corporating data quality segment should provide better software then just rule sets & post-functions.

We didn't want to send data to 10 different places while doing the integrations and we wanted to run the events by segment

There are a lot of integrations available with Segment which makes onboarding new softwares easier.

I work w/Segment peripherally so there's not much negative that I've seen. I'm sure the data folks may have a different opinion during setup.

Currently trying to connect our B2B lists with Braze and ensure Segment is passing data back and forth accurately.

Nothing special, I like all features, is a good tool to work

Some integrations with other tools like RTBhouse, tik tok or tabula are missing

Above all the quality of the data and have a good tagging unique plan that works for all tools

Easily send data to multiple connections from a single source.

Difficult to find filters that have been set up so, if a data endpoint isn't receiving, it's hard to debug.

Easily manage data funnels and multiple data processors