[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-index":3},[4],{"id":5,"title":6,"author":7,"body":8,"date":104,"description":105,"extension":106,"meta":107,"navigation":108,"path":109,"seo":110,"stem":111,"__hash__":112},"blog\u002Fblog\u002Fwelcome.md","Welcome to Segments","Segments Team",{"type":9,"value":10,"toc":97},"minimark",[11,16,24,27,30,33,37,44,66,69,73,76,88],[12,13,15],"h2",{"id":14},"why-another-cdp","Why another CDP?",[17,18,19,20],"p",{},"Every product team eventually ends up gluing together half a dozen tools just\nto answer one question: ",[21,22,23],"strong",{},"what did this user do, across every channel, and\nwhen?",[17,25,26],{},"You start with Google Analytics. Then a product analytics tool. Then a\nmarketing automation platform. Then a data warehouse for the \"real\" numbers.\nBy the time you ship a meaningful onboarding email, your data is duplicated\nin five places — and out of sync in at least three of them.",[17,28,29],{},"Customer Data Platforms (CDPs) were supposed to fix this. And to a point, they\nhave. But the incumbents are closed-source, billed per MTU, and assume your\ndata lives in their cloud.",[17,31,32],{},"We think there's a better way.",[12,34,36],{"id":35},"what-segments-is","What Segments is",[17,38,39,40,43],{},"Segments is an ",[21,41,42],{},"open Customer Data Platform",". It does three things well:",[45,46,47,54,60],"ol",{},[48,49,50,53],"li",{},[21,51,52],{},"Collect"," — ingest events from web, mobile and backend services through\na single, Segment-compatible API.",[48,55,56,59],{},[21,57,58],{},"Unify"," — stitch events into a single customer profile using\ndeterministic identity resolution.",[48,61,62,65],{},[21,63,64],{},"Activate"," — pipe segments to email, push, ads, warehouses and webhooks\nin real time.",[17,67,68],{},"Everything runs on technology you can audit: Postgres, Kafka, Redis,\nClickHouse, Centrifugo. You can self-host it, or use our managed cloud.",[12,70,72],{"id":71},"whats-next","What's next",[17,74,75],{},"Over the coming weeks we'll publish deep-dives on:",[77,78,79,82,85],"ul",{},[48,80,81],{},"The architecture behind sub-second event propagation",[48,83,84],{},"How we model identity resolution at scale",[48,86,87],{},"Migrating from Twilio Segment without downtime",[17,89,90,91,96],{},"Stay tuned — and if you'd like to try it,\n",[92,93,95],"a",{"href":94},"\u002Fpricing","create a free account",".",{"title":98,"searchDepth":99,"depth":99,"links":100},"",2,[101,102,103],{"id":14,"depth":99,"text":15},{"id":35,"depth":99,"text":36},{"id":71,"depth":99,"text":72},"2026-05-23","Why we built another Customer Data Platform — and what makes it different.","md",{},true,"\u002Fblog\u002Fwelcome",{"title":6,"description":105},"blog\u002Fwelcome","FeKP9rig8tfmPIVDJunLosfG0j4B5MJRDMNXBNFghSY"]