# Croct vs. Segment

Segment collects and routes customer data. Croct collects it too, and then acts on it in the
same platform, deciding what each visitor sees and measuring the result. One is a pipe. The
other closes the loop between the data and the page.

## How they compare

| Capability                                    | Segment | Croct |
|:----------------------------------------------|:-------:|:-----:|
| Native content management system              |    No   |  Yes  |
| Server-side personalization and A/B testing   |    No   |  Yes  |
| Content localization                          |    No   |  Yes  |
| Native real-time content personalization      |    No   |  Yes  |
| Native Bayesian A/B testing engine            |    No   |  Yes  |
| Native real-time dashboards and analytics     |    No   |  Yes  |
| Runs without developer or support involvement |    No   |  Yes  |
| First-class developer experience              |    No   |  Yes  |

## Why teams choose Croct

- **Server-side by design.** Content is resolved before the page is sent, so experiences
  arrive personalized with no flicker and no anti-flicker snippet blanking the page.
- **One platform, no extra vendors.** Segmentation, user profiles, experimentation and
  analytics are built in, so there is no separate CDP, feature-flag tool or analytics
  contract to buy and wire together.
- **Built for headless stacks.** Croct sits alongside Storyblok, Sanity, Strapi, Contentful
  or Shopify Hydrogen and makes the content they hold contextual, instead of replacing them.
- **Marketers ship without developers.** After setup, audiences, experiences, A/B tests,
  scheduling and preview all happen in the Croct interface.
- **Bayesian experimentation on unsampled data.** A/B, A/B/n and multivariate tests with
  cross-device consistency for identified users and bot traffic filtered out.

Against Segment specifically, the difference is what happens after the data lands. Croct builds
real-time profiles, resolves audiences at request time and serves the matching content, so there
is no downstream tool to buy and no round trip to wait for.

## Adopting Croct

Croct runs alongside your current stack, and profiles export to your warehouse or to any tool
you already run, so the data keeps flowing where it flows today.

Setup is one command, `npx croct@latest init`, which installs the SDK, wires the provider
and generates TypeScript types for every slot. Official SDKs cover Next.js, React, Vue,
Nuxt, JavaScript, PHP, Laravel, Symfony, Drupal, and Shopify Hydrogen. Most teams are live
the same day, and the forever-free plan needs no credit card or commitment.

Define slots where content should become dynamic, then move experiences across one at a time.
Existing profile data can be imported, and enriched profiles export to your warehouse or to any
tool you already run.

## Frequently asked questions

### Does Croct replace my CDP?

For personalization and experimentation, yes. Audiences, profiles and real-time processing are
built in, so there is no separate CDP to connect and keep in sync.

### Can I still send data to my warehouse?

Yes. Enriched profiles export to your warehouse or to any tool you already run.

### Does personalization slow the page down?

No. Content resolves on the server before the response is sent, with end-to-end response times
under 90 milliseconds at the 95th percentile.

### What statistics does the A/B testing use?

Bayesian, computed on unsampled data, with A/B, A/B/n and multivariate tests, cross-device
consistency for identified users, and bot traffic filtered out.

### How long does it take to get running?

One command to install, and most teams are live the same day. Marketers run experiments
afterwards without further development work.

### What does it cost?

The forever-free plan covers 10,000 monthly active users with 3 content slots and 1
experience or experiment, and needs no credit card. Growth starts at $100 per month billed
annually for 20,000 monthly active users. Scale is custom.