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