A Salesforce Data Cloud and Segment alternative
Salesforce Data 360, Twilio Segment and Mosaic compared on published pricing, identity matching, consent, where data lives and when to stay put.
If your business already runs on Salesforce, its customer data product (now called Data 360, formerly Data Cloud) is usually the simplest choice, because it is built to feed the Salesforce apps you already pay for. If your engineers collect event data from websites and apps and need to send it to hundreds of tools, Twilio Segment is built for that job. Look at something else when your customer data sits in a handful of business systems (membership, point of sale, bookings, email), you want the joined-up profiles in a database you own, and the people asking questions are marketers, not analysts. Whichever way you lean, price it on your own profile and user counts, and test identity matching on your own messy records before you sign.
What the vendors publish
Everything here is from each vendor's own page as of November 2026. Prices are as shown with a $ sign.
| | Salesforce Data 360 | Twilio Segment | |---|---|---| | Name on the pricing page | Data 360 | Customer Data Platform (segment.com/pricing redirects to Twilio) | | Published prices | Flex Credits $500 per 100k credits. Profiles $240 per 1,000 profiles a year. Enterprise Profiles $420 per 1,000 profiles a year | None shown. "Contact us for plan and add-on pricing" | | Billing unit | Credits used, or profiles a year | Monthly tracked users, custom volume | | Plans | Flex Credits, Profiles, Enterprise Profiles | Customer Data Pipeline (Connections) and Customer Data Platform (Connections, Unify, Engage) | | What is free | Ingestion, including batch and zero copy. Salesforce customers can provision Data 360 with limited storage and credits | A free trial, no card required. Length and limits not stated on the page | | Included limits | Profiles: 25 calculated insights, 25 transforms, 100 segments. Enterprise Profiles: 100, 100 and 500 | Seats unlimited. Throughput custom |
On Salesforce's Flex Credits plan, most actions are "tied to usage", including unifying records, building and activating segments, and querying. Ingestion is the exception. So the bill depends on how often you rebuild segments and run queries, as well as how many people you hold. Ask for a usage estimate based on your own schedule.
Segment's page lists "550+ destinations" in one place and "700+" in others. Salesforce's Data 360 page cites "200+ Connectors" and zero copy links to Snowflake and Databricks. Count only the connectors you need, and check each one is on the plan you are quoted.
How each one decides two records are the same person
This is where most customer data projects go wrong, so read the docs before the brochure.
Segment. Identity resolution uses cookie IDs, device IDs, emails and your own external IDs, and needs a Business tier account. Its settings give each identifier a limit (by default, one user_id and five of everything else per profile) and a priority (user_id first, then email). When a merge would break a limit, the lower-priority identifier is dropped and the match is retried. It also suggests blocking junk values such as null, -1 and anonymous. Segment warns that tightening limits later can affect existing profiles, so set them before you send data.
Salesforce Data 360. The product page says it can "automatically match and resolve customer identities" across devices, channels and anonymous sessions. We could not open Salesforce's help article on match rules for this post, so ask your account team to show the match and reconciliation rules on your data.
Mosaic. Match rules are written in plain words and run in a priority order you set, such as exact email, then exact mobile, then customer ID, then a fuzzy match on name, birth date and city. Records it cannot match with confidence wait in a review list for a person.
Whatever you choose, run this test: export 500 real records from three systems, including known duplicates and known different people with the same name. Count wrong merges and missed merges. A wrong merge is worse, because one person's consent and history now belong to someone else.
Consent
Segment's Consent Management is on Business tier plans. It stores consent as categories such as advertising and personalisation, and routes events only to destinations in categories the person agreed to. Segment advises against using it for email and SMS opt-ins, and suggests custom profile traits for those instead. That is a sensible split, but it means channel opt-ins are something you model yourself.
The Salesforce pricing page does not mention consent. Ask how opt-outs from each channel reach Data 360 and how quickly.
Mosaic stores consent per person and per channel (email, SMS, push, mail) and removes anyone without consent for that channel when a campaign audience is built, showing how many were removed.
This is general information, not legal advice. Rules differ by country, so check your own.
Where the data lives
- Salesforce. Zero copy lets Data 360 work with data held in Snowflake and Databricks "with no duplication", per its product page. Ask where profiles and segments themselves are stored.
- Segment. The pricing page lists Regional Segment (EU or US) without detail. Ask which data is stored where.
- Mosaic. Runs in your own cloud account or on your own servers, with profiles, segments and consent in a database you own.
A rough cost check
A made-up example, not a real customer. Ana runs marketing for a group of cafés in Lisbon and Porto with 40,000 customer profiles.
- Data 360 Profiles: 40 x $240 = $9,600 a year at the list rate. Enterprise Profiles: 40 x $420 = $16,800. Querying and streaming beyond what the plan includes is extra, by usage.
- Segment: no list price. She needs a quote on her monthly tracked users.
- Mosaic: quoted after a call, based on the systems to connect.
Then add the cost no vendor quotes: someone to map fields, fix source data and own match rules. On every option, that is the larger bill in year one.
When each one fits
| Your situation | Likely fit | Why | |---|---|---| | Sales, service and marketing already in Salesforce | Data 360 | Built to feed those apps. Ingestion is free on the published plans | | Engineers sending web and app events to many tools | Segment | Pipeline product, hundreds of destinations, identity limits you can tune | | Data in a few business systems, marketers asking questions, data must stay in your own database | Mosaic | Profiles in your database, plain-English questions, set up with you | | Under a few thousand customers, one main system | None yet | A clean CRM and a spreadsheet of opt-ins may be enough |
Stay with Salesforce or Segment if most of these are true: your team already knows the tool, your problems are bad source data rather than the platform, you depend on a connector only they offer, or you want self-serve setup. Mosaic is set up by a Thinkiyo team, so there is no sign-up-and-go option.
Questions for every sales call
- Show identity resolution on a sample of my data, including two different people with the same name.
- What happens to consent when two records merge and they disagree?
- Which of the connectors I need are on the plan quoted, in writing?
- What counts as billable usage, and can I see last month's usage by action?
- Where are profiles stored, and what leaves that region?
- How do I export every profile, segment and consent record if I leave?
- Who on my side needs to write SQL or code to run this?
Mistakes to avoid
- Buying for the connector count and not checking the three connectors you need.
- Testing matching on clean sample data.
- Treating consent categories for tracking as the same thing as email and SMS opt-ins.
- Forgetting that usage-priced queries and segment rebuilds grow with the team's curiosity.
- Fixing bad data in the combined profile instead of the source system, so it returns on the next sync.
What to measure
Before you switch, record four numbers: duplicate rate in your main system, the share of customers with a known email or mobile, how long it takes to answer a typical marketing question, and how many people a campaign reaches after opt-outs. Three months after launch, check that duplicates fell, wrong merges found by staff are rare and fixed at source, and questions are answered in minutes. If staff still export to spreadsheets, the platform is not being used, whatever it cost.
What runs in Mosaic today
Mosaic today holds one profile per customer built from linked source records, with each source record kept so staff can see where a field came from. Match rules are listed in priority order with exact and fuzzy types, and unmatched records sit in a review list. Staff can ask a set of common questions in plain English (who has lapsed, top customers by value, revenue by venue, counts by tier or location) and get numbers, a chart or table, and a readable version of the query. Segments are built from rules, and the campaign builder removes people without channel consent, plus self-excluded members and, for gaming offers, members flagged at higher gambling-harm risk.
Limits. Questions outside the supported types get suggestions, not an answer. Connecting your live systems and your sending tools is set-up work we scope with you, so ask what is connected for your tools before you plan around it. There is no self-serve trial. Contact us to run the matching test above on your own records.
For more, read how Mosaic works and how to build a single view of every club member.
Common questions
Is Salesforce Data Cloud the same as Data 360?
Salesforce's product page describes Data 360 as formerly Data Cloud, and its pricing page uses the Data 360 name, as of November 2026. Existing Data Services Credit customers are not forced to move to the new Flex Credits or profile pricing, per the same page.
How much does Segment cost?
Twilio does not publish a price on its customer data pricing page as of November 2026. Both plans are priced on monthly tracked users with custom volume, and the page says to contact sales. There is a free trial with no card required.
Do I need a data engineer for a customer data platform?
For Segment, the docs advise setting identity limits and priorities before you send events, which is a technical decision. For any platform, someone must own field mapping and match rules. Mosaic's setup is done with a Thinkiyo team, but you still need a person who knows your source systems.
Which one handles marketing consent best?
Segment's consent feature routes events by category and suggests custom traits for email and SMS opt-ins. The Salesforce pricing page does not cover consent, so ask. Mosaic checks per-channel consent when a campaign audience is built. Test each with a real opt-out and time how long it takes to take effect.
Can I keep the data in my own cloud?
Salesforce says Data 360 can work with data in Snowflake and Databricks without copying it. Ask where unified profiles are stored. Segment lists EU or US regions. Mosaic runs in your own cloud account or on your servers.