# Revenue optimization

Visitors leave when the offer in front of them is not the one they want. Croct reads behavioral
and retail signals while the visitor is still anonymous and puts the right offer, product and
promotion in front of them.

## The problem

Growth strategies need different offers for different people, and a single storefront shows one.
Shoppers cannot find the products they would buy, promotions land on people who would have
converted anyway, and conversion rate sits flat while revenue erodes.

## How Croct solves it

Store events flow into Croct automatically through the commerce [integrations](/integrations),
so profiles reflect what people actually browse, add and buy. Audiences follow from that
behavior, and the storefront adapts per shopper on the server: offers, product selections,
promotions and messaging. A/B tests measure the revenue effect rather than the click.

## Outcomes

Offers that match intent instead of averages, promotions spent where they change a decision, and
a storefront that adapts per shopper without a replatform.

## Features you use

- **[Segmentation](/segmentation).** Audiences written in CQL, an English-like query language, that update the moment a visitor qualifies.
- **[User profiles](/user-profiles).** Real-time profiles built from behavior, available on the first pageview and enriched from your own data.
- **[Personalization](/personalization).** Content decided per visitor on the server, with no flicker.
- **[A/B testing](/ab-testing).** Bayesian tests on unsampled data, so you learn which variation wins rather than which one looked better.
- **[Commerce integrations](/integrations).** Your commerce platform forwards store events
  automatically, with no instrumentation to write.

## Why 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.

## Getting started

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, Astro, Remix, Svelte, Gatsby, JavaScript, PHP, Laravel and Shopify Hydrogen. Most
teams are live the same day, and the forever-free plan needs no credit card.

## Frequently asked questions

### Does it work with my commerce platform?

Croct integrates with the major platforms and tracks store events automatically. See
[integrations](/integrations).

### Does it slow the storefront 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.

### Do I need developers to run this?

Only for the initial setup. After that, audiences, experiences, tests, scheduling and preview
all live in the Croct interface.

### 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. See [pricing](/pricing) for the
full table.