Yeah....We need to have a conversation and push back on them-
IMHO, Segments pricing starts breaking down as company's scale because of a couple factors, that generally allow people to push back.
Some of these reasons (that I know of...and I'm sure you know better), are:
1. Google tag manager is free
2. Many services, like Marketo, don't allow Segment to use their universal javascript widget...so you end up using Segment as a tag manager to push that provider's proprietary widget...reducing the value of Segment. In fact, if you look at the "www." side of our website, we could directly instrument 2 sdk's and remove segment (so net +1 javascript library) and dump segment all together. This would also significantly reduce the unique people count...how they bill!
3. We'll soon have a full-time front engineer focused on the website...So it's not very painful to instrument a new sdk, or add a shared cookie between sdk's.
4. There are options that are really good at moving log files (e.g., fluentd.org) for server side logging. It's how the big boys move log files :)
5. According to google analytics...we're at XX,XXX across webapp + www, so not sure why they are saying YYY,YYY
I realize there's value in Segment, but we can push back on pricing increases.
One last thing, allowing us access to our historic pricing, with no additional functionality, doesn't seem like a big give...especially as pricing usually reduces as you scale. So I am very skeptical of this "new pricing" line of reasoning they are trying to pull!
Comments
This is an email I just sent internally:
XXXX,
Yeah....We need to have a conversation and push back on them-
IMHO, Segments pricing starts breaking down as company's scale because of a couple factors, that generally allow people to push back.
Some of these reasons (that I know of...and I'm sure you know better), are:
1. Google tag manager is free
2. Many services, like Marketo, don't allow Segment to use their universal javascript widget...so you end up using Segment as a tag manager to push that provider's proprietary widget...reducing the value of Segment. In fact, if you look at the "www." side of our website, we could directly instrument 2 sdk's and remove segment (so net +1 javascript library) and dump segment all together. This would also significantly reduce the unique people count...how they bill!
3. We'll soon have a full-time front engineer focused on the website...So it's not very painful to instrument a new sdk, or add a shared cookie between sdk's.
4. There are options that are really good at moving log files (e.g., fluentd.org) for server side logging. It's how the big boys move log files :)
5. According to google analytics...we're at XX,XXX across webapp + www, so not sure why they are saying YYY,YYY
I realize there's value in Segment, but we can push back on pricing increases.
One last thing, allowing us access to our historic pricing, with no additional functionality, doesn't seem like a big give...especially as pricing usually reduces as you scale. So I am very skeptical of this "new pricing" line of reasoning they are trying to pull!
Looking forward to talking to them ~N