Well, they claim to be privacy aware and won't let you map < 20 emails to cookie at a time but it's pretty easy to bypass that.
627 karma · joined June 30, 2011
Well, they claim to be privacy aware and won't let you map < 20 emails to cookie at a time but it's pretty easy to bypass that.
We are a tiny company building an open-source alternative to an existing SaaS app and we have received two such letters in the last 6 months. First time I just replied in an email, second time I had the lawyers respond to create a legal trail. I don't think we were at fault in both the cases but it is still not worth it.
Creating the ID graph is a next level problem altogether!!. How do you know a record in Salesforce is the same as the anonymous visitor on your website. Requires joining across at-least 3 (possibly more IDs) - anonymousID, userID email (if the user signs up) and Salesforce record email.
Should the data pipe do this automatically? If not, what API abstraction should be exposed to the user?
All these tools need to be fed data about user behavior - from apps, server backends, other tools etc. It's a messy data connection problem, not just one way from SaaS to warehouse. Mobile App->SaaS; SaaS->SaaS; Warehouse->SaaS; SaaS->Warehouse and so on.
Maybe there is a way to define "bad" practices in OS outside of license. Similar to how monopolistic practices are banned in business because they are unhealthy for the broader ecosystem. Just asking
The cloud providers taking over open-source projects, launching their own forks (with restrictive licenses) etc isn't great for the open-source ecosystem. If you take away the incentives for the developers (respect, fame, etc) to write open-source software, then isn't it kind of doomed in the long run?
If Twilio wants to own the entire developer ecosystem, maybe they will do others like APM first (Datadogs etc)?
https://www.bandwidth.com/twilio-alternative/
For a fun project though so can't comment on uptime etc. However, if they are powering the VOIP infra behind the other providers, should be good I guess?
We are also working on a functionality where we can replay from your warehouse too.
https://segment.com/blog/customer-data-platform/
This is not surprising. The personalized SMS/push notification use cases (for which you need Segment data) are commonly implemented via marketing platforms (like Braze etc) as opposed to directly via Twillio.
I think this was the other way around. Twillio is powering a lot of these new age marketing automation tools. Instead of just being at the infrastructure layer, it wants to go up the stack and own the marketing applications. Sendgrid and now Segment acqusitions are part of the same strategy.
They did the same thing for the contact center (call center) software space. Lot of the cloud contact center companies were using Twillio and now they launched their own contact center product. That has been one of the key drivers in their 3x increase in valuation in the last 1 yr.
https://www.twilio.com/use-cases/contact-center
Segment's partners like Braze etc should be worried.
1) Low # of events per users. For example, if you have a lot of anonymous users who don't do many events and leave. In this case, you may have a lot of MTUs but low number of events. True for a lot of consumer businesses.
2) You have a huge scale (10s to 100s of millions of events per day). In that scenario, we support deploying enterprise RudderStack inside your VPC but still managed by us. In this case, we don't have to incur infra/data-transfer cost (and charge 80% margin) so can be much much cheaper. We have a couple of customers in this model. Some choose this for privacy/security reasons.
In normal scenarios too we can be 50% or more cheaper. Unlike Segment, we don't store any data (which is a major cost) so our COGS are quite lower. We use your warehouse for all the CDP features.
My experience of TD is > 10 yrs and then the multi-node version was substantially more expensive than the single-node version. Also, storage and compute was coupled which meant I had to pay for nodes even if 99% of my data was cold. That's a problem with RedShift too but not for Snowflake.
De-coupling storage and compute was a brilliant move by Snowflake. BigQuery can completely abstracted compute - you don't provision compute and only pay for data scanned. However, it gives you a sense of insecurity around cost - A single bad cron job running a query every sec can blow up your cost (real-life experience). Snowflake provides the best cost/performance tradeoff I have seen.
The legacy players like Teradata and Exadata (from Oracle) really don't scale. Teradata has ~2B in revenue, Exadata is probably in the same range. That's all up for grabs but that's only scratching the surface.
Historically, only transactional data was dumped into the warehouse. Snowflake is selling storage at S3 price (plus you get compression so often ends up cheaper) while they are making money of compute/query. If they can provide all the right query abstractions (SQL, full-text search), in theory all data can be thrown in Snowflake. Yes, tech savy bay area companies can setup their own stack using Presto etc but rest of the world is not like that.
Is it fair to say this is more like the Segment personas's product? We see a bunch of use cases for personas (which we don't have in RudderStack) so can point to you guys.
Congrats again on the launch.
1) generating a simple report (like how many people came to your website and then opened your emails in last 1 yr) used to take for ever. Storing data was costly.
2) You could not generate complicated reports, say combining marketing + product data (e.g. number of people who came through campaign X and did used the product)
3) You were stuck with their not-so-great UI.
4) Analytics is one use case. Segmentation is another. If you want to create a segment of users (e.g. customers using the free tier of your product and have become active in last 7 days) and sync that segment to multiple destinations like email, salesforce etc, there is not a great way to do that from all the marketing systems.
On the other hand, if you can get all the data in your warehouse, you can use the best of breed tools for storage (Snowflake etc), Visualization (Looker/ChartIO/Tableau) and so on.
But you would need a product like Segment, RudderStack (and now Grouparoo) to get the data into the warehouse and sync it from warehouse back to different destinations.
Because we are Segment event structure/API compatible, there is an inherent structure in events. You can pass arbitrary JSON but only inside the properties or traits field of track/identify call. We do automatically create the schemas for those cases.
Congrats on your launch!! Glad to see more projects in this space. Would love to checkout your repo and share ideas etc.
There was no IDE, auto-complete, visual debugger etc. You really had to think before you typed any code. Even fixing compilation error was a pain - you had to note down the line number and the error, go back and open vim, fix the error, exit vim, re-compile and rinse and repeat. Taught me the paradigm of thinking hard about the problem before starting to code and I think that has helped a lot.
This was still better than the punch-card days I have heard but I personally never had the experience.
We @RudderStack also raised a round recently. Glad to see investors putting money in Open-Source projects.
We can target an audience segment, (say men over 35) and show them same advt on all the pages I view. Or we show ads which are relevant for the content I am reading right now - if I am reading travel stories, show me travel ads.
Is the concern that we won't be able to sell all the inventory doing the latter?
Learned a lot at DataDomain as it scaled from a reasonably small team to a large enterprise and eventually got acquired. Financially though, would have fared much better in Google (assuming I had stuck around).