I wonder if this makes BI companies freak out a little bit -- because pushing this data into redshift and adding a visualization layer on top takes care of most smaller scale BI needs...
The BI space is absurd. BI viz is the photo apps of the b2b world. Everyone and their grandma thinks they can make one. Lots of VC money gonna get burned.
Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
11–20 of 39 posts
Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#12ETL-as-a-Service is a great idea, particularly one that is visualization/analytics-tool-agnostic! However, there are so many data sources, and they all require different integrations with their different APIs or export mechanisms. A service isn't really useful unless it can import the lion's share of services that a given company uses...
Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#13Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#14ETL-as-a-Service is a great idea, particularly one that is visualization/analytics-tool-agnostic! However, there are so many data sources, and they all require different integrations with their different APIs or export mechanisms. A service isn't really useful unless it can import the lion's share of services that a given company uses...
Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#15I wonder if this makes BI companies freak out a little bit -- because pushing this data into redshift and adding a visualization layer on top takes care of most smaller scale BI needs...
The T, transformation, is huge in many ways. Think of it this way: the data model is the primary UI for an analyst or any power user. It also dictates query performance.
Adding a visualization layer on top of Salesforce's schema, e.g. is not too helpful, regardless of where that data is living. You can answer trivial questions without too much difficulty, but the difficulty ramps up quickly.
The data access patterns, types of logic necessary, and end-user demands are hugely different between an OLTP and OLAP workload.
There's also potentially huge complexity in conforming dimensions across disparate source systems' data.
Master data management is another huge component that hits a lot of the ETL pipeline.
These concerns are all on top of hooking up the right ends of the hose to one another.
I don't mean to disparage the product or company and hope I don't come across as if I am. I just want to point out that they address only a small component of a large process, which in turn is only a segment of the BI lifecycle.
Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#16Earlier quoted context omitted.
Hey pkrein, I am a Segment fan and startup-scale user of your warehouse service. The warehouse service is super convenient, but its main shortfall for us is that you don't offer historical backfilling of data more than 60 days before the warehouse was enabled. That is the data we need in our warehouse most. There are other ways to load in Salesforce, Zendesk, or Stripe data. It is certainly nice to be able to do that…
Yep, as part of this launch we've revised our pricing. If you commit to an annual plan (even self-service plan) we will load all of your historical data, not just 60 days. Just email friends@segment.com after signing up for the paid annual plan and we'll make it happen on the next sync.
Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#17Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#18I wonder if this makes BI companies freak out a little bit -- because pushing this data into redshift and adding a visualization layer on top takes care of most smaller scale BI needs...
Actually, we don't have any interest in being a visualization tool, and are super focused on building customer data infrastructure of the future. This product release is in close partnership with our BI partners (Looker, Mode, Wagon, Periscope, BIME and Chartio). One of the biggest problems our mutual customers face is getting data into their warehouse so that they can use the BI tool in the first place. This launch…
So, instead of Total Company Sales this Month, I want Bob's Sales, Joe's Sales, etc. It feels like this is just a filter on top of what you already have. Almost like a parameterized query? (pass in @UserId for a where statement)
I originally thought maybe this is the job for one of your visualization partners but you really need to filter the results before you perform the aggregate.
Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#19Earlier quoted context omitted.
The BI space is absurd. BI viz is the photo apps of the b2b world. Everyone and their grandma thinks they can make one. Lots of VC money gonna get burned.
Agree. But Segment + Looker is a KILLER combo.
Re: Segment Sources – Load Salesforce, Zendesk, Stripe into Redshift and Postgres
#20ETL-as-a-Service is a great idea, particularly one that is visualization/analytics-tool-agnostic! However, there are so many data sources, and they all require different integrations with their different APIs or export mechanisms. A service isn't really useful unless it can import the lion's share of services that a given company uses...