# Location-based experiences

When the offer varies by country, region or city, one page cannot serve everyone. Croct reads
the visitor's location and adapts the offer, the currency and the wording before the page is
sent.

## The problem

Acquisition that varies by geography ends up fighting the website. Messaging that lands in one
market falls flat in another, prices shown in the wrong currency add friction at exactly the
wrong moment, and visitors have to hunt for the offer that applies to them. IP geolocation APIs
help a little, but they resolve in the browser, after the page has already rendered, and every
use of them costs developer time.

## How Croct solves it

Location is part of the visitor's profile from the first request, enriched rather than raw, so
audiences can be written against country, region or city directly. Croct resolves them on the
server, which means the local offer and the local currency are in the first response. Nothing
flickers, and no client-side lookup runs.

## Outcomes

Creditas increased conversion rate by 18% combining personalization with A/B testing on the user
journey.

More generally: offers that match the market, prices in the currency the visitor thinks in, and
a single page that serves every geography instead of one page per country.

## Features you use

- **[Segmentation](/segmentation).** Audiences written in CQL, an English-like query language, that update the moment a visitor qualifies.
- **[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.
- **[Component CMS](/component-cms).** Content typed per component, so marketers change it without touching code.

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

## Frequently asked questions

### How accurate is the location data?

Croct enriches the location rather than exposing a raw IP lookup, and it is available on the
first pageview, before the page renders.

### Can I show local currencies?

Yes. Currency, offer, wording and any other component can vary per audience, decided on the
server.

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