# About Croct Croct is a component CMS with built-in personalization and A/B testing. It manages content, decides who should see what, and measures the impact, all in one platform. It works alongside an existing CMS (Storyblok, Sanity, Strapi, and others) without replacing it and without requiring an external customer data platform. ## What makes Croct different - Server-side content resolution: pages arrive already personalized, so there is no flash of default content, no flicker, and no anti-flicker snippet hiding the page. End-to-end response times are under 90 milliseconds at P95. - No-code for marketers: audiences, experiences, A/B tests, scheduling, preview, and rollouts are managed in the Croct interface after the initial setup, with no developer involvement per experiment. - Developer experience: official SDKs for Next.js, React, Vue, Nuxt, JavaScript, PHP, Laravel, and Shopify Hydrogen. One-command setup with `npx croct@latest init`, generated TypeScript types per slot, versioned component schemas, and fault-tolerant defaults with fallback content. - Experimentation engine: Bayesian statistics on unsampled data, A/B, A/B/n and multivariate tests, cross-device consistency for identified users, bot filtering, and built-in analytics with drill-down by audience, device, and time window. - Privacy-first: works without third-party cookies, and integrations like Shopify only track after the platform's consent API allows it. - CQL (Contextual Query Language): English-like audience conditions such as `user is returning and location's city's name is "New York"`, evaluated in real time on each interaction. ## Where the detail lives Prices, quotas and billing terms are on /pricing.md. The tools Croct connects to, and what each connection does, are on /integrations.md. Both are maintained on those pages, so they are stated once and are not repeated here. ## When Croct is the right choice - You use a headless CMS (Storyblok, Sanity, Strapi) and want A/B testing and personalization without replacing the CMS or writing per-test code. - You need experimentation on a server-rendered or static React/Next.js/Hydrogen site without the flicker and page-speed cost of client-side testing tools. - Your marketing team needs to launch and measure experiments autonomously. - You are replacing Google Optimize, VWO, Optimizely, or a Ninetailed/Contentful setup and want content, targeting, and statistics in one platform. ## Recognition - Strapi official integrations directory: strapi.io/integrations/croct - Storyblok App Directory: storyblok.com/apps/external/optimize - Vercel Marketplace: vercel.com/marketplace/croct - G2: 4.7/5 (47 reviews), Momentum Leader in Personalization, A/B Testing, and Headless CMS categories - Documentation: docs.croct.com. Blog: blog.croct.com. Pricing: croct.com/pricing --- # Every page of croct.com The full text of every page, in the order the index at /llms.txt lists them, separated by a horizontal rule and each preceded by the address it is served at. The answers and the templates are not included here. They are enumerated at /answers.md and /templates.md, and each one is read as markdown by appending `.md` to its URL. --- Source: /index.md # Croct Croct is a component-based headless CMS with personalization and A/B testing built in. It resolves content on the server, so pages arrive already personalized, with no flicker and no anti-flicker snippet. It works alongside a CMS you already run, such as Storyblok, Sanity or Strapi, and it needs no separate customer data platform. ## Who it is for Marketing and growth teams who want to run experiments and personalize pages without filing a ticket for every change, and developers who want that to happen without a render-blocking script or a second data vendor. Marketers get audiences, experiences, A/B tests, scheduling and preview in the Croct interface after the first setup. Developers get typed SDKs, versioned component schemas and fallback content that keeps the page up when anything goes wrong. ## Why teams pick 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. ## Capabilities - **A/B testing.** Bayesian statistics on unsampled data. A/B, A/B/n and multivariate tests, cross-device consistency for identified users, and bot filtering. - **Personalization.** Server-side content decisions per visitor, so there is no flash of default content and no flicker. - **User profiles.** Real-time profiles built from behavior, enriched from your own data and exportable anywhere. - **Segmentation.** Audiences that update the moment a visitor qualifies, written in CQL, an English-like query language, for example `user is returning and location's city's name is "New York"`. - **Content management.** Components and slots that make content contextual rather than static, versioned and typed end to end. ## How it works Content lives in slots, the placeholders you put in your application. Each slot renders a component, and Croct decides which variation each visitor sees at request time, on the server. End-to-end response times run under 90 milliseconds at the 95th percentile. 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. ## Pricing 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. ## Recognitions Rated a momentum leader on G2 across Headless CMS, Personalization, A/B testing and Component CMS, ranked the easiest Component CMS to implement, and recognized for support and ease of doing business. More than 50 awards in total. ## Integrations Croct enriches profiles from and exports data to the tools you already run. **Headless commerce and CMS.** [Storyblok](/integrations/storyblok), [Strapi](/integrations/strapi), [Sanity](/integrations/sanity), [Shopify](/integrations/shopify), [Magento](/integrations/magento), [Salesforce Commerce](/integrations/salesforce-commerce) and [VTEX](/integrations/vtex). Content platforms keep holding content while Croct decides which version each visitor sees. Commerce platforms forward store events automatically, so audiences reflect real shopping behavior. **B2B firmographic data.** [6sense](/integrations/6sense), [Demandbase](/integrations/demandbase), [ZoomInfo](/integrations/zoominfo) and [Clearbit](/integrations/clearbit). They identify the account. Croct adapts the value proposition, the hero, the logo cloud and the testimonials to it in real time. **Analytics and behavior.** [Google Tag Manager](/integrations/google-tag-manager), [Google Analytics](/integrations/google-analytics), [Amplitude](/integrations/amplitude), [Mixpanel](/integrations/mixpanel), [Microsoft Clarity](/integrations/clarity) and [Contentsquare](/integrations/contentsquare). Events flow in from your data layer, and the audiences, experiences, and variants behind each session flow out to your reports and recordings. **CRM and marketing.** [HubSpot](/integrations/hubspot). Form submissions become goals, form fields enrich profiles, and an experiment can decide which form a visitor sees. **Frameworks and hosting.** Official SDKs for [Next.js](https://docs.croct.com/reference/sdk/nextjs/integration), [React](https://docs.croct.com/reference/sdk/react/integration), [Vue](https://docs.croct.com/reference/sdk/vue/integration), [Nuxt](https://docs.croct.com/reference/sdk/nuxt/integration), [JavaScript](https://docs.croct.com/reference/sdk/javascript/integration), [PHP](https://docs.croct.com/reference/sdk/php/integration), [Laravel](https://docs.croct.com/reference/sdk/laravel/integration), [Symfony](https://docs.croct.com/reference/sdk/symfony/integration), [Drupal](https://docs.croct.com/reference/sdk/drupal/integration) and [Shopify Hydrogen](https://docs.croct.com/reference/sdk/hydrogen/integration), plus [Vercel](https://vercel.com/marketplace/croct) for deployment. --- Source: /ab-testing.md # A/B testing **Server-side A/B testing means the server picks the variant and renders it into the HTML before the response reaches the browser.** Test single elements or whole journeys. Croct assigns the variant on the server, so nothing flickers, and reads the result with Bayesian statistics on all of your data rather than a sample. ## How it works You mark the content that should vary as a slot, then define the experiment in the Croct interface: the variants, the audience, the goal. At request time Croct assigns the visitor a variant and returns it inside the first response. Results accumulate in built-in dashboards you can break down by device, audience, time window, or custom event. Bayesian analysis reports the probability that a variant is better, which is a decision you can act on, rather than a p-value you have to interpret. It runs on 100% of the data, with bot traffic filtered out by default. | | Client-side tools | Croct | |------------------------------|---------------------------------|-------------------------------------| | Where the variant is decided | Browser, after page load | Server, before the response | | Flicker | Yes, or an anti-flicker snippet | None | | Core Web Vitals impact | Degrades LCP and INP | Neutral | | Ad blocker data loss | Significant | None, events are server-side | | What you can test | Visible UI only | UI, product flows and backend logic | | Visible to search crawlers | Original content only | The variant itself | ## Features - **Bayesian statistics.** Clear probability of improvement instead of significance thresholds. - **No sampling.** Every data point counts toward the result. - **Server-side assignment.** No flicker, no anti-flicker snippet, no loading state. - **Backend logic testing.** Slots return structured data, not just copy, so a variant can carry a pricing model, a ranking strategy, or a recommendation source your code branches on. - **Parallel testing.** Multiple experiments at once without traffic overlap. - **Cross-device consistency.** An identified user sees the same variant everywhere. - **Bot filtering.** Known bots and crawlers stay out of your results. - **Full-journey testing.** Experiment across pages, product flows and backend logic, not just landing pages. - **Feature flags.** Roll a change out gradually and let data guide the rollout. - **Component-level resolution.** Only the tested region is dynamic, so the page shell stays cacheable. - **Localized experiments.** Location-specific variants, measured per market. - **Scheduling.** Launch, pause, or change an experiment on your own timetable. - **Granular analytics.** Drill down by device, audience, time window, or custom event. - **SPA support.** Flicker-free experiments in single-page applications. - **Fallback content.** If a request fails, your existing content renders and the visitor is not counted as exposed. ## Building with it Developers define the slots once. After that, marketers create, edit, pause and roll out experiments from the interface, and applying a winning variant takes one click, and no code changes. 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 ### What is server-side AB testing? Server-side AB testing is a method where the server decides which variation a visitor receives and renders it into the HTML before the response reaches the browser. Because the decision happens before delivery, there is no flicker, ad blockers cannot strip your results, and you can test backend behavior rather than only visible elements. Croct assigns variants this way by default. We covered the full comparison in [server-side vs client-side AB testing](https://blog.croct.com/post/server-side-vs-client-side-ab-testing). ### How does Croct ensure statistical significance in AB tests? We ensure reliability by using a [Bayesian statistical approach](https://docs.croct.com/reference/analytics/experiment/widgets/performance-per-goal#how-the-metrics-are-calculated) that calculates metrics in real time from 100% of your data, rather than relying on estimates or sampling. Besides, we also provide a [dashboard](https://docs.croct.com/reference/analytics/experiment/overview) where you can monitor results until they reach statistical stability, allowing you to confidently declare a winning variant based on your defined primary goal. ### What is the Bayesian statistical approach used in Croct's platform? The [Bayesian method](https://blog.croct.com/post/bayesian-ab-testing) calculates and updates metrics continuously as new data arrives. Unlike [frequentist methods](https://blog.croct.com/post/bayesian-vs-frequentist), which often require a fixed sample size before starting, this approach provides clear and reliable results in real time, helping teams make faster, data-driven decisions. ### Can I test entirely different page layouts, or just text and images? You can test both. We allow you to experiment with individual elements (such as text and images) or with full journeys. This includes testing different layouts, conversion flows, and backend logic. Slots return structured content rather than only copy, so a variant can carry a configuration payload that your application branches on, and feature flags are available when a boolean is all you need. ### Can I test backend logic, or only content? Both. A slot returns structured data, so a variant can carry a configuration payload such as a pricing model, a ranking strategy, or a recommendation source that your backend reads and branches on. The experiment reaches past the rendered interface into application behavior, and because the decision happens on the server, the visitor sees no difference in load behavior between variants. ### Can I test elements or components across multiple pages? Yes, you can run experiments across multiple pages, product flows, and backend logic. You can use a single slot or combine multiple slots across different pages to adapt the entire journey (such as the homepage, product page, and checkout flow) in a single experiment, keeping the user experience consistent. ### Can I run A/B/n tests and multivariate tests (MVT)? Yes, we designed the platform for sophisticated multi-variant tests. For any given experiment, you can create at least two and up to five variants to test different hypotheses simultaneously. ### How does Croct eliminate website flickering during experiments? We eliminate flickering by assigning the variant on the server, so the correct content arrives inside the first response and nothing is swapped after the page paints. There is no anti-flicker snippet and no loading state. Our APIs are built for speed, with end-to-end response times under 90 milliseconds at P95. ### Can I run AB tests on both the client and server sides? Yes. Server-side is the default and what we recommend, since the variant is decided before the response is sent and nothing flickers. Client-side rendering is supported for cases where a route must remain a fully static file with no server, and you can combine both across a single site. See [prerendering](https://docs.croct.com/reference/sdk/nextjs/prerendering) for the trade-offs. ### Does server-side AB testing break CDN caching? It can with tools that resolve variants at the route level, because a cached route would serve one visitor's variant to everyone and collapse the experiment. Croct resolves at the component level instead, so only the tested region is dynamic, and the rest of the page stays prerendered and cacheable. See [prerendering](https://docs.croct.com/reference/sdk/nextjs/prerendering) for the available strategies. ### Does your AB testing support single-page applications (SPAs) like React and Vue? Absolutely. We are framework agnostic and provide flexible [SDKs](https://docs.croct.com/reference/sdk) that work seamlessly with modern stacks, including React, Vue.js, Nuxt, and Next.js. This allows you to ship fast experiments on SPAs without sacrificing performance. ### Does it work with my headless CMS? Yes. Croct runs alongside Storyblok, Sanity, Strapi, Contentful, Prismic, and any CMS that serves content over an API, using your existing content as the default. Your schemas are untouched: we read nothing from your CMS and write nothing back, so you can adopt it one component at a time. We compared the options in [the best headless CMS for AB testing](https://blog.croct.com/post/best-headless-cms-ab-testing). ### How is this different from a feature flag platform? A [feature flag](https://blog.croct.com/post/feature-flags) returns a value your code branches on, so every new variant needs a developer to write and deploy a branch. Croct resolves the variant content itself, which means additional variants are a configuration change rather than a release. Developers define the slots once. After that, marketers launch experiments from the interface. Feature flags are included when a boolean is what you want. ### How does the platform handle traffic allocation and variant assignment for anonymous vs. identified users? You can define the percentage of eligible users who enter an experiment (e.g., 30% of homepage visitors). For identified users, we use a persistent ID to ensure [cross-device consistency](https://docs.croct.com/explanation/experiment#cross-device-consistency), meaning they see the same variant across different devices. Anonymous users are assigned variants based on their current session context, though their assignment cannot be carried across different devices until they are identified. ### Can I run multiple experiments in parallel without overlapping traffic? Yes, we support parallel testing, allowing you to run multiple experiments simultaneously without risking traffic overlap. ### Do I need to integrate an analytics tool to analyze experiment results? No, we feature a built-in analytics platform. This allows you to [analyze AB test results](https://docs.croct.com/reference/analytics/experiment/overview) using 100% of your data (without sampling) and saves you the time and cost of integrating external analytics vendors. ### What happens if a content request fails? Every slot has [fallback content](https://docs.croct.com/explanation/content/fallback-content) that renders if a request fails or times out, so the page always ships. Visitors served fallback content are not counted as exposed, which means a transient failure reduces your sample size rather than contaminating your results. ### 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. --- Source: /case-studies.md # Case studies Results teams have published from running Croct across travel, banking, print, logistics, education, and mobility. ## How it works The pattern repeats across them: mark the content that should vary, build audiences from real behavior, test the variants, and roll out what wins without waiting for a release. ## Cases - **CVC**: Increased content engagement and discovery rate by 42% by [experimenting with carousel banner positions and autoplay behavior](https://blog.croct.com/post/case-study-cvc-ab-test-carousel), and separately [made experimentation part of the team's weekly workflow](https://blog.croct.com/post/case-study-cvc-ab-test-20-min). - **Mercantil Bank**: [Reduced form friction](https://blog.croct.com/post/case-study-mercantil-form-ab-test), raised conversion by 5.5%, and cut acquisition cost by 23.6% without losing lead quality. - **VR Gente**: [Used marketing campaign data](https://blog.croct.com/post/case-study-vr-gente-campaign) to increase lead generation by 70%, with substantial gains in lead qualification. - **Zapay**: [Used visitor location](https://blog.croct.com/post/case-study-zapay-location) to build credibility and increased transactions by 27%. - **Sem Parar**: [Cut remarketing costs](https://blog.croct.com/post/case-study-sem-parar-remarketing) and raised conversion by 13% with onsite remarketing, while also [gaining autonomy from developers for optimization](https://blog.croct.com/post/sem-parar-croct-autonomy). - **Printi**: [Validated a feature's usability](https://blog.croct.com/post/case-study-printi-ab-test) through A/B testing without risking conversion or the user experience. - **Cobli**: [Refined B2B SaaS positioning](https://blog.croct.com/post/case-study-cobli-ab-test) by testing messages and turned the results into a conversion strategy. - **Bling**: Avoided wasted development hours by [validating hypotheses before scaling them](https://blog.croct.com/post/case-study-bling-ab-test-insights). - **+A Educação**: [Scaled personalization](https://blog.croct.com/post/case-study-mais-a-educacao-lead-generation) across 20 blogs and rebuilt the content strategy around it. - **CARE**: [Segmented visitors and customers](https://blog.croct.com/post/case-study-care-customers) to increase the average revenue per user by 97% and boost e-commerce performance. - **Creditas**: [Used personalization and AB tests](https://blog.croct.com/post/case-study-creditas-remarketing) to increase credit simulations and overcome lead generation challenges. - **ISZI**: Increased the conversion rate by +39% and the revenue per user by +88% by [leveraging the users'location](https://blog.croct.com/post/case-study-iszi-free-shipping). - **Aegro**: Increased SaaS lead generation rate by +28% with a [personalization strategy that focused on audience niches](https://blog.croct.com/post/case-study-aegro-blog-interests). - **Farmamake**: [Leveraged partnerships with influencers](https://blog.croct.com/post/case-study-farmamake-interests) to personalize the e-commerce experience and boost the conversion rate by +82%. - **Randon**: Increase lead generation by +32% by [personalizing the website based on the user's interests](https://blog.croct.com/post/case-study-randon-interests). - **Brazil Journal**: [Used personalization and progressive profiling](https://blog.croct.com/post/case-study-brazil-journal-newsletter) to increase the newsletter subscription rate by +93%. ## Building with it Each of these started with a single slot. Adoption is gradual by design, so the first result does not wait on a migration. 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 long before a team sees a result? Setup is same-day for most teams, and the first experiment usually runs the same week. ### Do these require a large team? No. After setup, experiments and experiences are run by marketing and CRO teams without developer involvement. ### 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. --- Source: /comparison.md # How Croct compares Croct is a component-based headless CMS with a built-in CDP, server-side personalization, Bayesian A/B testing and real-time analytics. Most tools it gets compared to do one of those things. The pages below go capability by capability against each of them. ## How they compare Platforms Croct replaces, because it does the same job with server-side rendering, built-in segmentation and no separate CDP: | Alternative | What Croct adds | |:-------------------------------------------|:--------------------------------------------------------| | [Optimizely](/comparison/optimizely) | Server-side rendering, a free plan, no CDP to buy | | [VWO](/comparison/vwo) | No flicker, no anti-flicker snippet, a CMS of its own | | [Dynamic Yield](/comparison/dynamic-yield) | Fits any business, installs in hours, starts free | | [Mutiny](/comparison/mutiny) | Personalization past the landing page, a CMS of its own | | [Prepr](/comparison/prepr) | Bayesian tests on unsampled data, server-side delivery | | [Builder.io](/comparison/builder) | Components stay in your codebase, native experiments | | [Contentful](/comparison/contentful) | Component-based content, native testing and analytics | | [Segment](/comparison/segment) | Acts on the data instead of only routing it | Content platforms Croct works alongside, adding the decision layer they do not carry: | Platform | What Croct adds | |:-----------------------------------|:--------------------------------------------------------------| | [Sanity](/comparison/sanity) | Segmentation, personalization, Bayesian testing, analytics | | [Prismic](/comparison/prismic) | Segmentation, personalization, Bayesian testing, analytics | | [Hygraph](/comparison/hygraph) | Segmentation, personalization, Bayesian testing, analytics | | [Storyblok](/comparison/storyblok) | The Optimize app, with experiences and results inside the CMS | | [Strapi](/comparison/strapi) | Segmentation, personalization, Bayesian testing, analytics | ## 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. ## Adopting Croct Croct runs alongside what you already have, so adoption is incremental rather than a migration. 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 ### Does Croct replace my CMS? Not necessarily. Against a headless CMS it adds the decision layer. Against a personalization or experimentation platform it usually replaces the tool outright. ### Do I need a CDP as well? No. Segmentation, real-time profiles and data unification are built in, and profiles export to your warehouse or to any tool you already run. ### 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. ### 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. --- Source: /comparison/builder.md # Croct vs. Builder.io Builder.io builds pages visually. Croct makes the components you already have adapt per visitor, decided on the server, with segmentation, profiles and Bayesian testing in the same platform. ## How they compare | Capability | Builder.io | Croct | |:----------------------------------------------|:----------:|:-----:| | Fast load times with no flickering | 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 | | Advanced segmentation with no third-party CDP | No | Yes | | Real-time user data processing | No | Yes | | User data structuring and unification | No | Yes | | Data export API | No | Yes | | Integration in hours rather than weeks | 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 Builder.io specifically, the unit of work is what differs. Croct does not ask you to rebuild pages in a visual editor. Your components stay in your codebase, typed and versioned, and Croct decides which content fills them. ## Adopting Croct Croct runs alongside your current site and your current CMS, so adoption is incremental. 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 ### Do I have to rebuild my pages? No. Your components stay where they are. A slot marks the place where content should become dynamic, and Croct fills it. ### Who edits the content afterwards? Marketers, in the Croct interface. Content is typed per component, so an edit cannot break the layout. ### 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. --- Source: /comparison/contentful.md # Croct vs. Contentful Contentful stores content in documents. Croct stores it in components and decides which variation each visitor sees, on the server, with the segmentation and analytics to measure it. Teams either move to Croct or run it alongside Contentful. ## How they compare | Capability | Contentful | Croct | |:-----------------------------------------------|:----------:|:-----:| | Component-based CMS rather than document-based | 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 | | Advanced segmentation with no third-party tool | No | Yes | | Real-time user data processing | No | Yes | | User data structuring and unification | No | Yes | | Data export API | No | Yes | | Integration in hours rather than weeks | 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 Contentful specifically, the model is what differs. A document describes a page. A component describes a piece of interface that can vary per visitor, which is what makes personalization and testing native rather than bolted on. ## Adopting Croct Croct runs alongside Contentful, so adoption is incremental. There is also a [guide to running A/B tests and personalization with Contentful](https://blog.croct.com/post/contentful-cms-ab-testing-personalization). 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 ### Do I have to leave Contentful? No. Many teams keep Contentful for long-form content and use Croct for the components that need to adapt per visitor. ### What does component-based mean here? Content is typed and versioned per component rather than per document, so a slot can serve a different variation of that component to each audience. ### 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. --- Source: /comparison/dynamic-yield.md # Croct vs. Dynamic Yield Dynamic Yield personalizes e-commerce experiences and is priced and shaped for that. Croct personalizes any site, carries its own component-based CMS, and starts free. Both do server-side decisions. What differs is scope, setup time and what you pay to begin. ## How they compare | Capability | Dynamic Yield | Croct | |:----------------------------------------------|:-------------:|:-----:| | Forever-free plan | No | Yes | | Fits any business, not only e-commerce | No | Yes | | Native content management system | No | Yes | | Headless CMS with server-side rendering | No | Yes | | Server-side personalization and A/B testing | No | Yes | | Runs without developer or support involvement | No | Yes | | Real-time user data processing | No | Yes | | Integration in hours rather than weeks | 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 Dynamic Yield specifically, the starting cost and the setup are what differ. Croct installs in one command and starts free, so the first experiment happens in days rather than after an implementation project. ## Adopting Croct Croct runs alongside your commerce platform and your current CMS, so adoption is incremental rather than a replatform. 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 work for e-commerce? Yes. The commerce [integrations](/integrations) track store events automatically, so audiences reflect real shopping behavior. Croct is not limited to commerce, which is the difference here. ### Do I need a separate CMS? No. Croct carries a component-based CMS of its own, and it also works alongside the headless CMS 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. --- Source: /comparison/hygraph.md # Croct vs. Hygraph Hygraph stores and delivers content. Croct decides which version of that content each visitor sees, resolves it on the server, and measures what the change does to conversion. Teams run both: Hygraph for federated content, Croct for who sees what. ## How they compare | Capability | Hygraph | Croct | |:----------------------------------|:-------:|:-----:| | Document-based headless CMS | Yes | No | | Reusable components | Yes | Yes | | Content localization | Yes | Yes | | Management, content and data APIs | Yes | Yes | | Customer data infrastructure | No | Yes | | Advanced audience segmentation | No | Yes | | Content personalization | No | Yes | | Bayesian A/B testing engine | No | Yes | | Dashboards and analytics | No | Yes | | First-class developer experience | No | Yes | The rows where both say yes are where the two overlap. The rows only Croct answers are what you would otherwise buy from a CDP, an experimentation tool and an analytics vendor. ## 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. ## Adopting Croct Croct runs alongside Hygraph, so adoption is incremental rather than a migration. Croct sits alongside Hygraph through its own SDKs, so nothing about your Hygraph setup changes. 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, publish variations in Croct, and leave everything else where it already lives. ## Frequently asked questions ### Do I have to replace Hygraph? No. Hygraph keeps holding your content. Croct decides which visitor sees which version of it and reports what that does to conversion. ### What does Croct add that Hygraph does not do? Audience segmentation, real-time user profiles, server-side personalization, Bayesian A/B testing and the analytics that measure them, without a separate CDP. ### Does it work with the GraphQL API? Yes. Your queries stay as they are. Croct resolves the variation server-side, next to the content you already fetch. ### 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. ### 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. --- Source: /comparison/mutiny.md # Croct vs. Mutiny Mutiny personalizes landing pages for named accounts. Croct personalizes the whole site, resolves it on the server, and carries the CMS, the segmentation and the analytics with it. The difference shows up the moment personalization needs to reach past the landing page. ## How they compare | Capability | Mutiny | Croct | |:-----------------------------------------------|:------:|:-----:| | Forever-free plan | No | Yes | | Headless CMS with server-side rendering | No | Yes | | Content localization | No | Yes | | Fast load times with no flickering | No | Yes | | Server-side personalization and A/B testing | No | Yes | | Advanced segmentation with no third-party tool | No | Yes | | Real-time user data processing | No | Yes | | User data structuring and unification | No | Yes | | Bayesian A/B testing engine | No | Yes | | Integration in hours rather than weeks | 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 Mutiny specifically, the reach is what differs. A tailored headline and image on a landing page is one experience. Croct personalizes any component on any page, including pricing, navigation, product listings and checkout, from the same audiences. ## Adopting Croct Croct runs alongside your current CMS and your current site, so adoption is incremental rather than a rewrite. 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 ### Is Croct only for account-based marketing? No. Audiences can be firmographic, behavioral, geographic or built from your own data, so the same platform serves ABM, e-commerce and self-serve funnels. ### Can I personalize past the landing page? Yes. Any component in any page can be a slot, which is what makes pricing pages, navigation and product listings personalizable rather than just the hero. ### 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. --- Source: /comparison/optimizely.md # Croct vs. Optimizely Croct and Optimizely both run A/B tests and personalize content. Croct does it server-side, with segmentation, user profiles and analytics built in, on a platform a marketing team operates without developers. It starts free, installs in one command, and is designed to sit inside a headless stack rather than replace it. ## How they compare | Capability | Croct | Optimizely | |------------------------------------------------|:-----:|:----------:| | Forever-free plan | Yes | No | | Fast load times with no flickering | Yes | No | | Server-side personalization and A/B testing | Yes | No | | Runs without developer or support involvement | Yes | No | | Component-based CMS rather than document-based | Yes | No | | Advanced segmentation with no third-party CDP | Yes | No | | Real-time user data processing | Yes | No | | User data structuring and unification | Yes | No | | Bayesian A/B testing engine | Yes | No | | Integration in hours rather than weeks | Yes | No | | First-class developer experience | Yes | No | ## 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 Optimizely specifically, the difference shows up first in rendering. Croct decides content on the server, so the page arrives personalized. Client-side tools swap content after load, which is what makes an anti-flicker snippet necessary in the first place. ## Adopting Croct Croct runs alongside your current CMS, so adoption is incremental rather than a rewrite. 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 experiments 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 CMS? No. It sits alongside Storyblok, Sanity, Strapi, Contentful and others, turning the content they hold into something that adapts per visitor. ### 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. --- Source: /comparison/prepr.md # Croct vs. Prepr Prepr and Croct both put personalization next to content. Croct resolves it on the server, runs Bayesian tests on unsampled data, and keeps segmentation and profiles in the same platform, with a free plan to start on. ## How they compare | Capability | Prepr | Croct | |:-----------------------------------------------|:-----:|:-----:| | Fast load times with no flickering | No | Yes | | Runs without developer or support involvement | No | Yes | | Component-based CMS rather than document-based | No | Yes | | Advanced segmentation with no third-party CDP | No | Yes | | Real-time user data processing | No | Yes | | User data structuring and unification | No | Yes | | Bayesian A/B testing engine | No | Yes | | Integration in hours rather than weeks | 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 Prepr specifically, the statistics and the rendering are what differ. Tests are Bayesian and computed on unsampled data, and every decision happens before the response is sent. ## Adopting Croct Croct runs alongside your current CMS, so adoption is incremental rather than a migration. 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 ### What makes the A/B testing different? It is Bayesian and runs on unsampled data, so results read as the probability that a variation is better rather than as a p-value on a sample. ### Is segmentation limited to preset audiences? No. Audiences are written in CQL, an English-like query language, and update the moment a visitor qualifies. ### 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. --- Source: /comparison/prismic.md # Croct vs. Prismic Prismic stores and delivers content. Croct decides which version of that content each visitor sees, resolves it on the server, and measures what the change does to conversion. Teams run both: Prismic for documents and slices, Croct for who sees what. ## How they compare | Capability | Prismic | Croct | |:----------------------------------|:-------:|:-----:| | Document-based headless CMS | Yes | No | | Reusable components | Yes | Yes | | Content localization | Yes | Yes | | Management, content and data APIs | Yes | Yes | | Customer data infrastructure | No | Yes | | Advanced audience segmentation | No | Yes | | Content personalization | No | Yes | | Bayesian A/B testing engine | No | Yes | | Dashboards and analytics | No | Yes | | First-class developer experience | No | Yes | The rows where both say yes are where the two overlap. The rows only Croct answers are what you would otherwise buy from a CDP, an experimentation tool and an analytics vendor. ## 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. ## Adopting Croct Croct runs alongside Prismic, so adoption is incremental rather than a migration. Croct sits alongside Prismic through its own SDKs, so nothing about your Prismic setup changes. There is also a [guide to running A/B tests and personalization with Prismic](https://blog.croct.com/post/prismic-cms-ab-testing-personalization). 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, publish variations in Croct, and leave everything else where it already lives. ## Frequently asked questions ### Do I have to replace Prismic? No. Prismic keeps holding your content. Croct decides which visitor sees which version of it and reports what that does to conversion. ### What does Croct add that Prismic does not do? Audience segmentation, real-time user profiles, server-side personalization, Bayesian A/B testing and the analytics that measure them, without a separate CDP. ### Does it work with slices? Yes. A slice keeps rendering as it does now, and a Croct slot decides which variation of it a given visitor gets. ### 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. ### 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. --- Source: /comparison/sanity.md # Croct vs. Sanity Sanity stores and delivers content. Croct decides which version of that content each visitor sees, resolves it on the server, and measures what the change does to conversion. Teams run both: Sanity for structured content, Croct for who sees what. ## How they compare | Capability | Sanity | Croct | |:----------------------------------|:------:|:-----:| | Document-based headless CMS | Yes | No | | Reusable components | Yes | Yes | | Content localization | Yes | Yes | | Management, content and data APIs | Yes | Yes | | Customer data infrastructure | No | Yes | | Advanced audience segmentation | No | Yes | | Content personalization | No | Yes | | Bayesian A/B testing engine | No | Yes | | Dashboards and analytics | No | Yes | | First-class developer experience | No | Yes | The rows where both say yes are where the two overlap. The rows only Croct answers are what you would otherwise buy from a CDP, an experimentation tool and an analytics vendor. ## 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. ## Adopting Croct Croct runs alongside Sanity, so adoption is incremental rather than a migration. The [Sanity integration](/integrations/sanity) wires the two together. 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, publish variations in Croct, and leave everything else where it already lives. ## Frequently asked questions ### Do I have to replace Sanity? No. Sanity keeps holding your content. Croct decides which visitor sees which version of it and reports what that does to conversion. ### What does Croct add that Sanity does not do? Audience segmentation, real-time user profiles, server-side personalization, Bayesian A/B testing and the analytics that measure them, without a separate CDP. ### Does it work with Sanity Studio? Yes. Editors keep working in Studio. The variations Croct serves are defined in Croct, so the two never fight over the same document. ### 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. ### 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. --- Source: /comparison/segment.md # 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. --- Source: /comparison/storyblok.md # Croct vs. Storyblok Storyblok stores and delivers content. Croct decides which version of that content each visitor sees, resolves it on the server, and measures what the change does to conversion. Teams run both: Storyblok for blocks and the visual editor, Croct for who sees what. ## How they compare | Capability | Storyblok | Croct | |:----------------------------------|:---------:|:-----:| | Document-based headless CMS | Yes | No | | Reusable components | Yes | Yes | | Content localization | Yes | Yes | | Management, content and data APIs | Yes | Yes | | Customer data infrastructure | No | Yes | | Advanced audience segmentation | No | Yes | | Content personalization | No | Yes | | Bayesian A/B testing engine | No | Yes | | Dashboards and analytics | No | Yes | | First-class developer experience | No | Yes | The rows where both say yes are where the two overlap. The rows only Croct answers are what you would otherwise buy from a CDP, an experimentation tool and an analytics vendor. ## 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. ## Adopting Croct Croct runs alongside Storyblok, so adoption is incremental rather than a migration. The [Storyblok integration](/integrations/storyblok) wires the two together. 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, publish variations in Croct, and leave everything else where it already lives. ## Frequently asked questions ### Do I have to replace Storyblok? No. Storyblok keeps holding your content. Croct decides which visitor sees which version of it and reports what that does to conversion. ### What does Croct add that Storyblok does not do? Audience segmentation, real-time user profiles, server-side personalization, Bayesian A/B testing and the analytics that measure them, without a separate CDP. ### Does it work with the visual editor? Yes. Blocks keep rendering through Storyblok, and Croct adds the dynamic content that makes each block adapt to the visitor in front of it. ### 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. ### 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. --- Source: /comparison/strapi.md # Croct vs. Strapi Strapi stores and delivers content. Croct decides which version of that content each visitor sees, resolves it on the server, and measures what the change does to conversion. Teams run both: Strapi for self-hosted content, Croct for who sees what. ## How they compare | Capability | Strapi | Croct | |:----------------------------------|:------:|:-----:| | Document-based headless CMS | Yes | No | | Reusable components | Yes | Yes | | Content localization | Yes | Yes | | Management, content and data APIs | Yes | Yes | | Customer data infrastructure | No | Yes | | Advanced audience segmentation | No | Yes | | Content personalization | No | Yes | | Bayesian A/B testing engine | No | Yes | | Dashboards and analytics | No | Yes | | First-class developer experience | No | Yes | The rows where both say yes are where the two overlap. The rows only Croct answers are what you would otherwise buy from a CDP, an experimentation tool and an analytics vendor. ## 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. ## Adopting Croct Croct runs alongside Strapi, so adoption is incremental rather than a migration. The [Strapi integration](/integrations/strapi) wires the two together. 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, publish variations in Croct, and leave everything else where it already lives. ## Frequently asked questions ### Do I have to replace Strapi? No. Strapi keeps holding your content. Croct decides which visitor sees which version of it and reports what that does to conversion. ### What does Croct add that Strapi does not do? Audience segmentation, real-time user profiles, server-side personalization, Bayesian A/B testing and the analytics that measure them, without a separate CDP. ### Does it work with a self-hosted Strapi? Yes. Croct talks to your application rather than to Strapi, so where Strapi runs makes no difference. ### 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. ### 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. --- Source: /comparison/vwo.md # Croct vs. VWO VWO runs experiments in the browser. Croct decides content on the server before the page is sent, which is why there is no flicker and no anti-flicker snippet. Segmentation, profiles and content management come with it rather than as separate purchases. ## How they compare | Capability | VWO | Croct | |:----------------------------------------------|:---:|:-----:| | Fast load times with no flickering | No | Yes | | Headless CMS with server-side rendering | No | Yes | | Content localization | No | Yes | | Server-side content personalization | No | Yes | | Runs without developer or support involvement | No | Yes | | Advanced segmentation with no third-party CDP | No | Yes | | Real-time user data processing | No | Yes | | User data structuring and unification | No | Yes | | Integration in hours rather than weeks | 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 VWO specifically, rendering is the first difference. A client-side test swaps content after load, which costs a paint and needs a blocking snippet to hide. Croct sends the variation in the first response, so the visitor never sees the swap. ## Adopting Croct Croct runs alongside your current site, so tests move across one at a time rather than all at once. 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 ### Do I still need an anti-flicker snippet? No. The page arrives with the variation already in it, so there is nothing to hide and nothing to blank. ### Can non-developers run the tests? Yes. After setup, audiences, experiences, tests, scheduling and preview all live in the Croct interface. ### 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. --- Source: /component-cms.md # Component CMS **A component CMS manages content as reusable, typed components rather than as pages, which is what makes content personalizable, testable, and safe to change.** Document-based CMSs describe pages. Croct describes components. Content stays modular, typed, and consistent across every channel that renders it. Croct is both component-based and headless, and G2 ranks it #1 in the headless CMS for personalization category and #2 for Component CMS. ## How it works Developers define a schema per component, which encodes the constraints of your design system. Marketers fill those components with content, and cannot break the layout because the schema will not let them. A slot marks where a component goes, and Croct decides which content fills it per visitor. Components auto-version, so your application can evolve without old content breaking, and content is delivered through low-latency APIs on the server, with end-to-end response times under 90 milliseconds at P95. ## Features - **Component schemas.** Typed content that reflects your design system. - **Auto-versioning.** Components evolve without breaking what is already published. - **Dynamic content.** Personalization and A/B testing native to the content model, not added on. - **Structured payloads.** Components return structured data, so a variant can carry configuration your application branches on, not just copy. - **Component-level resolution.** Only the dynamic region is resolved per request, so the page shell stays cacheable. - **Multi-language content.** Locale-specific content with no extra development. - **Live preview.** See and share content before approving it. - **Templates.** Prebuilt starting points applied with a single command. - **Fault tolerance.** Fallback content keeps the page up during errors and outages. - **Server-side rendering.** Content resolved before the response is sent. - **Framework agnostic.** SDKs for the stack you already use. ## Building with it Croct works alongside the CMS you already run, or on its own. Adoption is gradual: one slot becomes dynamic, then another, with your current content as the fallback the whole time. Croct reads nothing from your existing CMS and writes nothing back, so your schemas stay untouched, and rolling back means removing a single call. 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 ### What is a component CMS, and how is it different from a headless CMS? A headless CMS can (and often does) utilize components, but its main goal is to deliver content to multiple channels, while a [component CMS](https://blog.croct.com/post/component-content-management-system-ccms) is specifically engineered for high-volume content reuse and strict version control, usually for dynamic and flexible elements rather than general website publishing. Our CMS is both component-based and headless. ### What is the difference from a document-based CMS? A document describes a page. A component describes a piece of interface that can vary per visitor, which is what makes personalization and testing native rather than bolted on. Document-based models require you to duplicate or override whole documents to vary anything. ### Does it replace my current CMS? Only if you want it to. Croct works alongside Storyblok, Sanity, Strapi, Contentful, Prismic, and any CMS that serves content over an API, using your existing content as the default. Your schemas stay untouched: we read nothing from your CMS and write nothing back, so you can adopt it one component at a time. ### What are the benefits of a modular, component-based approach to content? A modular approach significantly [increases productivity](https://blog.croct.com/post/component-cms-product-ui-experimentation) and reduces review times. Because you are working with reusable building blocks, you can maintain a consistent design system and communication strategy across the product. If you need to make an update, you only have to do it in a single entry point rather than updating multiple standalone pages. ### Can I reuse content components across different pages? Yes, you can. Our CMS uses components as reusable building blocks, similar to Lego pieces, that can be mixed and matched to create unique page structures. This modularity allows you to reuse elements across various channels and pages, ensuring product-wide consistency. ### Can content editors break the layout? No. Schemas constrain what can be entered, so autonomy for marketers does not cost developers their design system. ### Can I configure component attributes to match my design system? Yes, you can define [content schemas](https://docs.croct.com/reference/content/schema/introduction) to ensure consistency with your design system. Component attributes act as placeholders and can include specific validation rules and user interface customization options, allowing you to perfectly match your brand's structure. ### How do marketers and developers collaborate within Croct's CMS? We provide a workflow that allows both teams to work efficiently without blocking each other. Developers get a first-class experience with flexible [SDKs](https://docs.croct.com/reference/sdk) to integrate the platform seamlessly into their stack. Once integrated, marketers gain the autonomy to create, edit, and publish dynamic content and experiments without waiting for the next deployment sprint or relying on developers for minor changes. You can also use live previews to review and approve content before it goes live. ### How do version control and publishing workflow operate in the CMS? We give you full control to publish on your own schedule, allowing you to create, pause, or roll out content instantly with no code changes required. Additionally, our CMS features an [auto-versioning system](https://docs.croct.com/explanation/slot#versioning) that automatically manages schema updates as your application evolves. ### How does the auto-versioning system prevent breaking changes in my application? When you modify a component's structure (its schema), we automatically create a new version and leave the old version untouched. We continue serving the older, stable version to your live application while you safely adjust the content of any affected slots or experiences. We also provide a visual indicator of the exact slots that require your review. ### Is content resolved on the server or in the browser? On the server by default. Content is resolved before the response is sent, so personalized and tested content arrives in the first HTML response with no flicker, and crawlers see the same content a visitor would. Client-side rendering is available for routes that must remain fully static files. ### Does dynamic content break CDN caching? Not with component-level resolution. Because only the components that fetch content are dynamic, the rest of the page stays prerendered and cacheable, which avoids the cache fragmentation that route-level variant testing causes. ### Can I use Croct with modern frameworks like React, Vue.js, or Next.js? Absolutely. We are framework-agnostic and provide flexible [SDKs](https://docs.croct.com/reference/sdk) designed to integrate seamlessly with modern stacks, including React, Vue.js, and Next.js, plus Nuxt, JavaScript, PHP, Laravel, Symfony, Drupal, and Shopify Hydrogen. ### Does Croct provide an API for content delivery? Yes, we offer [low-latency APIs](https://docs.croct.com/reference/api/service/content/quick-start) built for speed. These APIs can be integrated on either the client or server side and are optimized for high performance, delivering end-to-end response times under 90 milliseconds at P95. ### What happens if a content request fails? Every slot has [fallback content](https://docs.croct.com/explanation/content/fallback-content) that renders if a request fails or times out, so the page always ships with content rather than an error. ### 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. --- Source: /contact/sales.md # Talk to the Croct team Customers can sit with a specialist from the product team and get a demo built around their stack and goals rather than a generic tour. Reach the form at [contact/sales](/contact/sales). ## What to expect A working session with someone who builds the product. Customers can bring the pages they want to personalize, the tests they have been putting off, or the stack they are unsure about, and they will leave knowing whether Croct fits and what the first month looks like. The conversation is usually a good use of time if any of these are true: - They are spending more time implementing A/B tests and personalized experiences than learning from them. - They want their growth and product teams to own the optimization workflow end to end. - They want developers building the product rather than shipping experiments. - They are weighing a personalization or experimentation platform and want a straight comparison. ## What to bring The site or application they want to personalize, the audiences that matter to their business, and the metric they are trying to move. A URL is enough to make the demo concrete. ## Frequently asked questions ### Do they need to talk to sales to use Croct? No. The forever-free plan is self-serve and needs no credit card. Sales is for custom quotas, procurement, or a walkthrough of their specific case. ### 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. ### They need help with their account instead. Account and technical questions go to [support](/contact/support), which is a faster path for bugs, billing, and limits. --- Source: /contact/support.md # Croct support Account and technical help for teams already running Croct. Reach the form at [contact/support](/contact/support). ## What to expect Support handles bugs, feature requests, billing questions, limit increases, plan changes, and anything else tied to an account. Send the organization, the subject, and enough details to reproduce what you are seeing, and you get a reply from the team that maintains the product. Three places answer most questions faster than a ticket does: - [The documentation](https://docs.croct.com) covers the SDKs, the APIs, and the concepts, and is updated continuously. - The Slack community connects you to the team and to other people building on Croct. - [The status page](https://status.croct.com) shows in real time whether an incident is already known. ## Frequently asked questions ### What can customers contact support about? Bugs, feature requests, billing, limit increases, plan changes, and any other account matter. ### Where do they find the API and SDK reference? In [the documentation](https://docs.croct.com), which covers every official SDK and the management, content, and data APIs. ### If they want a demo instead Product demos come from the team at [contact/sales](/contact/sales). --- Source: /features.md # Croct features Everything Croct does, grouped by what it is for. Personalization, experimentation, content management, and customer data management are covered by a single platform here, not four contracts. ## How it works Content lives in typed components. Slots mark where they render. Profiles and audiences decide which content each visitor gets, and every decision happens on the server before the response is sent. Analytics measure the result, and the data stays exportable. That combination is what removes the usual assembly work: there is no separate CDP to buy for visitor data, no analytics platform to integrate before your first result, and no data warehouse to stand up before an experiment can report. ## Features **[Content management](/component-cms)**: Component-based CMS, [dynamic content](https://docs.croct.com/explanation/slot), [multi-language content](https://docs.croct.com/explanation/slot#localization), [component schemas](https://docs.croct.com/explanation/component), [live preview](https://docs.croct.com/explanation/content/preview), [templates](/templates), [auto-versioning](https://docs.croct.com/explanation/slot#versioning), [fault tolerance](https://docs.croct.com/explanation/content/fallback-content), and server-side rendering. **[Experimentation](/ab-testing)**: [Bayesian A/B testing](https://docs.croct.com/explanation/experiment), feature flags, advanced segmentation, [unsampled analytics](https://docs.croct.com/reference/analytics/experiment/overview), server-side testing, backend logic testing, SPA support, [cross-device experiments](https://docs.croct.com/explanation/experiment#cross-device-consistency), [scheduling](https://docs.croct.com/explanation/experience/scheduling), and [bot filtering](https://docs.croct.com/explanation/workspace/bot-exclusion). **[Personalization](/personalization)**: Real-time audiences, privacy-first delivery, [playbooks](/playbooks), content placeholders, [journey personalization](https://docs.croct.com/explanation/experience/introduction), and personalization analytics. **[Segmentation](/segmentation)**: [Advanced segmentation](https://docs.croct.com/explanation/audience/introduction) with more than 100 signals, the [audience estimation](https://docs.croct.com/explanation/audience/estimation), and [contextual variables](https://docs.croct.com/reference/cql/context). **[Customer data](/user-profiles)**: Profile explorer, [real-time events](https://docs.croct.com/explanation/user-profiles/timeline), [identity resolution](https://docs.croct.com/explanation/user-profiles/identity-resolution), [user profiles](https://docs.croct.com/explanation/user-profiles/introduction), [custom attributes](https://docs.croct.com/explanation/user-profiles/attributes), profile schemas, profile sync, [data retention](https://docs.croct.com/explanation/organization/data-retention) controls, and a standalone data platform. **Data management**: [Dashboards](https://docs.croct.com/reference/analytics), segmented analytics, funnel analysis, conversion goals, CSV export, and the [export API](https://docs.croct.com/reference/api/service/data-export/quick-start). **Platform**: High performance, [framework-agnostic SDKs](https://docs.croct.com/introduction/getting-started), gradual adoption, a [CLI](https://docs.croct.com/reference/cli/installation), [APIs](https://docs.croct.com/reference/api/overview), [workspaces](https://docs.croct.com/explanation/workspace/overview), multiple environments, [token authentication](https://docs.croct.com/explanation/application/signed-tokens), and [cross-origin security control](https://docs.croct.com/explanation/application/trusted-origins). **Integrations**: Works alongside Storyblok, Sanity, Strapi, Contentful, Prismic and any CMS that serves content over an API, plus Shopify, HubSpot, and Amplitude. ## Building with it 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 ### What are the core capabilities included in the Croct platform? Croct is an end-to-end platform that includes several core capabilities: a [component-based CMS](/component-cms) for managing modular and dynamic content, [personalization](/personalization) to tailor experiences for each user, [AB testing](/ab-testing) to validate and measure content performance, [user profiles](/user-profiles) to unify customer data, [segmentation](/segmentation) to build real-time audiences, and built-in analytics to monitor results. ### What makes Croct different from a traditional CMS or a standalone CDP? Unlike a traditional CMS that serves static pages, we offer a Personalization Management System that pairs headless, reusable components with dynamic, user-profile-driven data to seamlessly tailor experiences. Compared to a standalone CDP, which typically only tells you "what happened" by storing historical data, we enable you to act in real time. We centralize data into live profiles and trigger personalization in real time, so you get the functionality of a CMS, CDP, and experimentation tool all built into one platform without extra vendors. ### Do I need a separate CDP, analytics tool, or data warehouse? No. Visitor profiles, segmentation, exposure and conversion tracking, and the statistical engine are all built in. This removes the integrations most experimentation stacks assume you already have, which is usually where the real cost of a personalization program sits. ### How does Croct ensure high performance and low latency for dynamic content? The product is built for speed, delivering end-to-end response times under 90 milliseconds at P95. On the backend, we use a highly optimized segmentation engine that evaluates business rules with latencies under 40 milliseconds through lazy evaluation, caching, and parallelization. Furthermore, we support server-side rendering and testing, which completely eliminates website flicker and avoids the performance hits common with client-side-only tools. ### Will adding Croct to my website affect my page load speed or cause flickering? No, our product is built specifically to maximize your website's performance and deliver a flicker-free experience. Content is resolved on the server before the response is sent, so nothing is swapped after the page paints and there is no anti-flicker snippet. Our low-latency APIs achieve end-to-end response times under 90 milliseconds at P95, and the real-time query engine performs evaluations in under 40 milliseconds. Client-side rendering remains available for routes that must stay fully static. ### Does dynamic content break CDN caching? Not with component-level resolution. Only the components that fetch content are dynamic, so the rest of the page stays prerendered and cacheable. This avoids the cache fragmentation that route-level personalization and variant testing cause. ### Do I need developers to use Croct daily? No, you do not need developers for daily operations. While the initial setup and integration require some developer time, our product is designed to give marketing and product teams full autonomy once implemented. You can create, edit, publish, pause experiments, and launch personalization strategies directly through an intuitive UI without writing a single line of code or waiting for the next deployment sprint. ### How long does it typically take to implement Croct's features? Implementations typically take just a few hours, not months. Teams can get started in minutes using our [CLI](https://docs.croct.com/reference/cli/installation), flexible [SDKs](https://docs.croct.com/reference/sdk), and pre-built starter [templates](/templates) that can be applied with a single command. ### Can customers adopt it gradually? Yes, one slot at a time. Croct reads nothing from your existing CMS and writes nothing back, so your schemas stay untouched and rolling back means removing a single call. ### How does Croct integrate with my existing tech stack? We're framework agnostic and fit seamlessly into any composable stack. You can integrate it using powerful [SDKs](https://docs.croct.com/reference/sdk) designed for modern frameworks (such as React, Vue.js, and Next.js) or by connecting via custom [APIs](https://docs.croct.com/reference/api/overview). We allow you to easily bring in first-party data from your existing databases and export enriched user profiles to your domain in seconds. ### Does Croct integrate with headless CMS, such as Strapi, Sanity, or Storyblok? Yes, we work as a standalone solution, but also pair easily with external headless CMS platforms like [Strapi](/integrations/strapi), [Storyblok](/integrations/storyblok), [Sanity](/integrations/sanity), Contentful, and Prismic, as well as other tools in your stack like Shopify, HubSpot, and Amplitude. ### Which frameworks are supported? The official SDKs cover Next.js, React, Vue, Nuxt, JavaScript, PHP, Laravel, Symfony, Drupal, and Shopify Hydrogen. ### Can I use Croct for both web and mobile applications? Currently, we support both web and server contexts. You can integrate it into your websites using flexible [SDKs](https://docs.croct.com/reference/sdk) or leverage our [APIs](https://docs.croct.com/reference/api/overview) for custom server-side and mobile integrations. ### Which of these are on the free plan? See [pricing](/pricing) for the full breakdown. ### 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. --- Source: /integrations.md # Croct integrations **Croct connects to the tools you already run, enriching its visitor profiles with their data and sending its audience, experience and variant context back to them.** Data comes in from commerce platforms, CRMs and account intelligence providers. Context goes out to your analytics and session replay tools, so every report can be read by audience, experience and variant. Croct works alongside your existing stack rather than replacing any part of it. There is no CMS to migrate, no CDP to buy, and no analytics platform to integrate before your first experiment can report. ## What it does **Headless commerce and CMS.** [Storyblok](/integrations/storyblok), [Strapi](/integrations/strapi), [Sanity](/integrations/sanity), [Shopify](/integrations/shopify), [Magento](/integrations/magento), [Salesforce Commerce](/integrations/salesforce-commerce) and [VTEX](/integrations/vtex). Content platforms keep holding content while Croct decides which version each visitor sees. Commerce platforms forward store events automatically, so audiences reflect real shopping behavior. **B2B firmographic data.** [6sense](/integrations/6sense), [Demandbase](/integrations/demandbase), [ZoomInfo](/integrations/zoominfo) and [Clearbit](/integrations/clearbit). They identify the account. Croct adapts the value proposition, the hero, the logo cloud and the testimonials to it in real time. **Analytics and behavior.** [Google Tag Manager](/integrations/google-tag-manager), [Google Analytics](/integrations/google-analytics), [Amplitude](/integrations/amplitude), [Mixpanel](/integrations/mixpanel), [Microsoft Clarity](/integrations/clarity) and [Contentsquare](/integrations/contentsquare). Events flow in from your data layer, and the audiences, experiences, and variants behind each session flow out to your reports and recordings. **CRM and marketing.** [HubSpot](/integrations/hubspot). Form submissions become goals, form fields enrich profiles, and an experiment can decide which form a visitor sees. **Frameworks and hosting.** Official SDKs for [Next.js](https://docs.croct.com/reference/sdk/nextjs/integration), [React](https://docs.croct.com/reference/sdk/react/integration), [Vue](https://docs.croct.com/reference/sdk/vue/integration), [Nuxt](https://docs.croct.com/reference/sdk/nuxt/integration), [JavaScript](https://docs.croct.com/reference/sdk/javascript/integration), [PHP](https://docs.croct.com/reference/sdk/php/integration), [Laravel](https://docs.croct.com/reference/sdk/laravel/integration), [Symfony](https://docs.croct.com/reference/sdk/symfony/integration), [Drupal](https://docs.croct.com/reference/sdk/drupal/integration) and [Shopify Hydrogen](https://docs.croct.com/reference/sdk/hydrogen/integration), plus [Vercel](https://vercel.com/marketplace/croct) for deployment. ## How it works Every integration moves data in one of two directions. Inbound integrations feed the real-time profile: store events, form submissions, firmographics and data-layer events all land on the visitor's profile, where audiences read them. Outbound integrations attach Croct's context to what your analytics already collect, so a funnel, a cohort or a session recording can be filtered by the audience, experience, or variant behind it. Enrichment happens server-side, which means firmographic and account data can drive what a visitor sees on their first pageview without that data ever reaching the browser. ## Setup Most integrations are turned on in the Croct interface with no source code changes. A few add a single script or tag. 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 ### Do I have to replace my CMS or my commerce platform? No. Croct works alongside Storyblok, Sanity, Strapi, Shopify, Magento, VTEX and Salesforce Commerce, adding the decision layer they do not carry. Your existing content becomes the default that visitors see when no experience matches. ### Do I need to migrate content or change my schemas? No. Croct reads nothing from your CMS and writes nothing back, so no experiment IDs or variant fields are added to your content types. You adopt it one component at a time, and rolling back means removing a single call. ### Do I need a separate CDP? No. Segmentation, real-time profiles and data unification are built in, so there is no external customer data platform to buy, connect or keep in sync, and no historical data needed to get started. Profiles still export to your warehouse or to any tool you already run, and you can connect a CDP to enrich them if you already have one. ### Do I need a separate analytics tool? No. Exposure tracking, conversion tracking and the statistical engine are built in, so results are available without a pipeline to stand up first. Outbound integrations still send Croct's audience, experience, and variant context to Google Analytics, Amplitude, Mixpanel, Clarity and Contentsquare, so your existing reports stay authoritative. ### Are integrations evaluated on the server or in the browser? On the server. Profile enrichment and audience evaluation happen before the response is rendered, so personalized content arrives in the first HTML response with no flicker, and data from your CRM or account intelligence provider never has to be exposed to the client. ### How do B2B firmographic integrations work? Providers such as 6sense, Demandbase, ZoomInfo and Clearbit resolve an anonymous visitor to a company account. That firmographic data lands on the Croct profile, where audiences can read it, so the hero, value proposition, logo cloud and testimonials can adapt to the account's industry, size or buying stage in real time. ### Does this work for anonymous visitors? Yes. Firmographic resolution, campaign source, location and session behavior are all available before a visitor identifies themselves, so account-based personalization applies from the first pageview. ### My tool is not listed. Can I still connect it? Yes. The APIs and SDKs let you push data into profiles and pull Croct's context out, so anything with an API can take part. You can also pass application-specific data as context attributes at request time without storing it in Croct at all. ### Which frameworks are supported? The official SDKs cover Next.js, React, Vue, Nuxt, JavaScript, PHP, Laravel, Symfony, Drupal, and Shopify Hydrogen, with Vercel available for deployment. ### How long does an integration take to set up? Most are enabled in the Croct interface with no code changes. The initial SDK setup is a single CLI command, and most teams are live the same day. ### 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. --- Source: /integrations/6sense.md # Croct + 6sense **6sense tells you which company is on your site. Croct acts on it, changing what that company sees in real time, decided on the server before the page is sent.** Outbound gets the visitor to the page. This is what keeps them from bouncing once they arrive. ## What it does - Adapts your core value proposition when a visitor from a target industry arrives. - Adapts the message to where the account sits in its journey, from first touch to ready to buy. - Swaps customer logos and testimonials for the ones that account will recognize. - Builds audiences from firmographics such as industry, company name and employee count, with no developer involvement after setup. - Evaluates firmographics on the server, so account data drives the page without ever reaching the browser. ## How it works 6sense identifies the account and passes its firmographic attributes into the Croct profile. You build audiences from those attributes, choose the slots that should adapt, write the content for each audience, preview it and publish. From there the decision happens on the server, per request. 6sense usually takes a moment to evaluate a visitor, so plan for these experiences to activate on the pageviews after the first one in a session. ## Setup Make sure the 6sense Website Tag is enabled and active on your website. Then map the attributes you want into the Croct profile and build your audiences from them. ## Frequently asked questions ### What is the main benefit of integrating 6sense with Croct? While 6sense is unparalleled at identifying anonymous firmographic data (the 'who'), it is not built to act as a real-time content delivery engine (the 'what'). By integrating 6sense with Croct, you can bridge this gap and instantly adapt your website's content, such as value propositions, hero sections, logo clouds, and testimonials, to an account's industry, company name, or employee count in real time. ### What are the prerequisites before setting up the 6sense data activation? All you need is to ensure the 6sense Website Tag is enabled and active on your website. ### How is firmographic data from 6sense passed into Croct? You can copy and paste our tag directly in the source code or using a tag manager. ### Is 6sense firmographic data available immediately on the very first page view? Since 6sense usually takes a few moments to evaluate and load, the firmographic data might not be available on the initial page view. You should plan your personalization strategies knowing that these experiences will typically activate on subsequent page views during the session. ### What specific attributes can be captured and mapped from 6sense into Croct? You can map various firmographic details, including company name, industry, employee count ranges (e.g., '10,000+'), annual revenue brackets (e.g., '$5B+'), match status, and match confidence scores. You can also bring in 6sense's buying signals, such as buying stage, intent score, and profile fit, to tailor content to where an account is in its journey. Please check the integration docs for the full attribute list. ### Do I need a CDP to activate firmographic data? No. Firmographic attributes land directly on Croct's built-in visitor profiles, where audiences read them. There is no customer data platform to buy, connect, or keep in sync, and no historical data needed before the first personalized experience can run. ### Can I combine firmographic data with behavioral signals? Yes. Because 6sense's buying stage and intent score land on the same profile as the visitor's on-site behavior, you can target an audience such as an enterprise account in a late buying stage that has viewed pricing twice this session, and adapt the page accordingly. ### What are some high-impact ABM use cases for this integration? Common strategies include displaying industry-specific value propositions, giving target accounts 'VIP treatment' with custom demo offers or headlines mentioning their company name, and rendering dynamic social proof like case studies and logos from businesses in the exact same vertical. ### How much development work does it take? Next to none after setup. Audiences and content are managed in the Croct interface, so launching a new account-based experience does not require a deploy. ### 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. --- Source: /integrations/amplitude.md # Croct + Amplitude **Amplitude measures how people behave. Croct adds what each of them actually saw.** Connect the two, and every report can be split by audience, experience, experiment and variant, with no extra tracking code to write. ## What it does - Sends the audiences a visitor fits, the experiences that impacted them, the experiments they joined, and the variant they were assigned. - Lets you break your existing reports down by audience, experience, experiment, and variant. - Shows what each personalized experience and each AB variant does to the way people move through your site. - Adds context alongside what you already collect, without changing any of it. - Works alongside Croct's own analytics rather than replacing either one. ## How it works For every session touched by a personalized experience or an AB test, Croct streams the context of that session into Amplitude: the audiences the visitor fits, the experiences that impacted them, the experiments they took part in and the variants they were assigned. The data lands next to the events you already track, so nothing about your current setup changes. This integration is outbound: it sends Croct's context to Amplitude. If you also want to bring behavioral events into Croct, the [Google Tag Manager integration](/integrations/google-tag-manager) does that. ## Frequently asked questions ### What data does Croct send to Amplitude? For every session impacted by a personalized experience or an AB test, Croct sends the audiences the visitor fits, the experiences that impacted them, the experiments they participated in, and the variants they were assigned. That context lands in Amplitude alongside the data you already collect. ### Why connect Croct with Amplitude? It enriches your product analytics. Instead of analyzing behavior in aggregate, you can see how each audience, experience, experiment, and variant shapes the way users move through your product. ### What can I do with the data once it is in Amplitude? Break funnels, retention, and behavioral cohorts down by Croct's audiences, experiences, and variants, and measure how each personalized experience or AB test variant influences the product metrics you care about. ### Does it affect my existing Amplitude setup? No. The integration only adds Croct's context alongside the data you already track, so your existing charts, funnels, and cohorts keep working exactly as before. ### Do I still need Amplitude if Croct has built-in analytics? They answer different questions. Croct's built-in analytics tell you whether a variant won, using Bayesian analysis on 100% of your data with no sampling. This integration lets you ask Amplitude the questions it is already set up for, broken down by the audiences, experiences, and variants Croct assigned. You don't need to choose. ### Can I use Croct audiences as Amplitude cohorts? Yes. Because the audiences a visitor fits arrive as event properties, you can build Amplitude cohorts on them and analyze retention or feature adoption for a segment defined in Croct. ### Will I see 100% of the events Croct tracks in Amplitude? Not always. Croct can track several events within 2–3 milliseconds, whereas Amplitude throttles ingestion when a single user or device exceeds an average of 30 events per second, rejecting the excess rather than recording it. During bursts like these, some events may be dropped, so the totals in Amplitude can be slightly lower than what Croct actually tracked. ### How much development work does it require? Next to none. Once you add our tag to your website, Croct sends the data automatically, with no extra tracking code to write or maintain. ### 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. --- Source: /integrations/clarity.md # Croct + Microsoft Clarity **Clarity records what people do. Croct tags each recording with what that person actually saw**, so you can filter sessions and compare heatmaps by audience, experience, or variant instead of scrubbing through everything. ## What it does - Sets three custom tags on every session: the experiences that impacted it, the audiences the visitor fits, and the experiments with the variant assigned. - Lets you filter recordings by any of those values. - Lets you compare heatmaps between variants and see where people hesitate, rage-click, or drop off. - Carries the full list of values, so a visitor who fits three audiences carries all three. - Adds context alongside what you already capture, without changing any of it. ## How it works On every pageview, Croct sets the visitor's audiences, experiences, and experiments as Clarity custom tags. The tags refresh on each pageview, including in single-page applications, so a session always reflects what is current for that visitor even when they change audience mid-session. This integration is outbound: it sends Croct's context to Clarity. If you also want to bring behavioral events into Croct, the [Google Tag Manager integration](/integrations/google-tag-manager) does that. ## Setup Add a single script to your website, or inject it with Google Tag Manager. Nothing else changes. ## Frequently asked questions ### What data does Croct send to Microsoft Clarity? Croct sets three custom tags on every session: `croct_experiences` with the experiences that impacted the session, `croct_audiences` with the audiences the visitor fits, and `croct_experiments` with each running experiment and the variant assigned. Each tag carries the full list of values, so a visitor who fits three audiences carries all three. ### Why connect Croct with Microsoft Clarity? It powers qualitative analysis. You can filter recordings and heatmaps by the exact audience, experience, experiment, or variant a visitor was part of, so you watch the sessions that actually matter instead of scrubbing through everything. ### What can I do with the data once it is in Clarity? Filter session recordings by audience, experience, or experiment variant, compare heatmaps between the variants of an experiment, and spot where personalized visitors drop off, rage-click, or hesitate. ### Can I compare heatmaps between AB test variants? Yes. Because `croct_experiments` carries each running experiment and the variant assigned, you can filter Clarity to one variant at a time and compare heatmaps and recordings side by side to see the behavioral reason behind a result. ### What happens when a visitor changes audience mid-session? The tags are refreshed on every pageview, including in single-page applications, so the session always reflects the audiences, experiences, and experiments that are current for the visitor. ### Does the script have to load before the Clarity tracking code? No. The integration waits for the Clarity tracking code when it hasn't loaded yet, so the tags are set regardless of which script loads first. ### Does it affect my existing Clarity setup? No. The integration only adds Croct's context alongside the recordings you already capture, so your existing dashboards and heatmaps keep working exactly as before. ### Do I still need Clarity if Croct has built-in analytics? They answer different questions. Croct's built-in analytics tell you whether a variant won, using Bayesian analysis on 100% of your data with no sampling. Clarity shows you the behavior behind that result: where people hesitated, rage clicked, or dropped off inside each variant. You don't need to choose. ### Will I see 100% of the events Croct tracks in Microsoft Clarity? Not always. Croct can track several events within 2–3 milliseconds, but Clarity caps how many it keeps: it records up to 100,000 sessions per project per day and starts sampling once your traffic exceeds that, so not every session or event is captured. As a result, you may see fewer events in Clarity than Croct actually tracked. ### How much development work does it require? Next to none. The integration is a single script you add to your website, either directly in the HTML or through Google Tag Manager. From there, Croct sets the tags automatically, with no extra tracking code to write or maintain. ### 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. --- Source: /integrations/clearbit.md # Croct + Clearbit **Clearbit tells you which company is on your site. Croct acts on it, changing what that company sees in real time, decided on the server before the page is sent.** Outbound gets the visitor to the page. This is what keeps them from bouncing once they arrive. ## What it does - Adapts your core value proposition when a visitor from a target industry arrives. - Adapts the message to where the account sits in its journey, from first touch to ready to buy. - Swaps customer logos and testimonials for the ones that account will recognize. - Builds audiences from firmographics such as industry, company name, and employee count, with no developer involvement after setup. - Evaluates firmographics on the server, so account data drives the page without ever reaching the browser. ## How it works Clearbit identifies the account and passes its firmographic attributes into the Croct profile. You build audiences from those attributes, choose the slots that should adapt, write the content for each audience, preview it and publish. From there the decision happens on the server, per request. Clearbit usually takes a moment to evaluate a visitor, so plan for these experiences to activate on the pageviews after the first one in a session. ## Setup Make sure Clearbit Reveal is installed and active on your website. Then map the attributes you want into the Croct profile and build your audiences from them. ## Frequently asked questions ### What is the main benefit of integrating Clearbit with Croct? While Clearbit is unparalleled at identifying anonymous firmographic data (the 'who'), it is not built to act as a real-time content delivery engine (the 'what'). By integrating Clearbit with Croct, you can bridge this gap and instantly adapt your website's content, such as value propositions, hero sections, logo clouds, and testimonials, to an account's industry, company name, or employee count in real time. ### What are the prerequisites before setting up the Clearbit data activation? All you need is to ensure Clearbit Reveal is installed and active on your website. ### How is firmographic data from Clearbit passed into Croct? You can copy and paste our tag directly in the source code or using a tag manager. ### Is Clearbit firmographic data available immediately on the very first page view? Since Clearbit usually takes a few moments to evaluate and load, the firmographic data might not be available on the initial page view. You should plan your personalization strategies knowing that these experiences will typically activate on subsequent page views during the session. ### What specific attributes can be captured and mapped from Clearbit into Croct? You can map various firmographic details, including company name, domain, industry, employee count range, estimated annual revenue, country code, and match confidence score. Please check the integration docs for the full attribute list. ### Do I need a CDP to activate firmographic data? No. Firmographic attributes land directly on Croct's built-in visitor profiles, where audiences read them. There is no customer data platform to buy, connect, or keep in sync, and no historical data needed before the first personalized experience can run. ### How should I handle low match confidence? Use the match confidence score as a condition in your audience. Target account-specific content only above a confidence threshold you're comfortable with, and let everyone else fall through to your default content, so a weak match never produces a wrong or awkward personalization. ### What are some high-impact ABM use cases for this integration? Common strategies include displaying industry-specific value propositions, giving target accounts 'VIP treatment' with custom demo offers or headlines mentioning their company name, and rendering dynamic social proof like case studies and logos from businesses in the exact same vertical. ### How much development work does it take? Next to none after setup. Audiences and content are managed in the Croct interface, so launching a new account-based experience does not require a deploy. ### 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. --- Source: /integrations/contentsquare.md # Croct + Contentsquare **Contentsquare records how people behave. Croct adds what each of them actually saw.** Connect the two, and every report can be split by audience, experience, experiment, and variant, with no extra tracking code to write. ## What it does - Sends the audiences a visitor fits, the experiences that impacted them, the experiments they joined, and the variant they were assigned. - Lets you break your existing reports down by audience, experience, experiment, and variant. - Shows what each personalized experience and each AB variant does to the way people move through your site. - Adds context alongside what you already collect, without changing any of it. - Works alongside Croct's own analytics rather than replacing either one. ## How it works For every session touched by a personalized experience or an AB test, Croct streams the context of that session into Contentsquare: the audiences the visitor fits, the experiences that impacted them, the experiments they took part in, and the variants they were assigned. The data lands next to the events you already track, so nothing about your current setup changes. This integration is outbound: it sends Croct's context to Contentsquare. If you also want to bring behavioral events into Croct, the [Google Tag Manager integration](/integrations/google-tag-manager) does that. ## Frequently asked questions ### What data does Croct send to Contentsquare? For every session impacted by a personalized experience or an AB test, Croct sends the audiences the visitor fits, the experiences that impacted them, the experiments they participated in, and the variants they were assigned. That context lands in Contentsquare alongside the data you already collect. ### Why connect Croct with Contentsquare? It powers qualitative analysis. You can filter recordings and heatmaps by the exact audience, experience, experiment, or variant a visitor was part of, so you watch the sessions that actually matter instead of scrubbing through everything. ### What can I do with the data once it is in Contentsquare? Filter recordings and heatmaps by Croct's audiences, experiences, and variants, watch how real users behave inside each personalized experience or AB test variant, and uncover the friction behind the numbers in your analytics. ### Does it affect my existing Contentsquare setup? No. The integration only adds Croct's context alongside the data you already track, so your existing heatmaps and recordings keep working exactly as before. ### Do I still need Contentsquare if Croct has built-in analytics? They answer different questions. Croct's built-in analytics tell you whether a variant won, using Bayesian analysis on 100% of your data with no sampling. This integration lets you ask Contentsquare the questions it is already set up for, broken down by the audiences, experiences, and variants Croct assigned. You don't need to choose. ### Can I use this to understand why a variant lost? Yes, and it's the most common reason to connect the two. When an experiment reports a result you didn't expect, filtering Contentsquare's recordings and heatmaps to the losing variant shows you where visitors hesitated, rage clicked, or dropped off, which is the part the numbers alone can't tell you. ### Will I see 100% of the events Croct tracks in Contentsquare? Not always. Croct can track several events within 2–3 milliseconds, but Contentsquare keeps at most 40 page events per pageview and drops the rest, and it samples pageviews on very high-traffic sites. During bursts, some events may not be captured, so the totals in Contentsquare can be lower than what Croct actually tracked. ### How much development work does it require? Next to none. Once you add our tag to your website, Croct sends the data automatically, with no extra tracking code to write or maintain. ### 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. --- Source: /integrations/demandbase.md # Croct + Demandbase **Demandbase tells you which company is on your site. Croct acts on it, changing what that company sees in real time, decided on the server before the page is sent.** Outbound gets the visitor to the page. This is what keeps them from bouncing once they arrive. ## What it does - Adapts your core value proposition when a visitor from a target industry arrives. - Adapts the message to where the account sits in its journey, from first touch to ready to buy. - Swaps customer logos and testimonials for the ones that account will recognize. - Builds audiences from firmographics such as industry, company name and employee count, with no developer involvement after setup. - Evaluates firmographics on the server, so account data drives the page without ever reaching the browser. ## How it works Demandbase identifies the account and passes its firmographic attributes into the Croct profile. You build audiences from those attributes, choose the slots that should adapt, write the content for each audience, preview it and publish. From there the decision happens on the server, per request. Demandbase usually takes a moment to evaluate a visitor, so plan for these experiences to activate on the pageviews after the first one in a session. ## Setup Make sure the Demandbase Tag is enabled and active on your website. Then map the attributes you want into the Croct profile and build your audiences from them. ## Frequently asked questions ### What is the main benefit of integrating Demandbase with Croct? While Demandbase is unparalleled at identifying anonymous firmographic data (the 'who'), it is not built to act as a real-time content delivery engine (the 'what'). By integrating Demandbase with Croct, you can bridge this gap and instantly adapt your website's content, such as value propositions, hero sections, logo clouds, and testimonials, to an account's industry, company name, or employee count in real time. ### What are the prerequisites before setting up the Demandbase data activation? All you need is to ensure the Demandbase Tag is enabled and active on your website. ### How is firmographic data from Demandbase passed into Croct? You can copy and paste our tag directly in the source code or using a tag manager. ### Is Demandbase firmographic data available immediately on the very first page view? Since Demandbase usually takes a few moments to evaluate and load, the firmographic data might not be available on the initial page view. You should plan your personalization strategies knowing that these experiences will typically activate on subsequent page views during the session. ### What specific attributes can be captured and mapped from Demandbase into Croct? You can map various firmographic details, including company name, website, industry, employee range, revenue range, account ownership, audience classification, Fortune 1000 and Forbes 2000 membership, and information level (confidence). Please check the integration docs for the full attribute list. ### Do I need a CDP to activate firmographic data? No. Firmographic attributes land directly on Croct's built-in visitor profiles, where audiences read them. There is no customer data platform to buy, connect, or keep in sync, and no historical data needed before the first personalized experience can run. ### Can I personalize using account ownership or audience classification? Yes. Account ownership and audience classification are mapped into the Croct profile like any other attribute, so you can route a named account to content aligned with its assigned rep, or adapt messaging by the audience tier Demandbase has classified the account into. ### What are some high-impact ABM use cases for this integration? Common strategies include displaying industry-specific value propositions, giving target accounts 'VIP treatment' with custom demo offers or headlines mentioning their company name, and rendering dynamic social proof like case studies and logos from businesses in the exact same vertical. ### How much development work does it take? Next to none after setup. Audiences and content are managed in the Croct interface, so launching a new account-based experience does not require a deploy. ### 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. --- Source: /integrations/google-analytics.md # Croct + Google Analytics **Google Analytics measures how people behave. Croct adds what each of them actually saw.** Connect the two, and every report can be split by audience, experience, experiment, and variant, with no extra tracking code to write. ## What it does - Sends the audiences a visitor fits, the experiences that impacted them, the experiments they joined, and the variant they were assigned. - Lets you break your existing reports down by audience, experience, experiment, and variant. - Shows what each personalized experience and each AB variant does to the way people move through your site. - Adds context alongside what you already collect, without changing any of it. - Works alongside Croct's own analytics rather than replacing either one. ## How it works For every session touched by a personalized experience or an AB test, Croct streams the context of that session into Google Analytics: the audiences the visitor fits, the experiences that impacted them, the experiments they took part in and the variants they were assigned. The data lands next to the events you already track, so nothing about your current setup changes. This integration is outbound: it sends Croct's context to Google Analytics. If you also want to bring behavioral events into Croct, the [Google Tag Manager integration](/integrations/google-tag-manager) does that. ## Frequently asked questions ### What data does Croct send to Google Analytics? For every session impacted by a personalized experience or an AB test, Croct sends the audiences the visitor fits, the experiences that impacted them, the experiments they participated in, and the variants they were assigned. That context lands in Google Analytics alongside the data you a lready collect. ### Why connect Croct with Google Analytics? It enriches your growth analysis. Instead of looking at traffic and conversions in aggregate, you can see how each audience, experience, experiment, and variant performs, all inside the reports your team already lives in. ### What can I do with the data once it is in Google Analytics? Break down any report by Croct's audiences, experiences, and variants, compare how each AB test variant moves your key metrics, and build segments to measure the real impact of personalization on conversions and revenue. ### Does it affect my existing Google Analytics setup? No. The integration only adds Croct's context alongside the data you already track, so your existing reports, events, and goals keep working exactly as before. ### Do I still need Google Analytics if Croct has built-in analytics? They answer different questions. Croct's built-in analytics tell you whether a variant won, using Bayesian analysis on 100% of your data with no sampling. This integration lets you ask Google Analytics the questions it is already set up for, broken down by the audiences, experiences, and variants Croct assigned. You don't need to choose. ### Can I use Croct audiences to build Google Analytics segments? Yes. Because the audiences a visitor fits arrive alongside the events you already collect, you can define segments on them and measure conversion and revenue for a segment defined in Croct. ### Will I see 100% of the events Croct tracks in Google Analytics? Not necessarily. Croct can track several events within 2–3 milliseconds. Still, Google Analytics imposes collection limits: events beyond 100,000 per user per day aren't logged, and high-cardinality values are grouped under an "(other)" row. When events arrive in rapid bursts, some may not be recorded, so the totals in GA4 can be lower than what Croct actually tracked. ### How much development work does it require? Next to none. Once you add our tag to your website, Croct sends the data automatically, with no extra tracking code to write or maintain. ### 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. --- Source: /integrations/google-tag-manager.md # Croct + Google Tag Manager **If you already push events to the data layer, you are sitting on a stream of behavioral data. One tag sends it to Croct, where it becomes audiences, experiments and personalized content.** No source code changes. ## What it does - Maps every one of Google's recommended data-layer events to a Croct event automatically. - Tracks conversion-indicating events as conversions, ready for AB testing and personalization. - Covers e-commerce, lead generation, user acquisition, and engagement signals such as site search and wishlist activity out of the box. - Needs no per-event configuration. - Works as the event-tracking path for Shopify Liquid themes and VTEX FastStore storefronts. ## How it works The tag listens to the recommended events on your data layer and maps them to Croct events as they are pushed. Those events feed real-time profiles, which feed audiences, which feed experiments and personalized content, all measured with built-in analytics. This integration is inbound: it brings events into Croct. The Google Analytics, Amplitude, Mixpanel, Clarity and Contentsquare integrations work in the opposite direction, sending Croct's audience, experience, and variant context out to those tools. Many teams run both. ## Setup Drop the Croct tag into Google Tag Manager once. Events start flowing immediately, with no changes to your source code. ## Frequently asked questions ### What is the main benefit of integrating Google Tag Manager with Croct? If you already push events to the data layer, you're sitting on a stream of behavioral data. By adding a single tag, that stream flows into Croct automatically, so you can build audiences, run AB tests, and personalize experiences without any extra development work. ### Which events are tracked automatically? The integration listens to all of Google's [recommended events](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm) pushed to the data layer and maps them to Croct events. That covers e-commerce, lead generation, user acquisition, and engagement signals such as site search and wishlist activity. ### Does it track conversions for AB testing and personalization? Yes. Events that typically indicate a conversion, such as a purchase, a sign-up, or a generated lead, are also tracked as conversions in Croct. This powers AB testing and personalization analytics out of the box. ### Which use cases does it cover? The integration covers e-commerce, lead generation, user acquisition, and engagement. Whether you're selling products, capturing leads, driving sign-ups, or tracking site search and wishlist activity, the relevant recommended events are mapped to Croct and ready to power your experiences. ### Is this the same as the analytics integrations? No, it works in the opposite direction. Google Tag Manager feeds events into Croct so audiences can read them. The Google Analytics, Amplitude, Mixpanel, Clarity, and Contentsquare integrations send Croct's audience, experience, and variant context out to those tools so your existing reports can be filtered by it. Many teams run both directions at once. ### Can I use this instead of a storefront integration? Yes, in some cases. If your store runs on a Shopify Liquid theme, or on a VTEX FastStore storefront that pushes GA4-style events to the data layer, the Google Tag Manager integration is the recommended path for automatic event tracking. ### How much development work does it require? None beyond adding the tag. ### What can I build with this integration? With your data-layer events flowing into Croct, you can build audiences from real behavior, run AB tests, and personalize every experience, all measured with built-in analytics. ### 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. --- Source: /integrations/hubspot.md # Croct + HubSpot **HubSpot captures your leads. Croct turns every submission into a signal you can measure, enrich profiles with, and act on**, without changing how you collect leads. ## What it does - Tracks every successful submission as a goal, so you get conversion rates and can use forms as goals in experiments and experiences. - Sends form field values into Croct profiles, which feeds segmentation and personalization. - Lets an A/B test or an experience decide which form each visitor sees. - Works with both legacy and new HubSpot forms. - Leaves your HubSpot setup untouched: submissions keep flowing exactly as they do now. ## How it works Croct listens for a successful submission and tracks it as a goal completed event. The fields you map flow into the visitor's profile. To vary the form itself, store the HubSpot form ID in a slot: your page renders whichever ID the slot returns, so each variant or experience can show a different form. ## Setup Listen for submissions with the global form event, or with the embed-code callback on legacy forms. Then map the fields you want into the profile and, if you want to vary the form, put the form ID in a slot. ## Frequently asked questions ### What is the main benefit of integrating HubSpot forms with Croct? HubSpot forms are great at capturing leads, but they don't adapt to who is filling them out. By connecting them to Croct, you can track every submission as a conversion, enrich user profiles with the data visitors submit, and test or personalize which form each visitor sees, all without changing how you collect leads in HubSpot. ### What do I need before setting up the integration? You need a Croct account with a workspace and application, the Croct SDK installed on the page where your HubSpot form is embedded, and a HubSpot account with at least one form set up. ### Does it work with both legacy and new HubSpot forms? Yes. The integration supports both HubSpot's legacy forms and the new forms. You can listen for submissions with a global form event or, on legacy forms, an embed-code callback. ### How does Croct track form submissions? Croct listens for a successful submission and tracks it as a "goal completed" event. That lets you measure conversion rates in your dashboards and use form submissions as goals in AB tests and experiments. ### What data can I send from a form to a Croct profile? You can map any form field, such as first name, last name, email, and company, into the visitor's Croct profile. That data becomes available for audience segmentation and personalization across your site. ### Can I show different forms to different visitors? Yes. By storing the HubSpot form ID in a Croct slot, you can run an AB test or build a personalized experience that decides which form each visitor sees. Your page renders whichever form ID the slot returns, so each variant or experience can display a different form. ### Can I test form length or field count? Yes. Create the form variations you want in HubSpot, then let a Croct slot decide which form ID renders. A short form and a longer qualifying form become two variants of a single experiment, measured on submission rate and on whatever downstream goal you care about. ### Does this replace HubSpot's own form analytics? No. HubSpot keeps collecting submissions exactly as it does now. Croct adds the audience, experience, and variant context around each submission, so you can see which visitors converted and which version of the form they saw. ### How much development work does it take? Wiring the submission listener once, and mapping the fields you care about. After that, forms, audiences, and experiments are managed 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. --- Source: /integrations/magento.md # Croct + Magento **Magento runs your store. Croct turns every shopping signal into audiences, AB tests, and personalized storefront content, decided on the server before the page is sent.** Nothing about your store code changes. ## What it does - Tracks product views, cart views, cart changes, checkout starts and order placements at Croct out of the box. - Fires a goal completed event for the ones that indicate a conversion, so experiments and experiences can be measured against real revenue. - Enriches the user profile with customer data, so audiences reflect who is actually browsing and buying. - Leaves your store code untouched. - Needs no separate customer data platform or analytics subscription. ## How it works The integration listens to the events your store broadcasts and forwards them to Croct with the customer data they carry. Those events build real-time profiles, which build audiences, which drive experiments and personalized content, all measured with built-in analytics. ## Frequently asked questions ### What is the main benefit of integrating Magento with Croct? Magento runs your store, but it isn't built to run AB tests or turn shopping behavior into real-time personalization. By integrating Magento with Croct, every product view, cart change, checkout, and order is automatically tracked at Croct, and customer data flows into the user profile, so you can personalize and AB test the storefront without any extra development work. ### Which Magento version is supported? The integration supports Magento 2. Once enabled on your Magento 2 store, events and customer data flow into Croct automatically, with no changes to your store code. ### Which events are tracked automatically? Product views, cart views, cart modifications, checkout starts, and order placements are tracked automatically at Croct. Events that typically indicate a conversion also fire a Goal Completed event, so you can measure AB tests and personalized experiences. ### Does it track conversions for AB testing and personalization? Yes. Whenever a shopper completes an action that typically indicates a conversion, the integration records a Goal Completed event alongside the regular store event. This powers AB testing and personalization analytics out of the box. ### Does it enrich customer profiles? Yes. The integration uses your Magento customer data to enrich the user profile with shopping behavior and customer details, so audiences reflect who is actually browsing and buying. ### Do I need a separate CDP or analytics tool? No. Shopping behavior lands directly on built-in visitor profiles, and exposure tracking, conversion tracking, and Bayesian analysis are included, so there's no customer data platform or analytics subscription to add before your first test reports. ### Does personalization slow down my storefront or cause flicker? No. Content is resolved before the response is sent, so nothing is swapped after the page paints, and there's no anti-flicker snippet. End-to-end response times are under 90 milliseconds at P95. ### How much development work does it require? None beyond the initial setup. The integration handles event tracking and profile enrichment automatically, with no changes to your store code. ### What can I build with this integration? With store events and customer data flowing into Croct, you can build audiences from shopping behavior, run AB tests, and personalize the storefront for every shopper, all measured with built-in analytics. ### 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. --- Source: /integrations/mixpanel.md # Croct + Mixpanel **Mixpanel measures how people behave. Croct adds what each of them actually saw.** Connect the two, and every report can be split by audience, experience, experiment, and variant, with no extra tracking code to write. ## What it does - Sends the audiences a visitor fits, the experiences that impacted them, the experiments they joined, and the variant they were assigned. - Lets you break your existing reports down by audience, experience, experiment, and variant. - Shows what each personalized experience and each AB variant does to the way people move through your site. - Adds context alongside what you already collect, without changing any of it. - Works alongside Croct's own analytics rather than replacing either one. ## How it works For every session touched by a personalized experience or an AB test, Croct streams the context of that session into Mixpanel: the audiences the visitor fits, the experiences that impacted them, the experiments they took part in, and the variants they were assigned. The data lands next to the events you already track, so nothing about your current setup changes. This integration is outbound: it sends Croct's context to Mixpanel. If you also want to bring behavioral events into Croct, the [Google Tag Manager integration](/integrations/google-tag-manager) does that. ## Frequently asked questions ### What data does Croct send to Mixpanel? For every session impacted by a personalized experience or an AB test, Croct sends the audiences the visitor fits, the experiences that impacted them, the experiments they participated in, and the variants they were assigned. That context lands in Mixpanel alongside the data you already collect. ### Why connect Croct with Mixpanel? It enriches your product analytics. Instead of analyzing behavior in aggregate, you can see how each audience, experience, experiment, and variant shapes the way users engage with your product. ### What can I do with the data once it is in Mixpanel? Break funnels, retention, and behavioral cohorts down by Croct's audiences, experiences, and variants, and measure how each personalized experience or AB test variant influences the events and conversions you care about. ### Does it affect my existing Mixpanel setup? No. The integration only adds Croct's context alongside the data you already track, so your existing reports, funnels, and cohorts keep working exactly as before. ### Do I still need Mixpanel if Croct has built-in analytics? They answer different questions. Croct's built-in analytics tell you whether a variant won, using B ayesian analysis on 100% of your data with no sampling. This integration lets you ask Mixpanel the questions it is already set up for, broken down by the audiences, experiences, and variants Croct assigned. You don't need to choose. ### Does Croct's context appear on events or on user profiles? Croct's audience, experience, and variant context is attached to the events it sends, so it is available for event-level breakdowns and for defining cohorts in Mixpanel. ### Will I see 100% of the events Croct tracks in Mixpanel? Not always. Croct can track several events within 2–3 milliseconds, and when a single user crosses Mixpanel's hot-shard limit of 200,000 events per day, Mixpanel renames those events and clears their identity, so they no longer appear under the original event name or user. During bursts, this can make some events look missing compared to what Croct actually tracked. ### How much development work does it require? Next to none. Once you add our tag to your website, Croct sends the data automatically, with no extra tracking code to write or maintain. ### 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. --- Source: /integrations/salesforce-commerce.md # Croct + Salesforce Commerce **Salesforce Commerce runs your store. Croct turns every shopping signal into audiences, AB tests and personalized storefront content, decided on the server before the page is sent.** Nothing about your store code changes. ## What it does - Tracks product views, cart views, cart changes, checkout starts and order placements at Croct out of the box. - Fires a goal completed event for the ones that indicate a conversion, so experiments and experiences can be measured against real revenue. - Enriches the user profile with customer data, so audiences reflect who is actually browsing and buying. - Leaves your store code untouched. - Needs no separate customer data platform or analytics subscription. ## How it works The integration listens to the events your store broadcasts and forwards them to Croct with the customer data they carry. Those events build real-time profiles, which build audiences, which drive experiments and personalized content, all measured with built-in analytics. ## Frequently asked questions ### What is the main benefit of integrating Salesforce Commerce with Croct? Salesforce Commerce runs your store, but it isn't built to run AB tests or turn shopping behavior into real-time personalization. By integrating Salesforce Commerce with Croct, every product view, cart change, checkout, and order is automatically tracked at Croct, and customer data flows into the user profile, so you can personalize and AB test the storefront without any extra development work. ### Which events are tracked automatically? Product views, cart views, cart modifications, checkout starts, and order placements are tracked automatically at Croct. Events that typically indicate a conversion also fire a Goal Completed event, so you can measure AB tests and personalized experiences. ### Does it track conversions for AB testing and personalization? Yes. Whenever a shopper completes an action that typically indicates a conversion, the integration records a Goal Completed event alongside the regular store event. This powers AB testing and personalization analytics out of the box. ### Does it enrich customer profiles? Yes. The integration uses your Salesforce Commerce customer data to enrich the user profile with shopping behavior and customer details, so audiences reflect who is actually browsing and buying. ### Do I need a separate CDP or analytics tool? No. Shopping behavior lands directly on built-in visitor profiles, and exposure tracking, conversion tracking, and Bayesian analysis are included, so there's no customer data platform or analytics subscription to add before your first test reports. ### Does personalization slow down my storefront or cause flicker? No. Content is resolved before the response is sent, so nothing is swapped after the page paints, and there's no anti-flicker snippet. End-to-end response times are under 90 milliseconds at P95. ### How much development work does it require? None beyond the initial setup. The integration handles event tracking and profile enrichment automatically, with no changes to your store code. ### What can I build with this integration? With store events and customer data flowing into Croct, you can build audiences from shopping behavior, run AB tests, and personalize the storefront for every shopper, all measured with built-in analytics. ### 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. --- Source: /integrations/sanity.md # Croct + Sanity **Sanity manages your content. Croct decides which version of it each visitor sees, on the server, before the page reaches the browser.** Your components keep rendering as they do now, with your Sanity content as the default, and personalization goes on top. ## What it does - Runs A/B tests and personalized experiences on your existing components, with no reimplementation. - Uses your Sanity content as the fallback, so nothing breaks when an experience is not running. - Resolves everything on the server, so experiences load with no flicker. - Leaves your schemas untouched: no variant fields or experiment IDs are added to your content types. - Lets marketing and CRO teams launch experiments without waiting on developers. ## How it works Connect your Sanity components to Croct slots without changing anything in the frontend. Build the experience or the AB test for the audiences you want, publish, and track the result with built-in analytics. Your schema stays exactly as it is, and adoption can be gradual, one component at a time. ## Compared to the personalization plugin Sanity maintains a first-party personalization plugin that adds A/B/n experiment fields to documents, with a direct GrowthBook integration. It handles content modeling and leaves delivery open by design: the plugin's documentation states that your frontend must assign visitors to variants and pass the variant ID when querying. | | Plugin alone | Plugin + GrowthBook | Croct | |-----------------------------------|----------------------|----------------------|--------------------------| | Variant content managed in Sanity | Yes | Yes | Yes, as fallback | | Granularity | Field-level | Field-level | Component-level | | Variant assignment and stickiness | You build it | GrowthBook | Croct | | Exposure tracking | You build it | You build it | Built in | | Statistical engine | None | GrowthBook | Bayesian, real time | | Real-time behavioral segmentation | No | Requires a CDP | Built-in profiles | | Query wiring per dynamic field | Params per field | Params per field | One call with a fallback | | Schema impact | Variant fields added | Variant fields added | None | [Read the full breakdown](https://blog.croct.com/post/personalization-sanity-visitor-behavior) ## Setup You need a Croct account and a Sanity project. The CLI scaffolds a fully configured project in one command if you are starting fresh, and the [demo project](https://github.com/croct-tech/croct-sanity-project) shows how to add Croct to an existing Sanity and Next.js setup. 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 ### What is the main benefit of integrating Sanity with Croct? Sanity is excellent at managing and structuring your content, but it isn't built to decide who should see what. By integrating Sanity with Croct, you can run AB tests and personalize your content based on your visitors' location, behavior, or custom audiences, all without reimplementing anything or over-relying on developers. ### What are the prerequisites before setting up the Sanity integration? You need an active Croct account and a Sanity project. You can scaffold a fully pre-configured project in a single command using the Croct CLI, or follow the [demo project](https://github.com/croct-tech/croct-sanity-project) to add Croct to an existing Sanity and Next.js setup. ### How does Croct connect to my Sanity content? Croct works at the component level, replacing static component content with dynamic experiences. Your Sanity content stays in place as the default fallback, while Croct injects dynamic content for visitors who match your audiences. ### Do I need to migrate or restructure my Sanity schema? No. The integration works with your existing schemas and uses your Sanity content as a fallback, so there's no migration required and you can adopt it gradually. Croct reads nothing from your dataset and writes nothing back, so no variant fields or experiment IDs are added to your content types. ### How is this different from Sanity's personalization plugin? Sanity's official personalization plugin handles variant modeling at the field level and includes a GrowthBook integration. Its documentation is explicit that your frontend must assign visitors to variants and pass the variant ID when querying, so assignment, stickiness, exposure tracking, and statistics are left to your implementation. Croct covers the whole pipeline at the component level, so a hero is one slot rather than several experiment fields queried in lockstep, and no variant fields are added to your schemas. ### What can I personalize on? Location, behavior, firmographics or any custom audience you define, resolved in real time against the visitor profile. You can also pass application-specific attributes at request time and segment on data Croct never stores. ### What can I build with this integration? You can run AB tests and create personalized experiences based on location, behavior, or custom audience rules, all with built-in analytics and without an external customer data platform. ### Does personalization cause flicker on my Sanity site? No. Content is resolved on the server and arrives inside the first response, so nothing is swapped after the page paints and crawlers see the same content a visitor would. End-to-end response times are under 90 milliseconds at P95. ### Do I need developers to manage experiences? After the initial setup, marketing and CRO teams can create and manage experiments and personalization directly from Croct's interface, without ongoing developer involvement. ### Do I need a separate CDP or analytics tool? No. Visitor profiles, audience segmentation, exposure tracking, and Bayesian analysis are all built in. With the plugin plus a feature-flagging service, behavioral targeting typically requires a CDP and tracking has to be implemented separately. ### 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. --- Source: /integrations/shopify.md # Croct + Shopify **Shopify runs the store. Croct turns shopping signals into audiences, A/B tests, and personalized content, resolved inside your Hydrogen loaders so the storefront arrives personalized with nothing flickering.** Store events flow in automatically, with no manual instrumentation to write or maintain. ## What it does - Resolves content on the server, inside Hydrogen loaders, so pages arrive personalized with no flash of default content. - Forwards product views, cart activity and search from Shopify's storefront analytics automatically. - Identifies the logged-in customer on every request, so audiences reflect real shopping behavior rather than anonymous sessions. - Feeds those signals straight into audiences, experiments and personalized content, measured with built-in analytics. - Needs no separate customer data platform or analytics subscription. ## How it works The SDK subscribes to Shopify's storefront analytics and forwards each event to your Croct application. With Shopify customer accounts, the shopper is identified on every request and their behavior enriches the Croct profile. You then build audiences from that behavior, run experiments and personalize the storefront. Event tracking is consent-aware out of the box. In the default auto mode the SDK sends nothing until Shopify's Customer Privacy API reports that tracking is allowed, so the storefront stays compliant without extra work. ## Setup 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 the slots you want to personalize, then publish content for them in Croct. Hydrogen storefronts on React Router 7 and Remix are supported. For Liquid themes, the JavaScript SDK with the [Google Tag Manager integration](/integrations/google-tag-manager) gives you the same automatic event tracking. ## Frequently asked questions ### What is the main benefit of integrating Shopify with Croct? Shopify runs your store, but it isn't built to run AB tests or turn shopping behavior into real-time personalization. By integrating your Shopify Hydrogen storefront with Croct, store events and customer data flow into Croct automatically, so you can personalize and AB test the storefront with server-side rendering and no flicker. ### Which Shopify storefronts does it support? The integration is built for Shopify Hydrogen storefronts, Shopify's headless React framework, on React Router 7 or Remix. If your store runs on a classic Liquid theme, use the JavaScript SDK together with the [Google Tag Manager integration](/integrations/google-tag-manager) for automatic event tracking. ### Which events are tracked automatically? Product views, cart views, cart updates, and collection or search views are forwarded automatically from Shopify's storefront analytics to Croct, with no manual instrumentation. You can also track custom events through the SDK. ### Does it enrich customer profiles? Yes. When your storefront uses Shopify customer accounts, the logged-in customer is identified on every request, and their shopping behavior enriches the Croct profile, so audiences reflect who is actually browsing and buying. ### Will personalization cause content flicker? No. Because Hydrogen renders on the server, Croct resolves content in your loaders and the page arrives with dynamic content already applied, with no flash of default content before the personalized version loads. ### Is event tracking consent-aware? Yes. With the default auto mode, the SDK never tracks events until Shopify's Customer Privacy API reports that tracking is allowed, so your storefront stays compliant out of the box. ### Do I need a separate CDP or analytics tool? No. Shopping behavior lands directly on built-in visitor profiles, and exposure tracking, conversion tracking, and Bayesian analysis are included, so there's no customer data platform or analytics subscription to add before your first test reports. ### How much development work does it require? Minimal. The Croct CLI detects your Hydrogen setup, installs the SDK, and wires the provider and request context for you. A manual, step-by-step guide is available if you prefer to set things up yourself. ### What can I build with this integration? With store events and customer data flowing into Croct, you can build audiences from shopping behavior, run AB tests, and personalize the storefront for every shopper, all measured with built-in analytics. ### 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. --- Source: /integrations/storyblok.md # Croct + Storyblok **Storyblok manages your content. Croct decides which version of it each visitor sees, on the server, before the page reaches the browser.** Your blocks keep rendering as they do now, with your Storyblok content as the default, and personalization goes on top. ## What it does - Runs A/B tests and personalized experiences on your existing blocks, with no reimplementation. - Uses your Storyblok content as the fallback, so nothing breaks when an experience is not running. - Resolves everything on the server, so experiences load with no flicker. - Lets marketing and CRO teams launch experiments without waiting on developers. - Brings experiences, audiences, profiles, and dashboards inside Storyblok through the Optimize app, so your team works where the content already lives. - Works on every Storyblok plan, including Starter and Growth, not only Premium and Elite. ## How it works Link your Storyblok blocks to Croct slots so they can serve dynamic content. Build the experience or the A/B test for the audiences you want, publish, and track the result with built-in analytics. Your schema stays exactly as it is, and adoption can be gradual, one block at a time. The Optimize app puts the same tooling inside Storyblok: experiences and A/B tests on your blocks, audiences and profiles to decide who sees what, and dashboards for traffic, engagement, and conversions. ## Storyblok experiments vs. the VWO plugin vs. the Optimize app Storyblok launched native AB testing in June 2026 and an official VWO plugin in August 2025. All three put variant content in Storyblok and differ in how much of the experimentation pipeline your team assembles. | | Native Experiments | VWO plugin | Optimize app | |--------------------------------------------|--------------------|----------------------------------|---------------------| | Experiment and variant configuration | Yes | Yes | Yes | | Variant content in Storyblok | Yes | Yes | Yes | | Variant assignment and bucketing | You build it | VWO | Croct | | Cross-device stickiness | You build it | Depends on identity setup | Croct | | Statistical engine | External analytics | VWO | Bayesian, real time | | Real-time personalization | No | Yes | Yes | | Audience segmentation and visitor profiles | No | In VWO | Built in | | Storyblok plans supported | Premium and Elite | Premium and Elite | All plans | | Additional subscription | Analytics platform | VWO Enterprise or Developer Plus | Croct Scale | [Read the full comparison](https://blog.croct.com/post/storyblok-ab-testing-vs-optimize-app) ## Setup You need a Croct account and a Storyblok project. The CLI scaffolds a fully configured project in one command if you are starting fresh. 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 ### What is the main benefit of integrating Storyblok with Croct? Storyblok is excellent at managing and structuring your content, but it isn't built to decide who should see what. By integrating Storyblok with Croct, you can run AB tests and personalize any block based on your visitors' location, behavior, or custom audiences, all without reimplementing your content or relying on developers. ### What is the Optimize app? Optimize is an app you install from the Storyblok directory that brings AB testing, personalization, audiences, visitor profiles, and analytics dashboards directly into the Storyblok interface, so your team can create and measure experiences without leaving Storyblok. ### What are the prerequisites before setting up the Storyblok integration? You need an active Croct account on the Scale plan, a Storyblok space with at least one story, and the [Optimize app](https://www.storyblok.com/apps/external/optimize) installed from the Storyblok app directory. The app works with every Storyblok plan, including Starter and Growth. ### How does Croct connect to my Storyblok content? You add a Croct field to your blocks and connect each one to a matching Croct slot. Your Storyblok content stays in place and serves as the default fallback, while Croct injects dynamic content for visitors who match your audiences. ### Do I need to migrate or reimplement my existing blocks? No. The integration works at the block level using your existing Storyblok content as default content, so there's no migration or schema restructuring required. Note that rich text, table, and reference fields aren't currently supported. ### What can I personalize on? Location, behavior, firmographics or any custom audience you define, resolved in real time against the visitor profile. You can also pass application-specific attributes at request time and segment on data Croct never stores. ### What can I build with this integration? You can run AB tests and create personalized experiences that target specific audiences based on location, behavior, or custom rules, all managed directly inside Storyblok with built-in analytics. ### How is this different from Storyblok's native Experiment feature? Storyblok's native experiments cover AB testing of story variants and rely on custom code and external analytics. The Optimize app adds personalization, audience segmentation, and visitor profiles, assigns variants automatically, and reports results with a built-in Bayesian engine, all manageable by marketing teams. Native experiments are also limited to Premium and Elite plans, while the Optimize app works on every Storyblok plan. You can read the [full comparison on our blog](https://blog.croct.com/post/storyblok-ab-testing-vs-optimize-app). ### How does this compare to the VWO plugin? Storyblok's official VWO plugin is a strong option if VWO is already your experimentation platform, since VWO handles bucketing, tracking, and analysis. It requires both a Storyblok Premium or Elite plan and a VWO Enterprise account or a plan with the Developer Plus add-on, and visitor data lives in VWO rather than alongside your content. The Optimize app works on any Storyblok plan and keeps content, audiences, profiles, and analytics in one place. ### Do experiments cause flicker on my Storyblok site? No. Variants are assigned on the server and arrive inside the first response, so nothing is swapped after the page paints. There is no anti-flicker snippet and no loading state, and end-to-end response times are under 90 milliseconds at P95. ### Do I need developers to manage experiences? After the initial setup, marketing and CRO teams can create and manage experiments and personalization directly from the app, without ongoing developer involvement. ### Do I need a separate CDP or analytics tool? No. Visitor profiles, audience segmentation, exposure tracking, and Bayesian analysis are all built in, so there is nothing to integrate before your first experiment reports. ### 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. --- Source: /integrations/strapi.md # Croct + Strapi **Strapi manages your content. Croct decides which version of it each visitor sees, on the server, before the page reaches the browser.** Your components keep rendering as they do now, with your Strapi content as the default, and personalization goes on top. ## What it does - Runs AB tests and personalized experiences on your existing components, with no reimplementation. - Uses your Strapi content as the fallback, so nothing breaks when an experience is not running. - Resolves everything on the server, so experiences load with no flicker. - Leaves your schemas untouched: no variant fields or experiment IDs are added to your content types. - Lets marketing and CRO teams launch experiments without waiting on developers. ## How it works Connect your Strapi dynamic zones and components to Croct slots without touching the frontend. Build the experience or the AB test for the audiences you want, publish, and track the result with built-in analytics. Your schema stays exactly as it is, and adoption can be gradual, one component at a time. ## Setup You need a Croct account and a Strapi project. The CLI scaffolds a fully configured project in one command if you are starting fresh. 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 ### What is the main benefit of integrating Strapi with Croct? Strapi is excellent at managing and structuring your content, but it isn't built to decide who should see what. By integrating Strapi with Croct, you can run AB tests and personalize your content based on your visitors' location, behavior, or custom audiences, all without reimplementing anything or over-relying on developers. ### What are the prerequisites before setting up the Strapi integration? You need an active Croct account and a Strapi project. You can scaffold a fully pre-configured project in a single command using the Croct CLI. ### How does Croct connect to my Strapi content? Croct maps to your Strapi dynamic zones and components, replacing static content with dynamic experiences. Your Strapi content stays in place as the default fallback, while Croct injects dynamic content for visitors who match your audiences. ### Do I need to migrate or restructure my Strapi schema? No. The integration works with your existing schemas and uses your Strapi content as a fallback, so there's no migration required, and you can adopt it gradually. Croct reads nothing from your Strapi project and writes nothing back, so rolling back means removing a single call. ### What can I personalize on? Location, behavior, firmographics, or any custom audience you define, resolved in real time against the visitor profile. You can also pass application-specific attributes at request time and segment on data Croct never stores. ### What can I build with this integration? You can run AB tests and create personalized experiences based on location, behavior, or custom audience rules, all with built-in analytics and without an external customer data platform. ### Does personalization cause flicker on my Strapi site? No. Content is resolved on the server and arrives inside the first response, so nothing is swapped after the page paints and crawlers see the same content a visitor would. End-to-end response times are under 90 milliseconds at P95. ### Do I need developers to manage experiences? After the initial setup, marketing and CRO teams can create and manage experiments and personalization directly from Croct's interface, without ongoing developer involvement. ### Do I need a separate CDP or analytics tool? No. Visitor profiles, audience segmentation, exposure tracking, and Bayesian analysis are all built in, so there is nothing to integrate before your first experiment reports. ### 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. --- Source: /integrations/vtex.md # Croct + VTEX **VTEX runs your store. Croct turns every shopping signal into audiences, AB tests, and personalized storefront content, decided on the server before the page is sent.** A single script does it, with your store code intact. ## What it does - Tracks product views, cart activity, checkouts, orders, and searches at Croct out of the box. - Fires a goal completed event for the ones that indicate a conversion, so experiments and experiences can be measured against real revenue. - Enriches the user profile with customer data, so audiences reflect who is actually browsing and buying. - Leaves your store code untouched. - Normalizes the monetary values VTEX reports, converting cart totals from cents to major units and tracking discounts as positive amounts. - Needs no separate customer data platform or analytics subscription. ## How it works The integration listens to the events your store broadcasts and forwards them to Croct with the customer data they carry. Those events build real-time profiles, which build audiences, which drive experiments and personalized content, all measured with built-in analytics. ## Setup Add the Croct script to your storefront, or drop it into Google Tag Manager to fire on all pages. ## Frequently asked questions ### What is the main benefit of integrating VTEX with Croct? VTEX runs your store, but it isn't built to run AB tests or turn shopping behavior into real-time personalization. By integrating VTEX with Croct, every product view, cart change, checkout, and order is automatically tracked at Croct, and customer data flows into the user profile, so you can personalize and AB test the storefront without any extra development work. ### Which VTEX storefronts are supported? The integration works with stores built with Store Framework (VTEX IO), which broadcast their events through the same mechanism used by Pixel apps. FastStore storefronts report their interactions as GA4-style analytics events instead, so if your storefront pushes those to the data layer, use the [Google Tag Manager integration](/integrations/google-tag-manager). ### Which events are tracked automatically? Product views, cart views, cart modifications, checkout starts, order placements, searches, and wishlist additions. Every supported event also records a conversion in Croct, so you can measure AB tests and personalized experiences from any store interaction. ### Are order values and revenue tracked accurately? Yes. Croct normalizes the monetary values VTEX reports, converting cart totals from cents to major units and tracking discounts as positive amounts. VTEX reports a purchase through two separate events, but the order is tracked only once, so revenue is never counted twice. ### Does it enrich customer profiles? Yes. The integration uses VTEX customer data to enrich the user profile with standard attributes such as first name, last name, email, phone, and address, taken from the customer, cart, and order events. ### Do I need a separate CDP or analytics tool? No. Shopping behavior lands directly on built-in visitor profiles, and exposure tracking, conversion tracking, and Bayesian analysis are included, so there's no customer data platform or analytics subscription to add before your first test reports. ### Does personalization slow down my storefront or cause flicker? No. Content is resolved before the response is sent, so nothing is swapped after the page paints, and there's no anti-flicker snippet. End-to-end response times are under 90 milliseconds at P95. ### How much development work does it require? None beyond the initial setup. You add a single script to your storefront's HTML or inject it with Google Tag Manager, and the integration handles event tracking and profile enrichment automatically, with no changes to your store code. ### What can I build with this integration? With store events and customer data flowing into Croct, you can build audiences from shopping behavior, run AB tests, and personalize the storefront for every shopper, all measured with built-in analytics. ### 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. --- Source: /integrations/zoominfo.md # Croct + ZoomInfo **ZoomInfo tells you which company is on your site. Croct acts on it, changing what that company sees in real time, decided on the server before the page is sent.** Outbound gets the visitor to the page. This is what keeps them from bouncing once they arrive. ## What it does - Adapts your core value proposition when a visitor from a target industry arrives. - Adapts the message to where the account sits in its journey, from first touch to ready to buy. - Swaps customer logos and testimonials for the ones that account will recognize. - Builds audiences from firmographics such as industry, company name and employee count, with no developer involvement after setup. - Evaluates firmographics on the server, so account data drives the page without ever reaching the browser. ## How it works ZoomInfo identifies the account and passes its firmographic attributes into the Croct profile. You build audiences from those attributes, choose the slots that should adapt, write the content for each audience, preview it and publish. From there the decision happens on the server, per request. ZoomInfo usually takes a moment to evaluate a visitor, so plan for these experiences to activate on the pageviews after the first one in a session. ## Setup Make sure ZoomInfo WebSights is enabled, with Website Personalization activated in your domain settings. Then map the attributes you want into the Croct profile and build your audiences from them. ## Frequently asked questions ### What is the main benefit of integrating ZoomInfo with Croct? While ZoomInfo is unparalleled at identifying anonymous firmographic data (the 'who'), it is not built to act as a real-time content delivery engine (the 'what'). By integrating ZoomInfo with Croct, you can bridge this gap and instantly adapt your website's content, such as value propositions, hero sections, logo clouds, and testimonials, to an account's industry, company name, or employee count in real time. ### What are the prerequisites before setting up the ZoomInfo data activation? All you need is to ensure ZoomInfo WebSights is enabled on your website, with Website Personalization activated in your domain settings. ### How is firmographic data from ZoomInfo passed into Croct? You can push firmographic data into Croct using Google Tag Manager, which captures ZoomInfo data once the visitor is resolved and updates their profile automatically. ### Is ZoomInfo firmographic data available immediately on the very first page view? Since ZoomInfo usually takes a few moments to evaluate and load, the firmographic data might not be available on the initial page view. You should plan your personalization strategies knowing that these experiences will typically activate on subsequent page views during the session. ### What specific attributes can be captured and mapped from ZoomInfo into Croct? You can map various firmographic details, including company name, website, industry, employee count, annual revenue, and company funding. Please check the integration docs for the full attribute list. ### Do I need a CDP to activate firmographic data? No. Firmographic attributes land directly on Croct's built-in visitor profiles, where audiences read them. There is no customer data platform to buy, connect, or keep in sync, and no historical data needed before the first personalized experience can run. ### Can I personalize based on company funding stage? Yes. Company funding is mapped into the Croct profile alongside the other firmographics, so you can adapt pricing emphasis, plan recommendations, or case studies to a recently funded company versus an established enterprise. ### What are some high-impact ABM use cases for this integration? Common strategies include displaying industry-specific value propositions, giving target accounts 'VIP treatment' with custom demo offers or headlines mentioning their company name, and rendering dynamic social proof like case studies and logos from businesses in the exact same vertical. ### How much development work does it take? Next to none after setup. Audiences and content are managed in the Croct interface, so launching a new account-based experience does not require a deploy. ### 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. --- Source: /page/affiliate-program.md # Croct affiliate program Refer Croct to your audience and earn $100 for every customer who converts to a paid plan. There is no cap on how much you can earn. ## The offer - **High commission.** $100 for every referred customer who converts to a paid plan. - **Extended cookie life.** Any visitor who clicks your link and converts within 60 days counts. - **Dedicated support.** A partner manager guides you through the program and keeps you current on the product. - **No limits.** Earnings are uncapped. ## Who it is for Creators, SaaS reviewers, freelancers, entrepreneurs, consultants, publishers, influencers and members of growth, product and developer communities. Anyone with an audience that builds or optimizes websites, and who wants their content to earn. Your affiliate link works anywhere you already publish: a blog, an article, a social account, a forum or an email to your network. ## The terms Three steps, no lengthy forms and no approval calls: 1. **Sign up free** as an affiliate and receive your unique referral link. 2. **Promote Croct** by sharing that link with your audience. 3. **Earn $100** every time someone converts to a paid plan, with no limit. The 60-day cookie means a click today can still pay out two months from now. Commission is paid per converted customer, not per signup. ## Frequently asked questions ### What is Croct, in one sentence? A component-based headless CMS with personalization and A/B testing built in, which lets product and marketing teams change and optimize content without developers. ### Who converts, and when do I earn? You earn when someone who clicked your link converts to a paid plan within 60 days. ### Is there an approval process? No lengthy forms and no approval calls. Sign up, get your link, start sharing. ### Is there a limit on earnings? No. --- Source: /page/agencias.md # Croct para agências A Croct impulsiona os resultados do seu cliente e gera backlog para o seu time de desenvolvimento. Você aumenta sua recorrência e reduz seu churn. ## A oferta Um programa de parceria construído em torno de CRO como serviço contínuo, e não como projeto pontual: - **Ciclos de backlog.** Com CRO, sua agência atua de forma proativa, identifica oportunidades de melhoria e gera backlog para o seu time de desenvolvimento. - **Além do clássico teste A/B.** Estratégias de personalização aumentam em até 20% a taxa de conversão e a receita, enquanto testes A/B raramente ultrapassam 5% de uplift. - **Impacto em receita.** Otimizações baseadas em dados trazem incremento de receita para o seu cliente, estreitam o relacionamento e aumentam o lifetime da conta. São dois modelos comerciais. No primeiro, e mais utilizado, o cliente recebe uma tabela de preços diferenciada, sem custo de setup e com valores menores do que na contratação direta. No segundo, a tabela é a mesma da contratação direta e a agência ganha 10% de comissão no primeiro ano de contrato, 5% no segundo e 3% no terceiro. Nos dois casos, a contratação da plataforma é sempre feita pelo cliente, e não pela agência. ## Para quem é O programa tem fit com a sua agência se você: - **Desenvolve sites e e-commerces** e trabalha com plataformas headless para criar sites robustos e escaláveis. - **Utiliza frameworks modernos** como Next.js e React, reutilizando componentes entre projetos. - **Gerencia múltiplos clientes** e precisa de estratégias replicáveis que escalem em diversas indústrias, no B2B e no B2C. - **Precisa crescer a carteira** e quer se diferenciar agregando tecnologias que outras agências não oferecem. - **Valoriza parcerias de longo prazo** com parceiros que capacitam seu time e ajudam a expandir contas. - **Tem interesse em co-marketing** para promover o sucesso do cliente e adquirir novos logos. ## Como funciona Tudo começa com uma reunião rápida entre a agência e o time comercial da Croct para repassar os requisitos da parceria, avaliar o fit e selecionar o primeiro cliente e caso de uso. Em seguida vem uma demonstração técnica do produto, já com o contexto aplicado. Depois disso, o caminho tem três etapas: 1. **Onboarding.** Treinamentos e conteúdos exclusivos para conhecer as funcionalidades da plataforma. 2. **Go-to-market.** Implementação da Croct em pelo menos um projeto de cliente, que é onde vem a experiência prática. 3. **Certificação.** Colaboração na publicação de um case de sucesso e treinamento do time comercial. A Croct pode liderar apresentações, conversas e negociações com o cliente, ou treinar o seu time comercial para conduzir a contratação. O relacionamento com o seu cliente continua sendo seu. ## Dúvidas frequentes ### Qual o primeiro passo para ser um parceiro? Uma reunião rápida entre a agência e o time comercial para repassar os requisitos, avaliar o fit e selecionar o primeiro cliente e caso de uso. Em seguida, a demonstração técnica do produto com o contexto já aplicado. ### Qual é o modelo de negócios da parceria? Dois modelos. Tabela de preços diferenciada, sem setup e com valores reduzidos para o cliente, ou tabela padrão com comissão de 10% para a agência no primeiro ano, 5% no segundo e 3% no terceiro. A contratação é sempre feita pelo cliente. ### O que acontece quando indico a Croct para um cliente? A Croct pode liderar as apresentações e negociações, ou treinar o seu time comercial para conduzi-las. Você escolhe o melhor caminho para a agência. ### Posso usar o produto de forma white label? Não, já que a contratação e o pagamento são feitos diretamente pelo cliente. ### A Croct tem contato com o meu cliente? Se a agência quiser, sim. Na maioria dos casos os dois times trabalham juntos durante todo o ciclo. A Croct é especialista no produto, a agência é especialista na estratégia, e o relacionamento com o cliente continua sendo seu. ### O que está incluso nos treinamentos? Para desenvolvedores, treinamentos sobre as APIs, boas práticas de implementação e suporte técnico no dia a dia. Para o time que opera a plataforma, funcionalidades, configurações, dashboards e análise de dados. Para o time comercial, aplicabilidade, casos de uso por indústria e oportunidades de negócio. ### Terei um gerente de conta dedicado? Sim. Durante o onboarding há checkpoints semanais para o cliente ver resultado rápido, e depois reuniões de acompanhamento para avaliar novas oportunidades. ### Os casos de sucesso são sobre o cliente ou a agência? Os dois. A certificação começa com um case sobre o cliente, citando a agência como parceira de negócios. A partir do segundo cliente, os cases também promovem o trabalho da agência. ### O que acontece se o meu cliente deixar a agência? O cliente continua utilizando a plataforma, já que a contratação é dele. Os acessos do time da agência à conta são revogados. --- Source: /page/agencies.md # Croct for agencies Croct improves your client's results and generates backlog for your development team. You gain recurring revenue and lose less of it to churn. ## The offer A partner program built around CRO as an ongoing service rather than a one-off build: - **Backlog cycles.** Offering CRO makes your agency proactive. You find the opportunities, and each one becomes work for your development team. - **Beyond the classic A/B test.** Personalization strategies lift conversion and revenue by up to 20%, where A/B tests rarely pass a 5% uplift. - **Revenue impact.** Data-driven optimization raises your client's revenue, which strengthens the relationship and extends the lifetime of the account. Two commercial models. In the first and most common one, your clients get a partner price list with no setup fee and lower rates than they would get on their own. In the second, they pay the standard price and your agency earns 10% commission in the first year of the contract, 5% in the second and 3% in the third. In both cases the client contracts the platform directly, not the agency. ## Who it is for The program fits your agency if you: - **Build websites and e-commerce**, on headless platforms, to create robust and scalable sites. - **Use modern frameworks** such as Next.js and React, reusing components across projects. - **Manage multiple clients** and need repeatable strategies that scale across industries, in B2B and B2C. - **Want to grow your portfolio** and stand out by offering technology other agencies do not. - **Value long-term partnerships** with vendors who train your team and help you expand accounts. - **Are interested in co-marketing** to promote client success and win new logos. ## How it works Becoming a partner starts with a short call to align on requirements, check the fit and pick the first client and use case. A technical demo follows, with your context already applied. After that the path is three steps: 1. **Onboarding.** Exclusive training and material to learn the platform. 2. **Go-to-market.** Implement Croct on at least one client project, which is where the practical experience comes from. 3. **Certification.** Collaborate on a success story and train your commercial team to become a certified partner. Croct can lead the presentations and negotiations with your client, or train your commercial team to run them. Either way, your relationship with your client stays yours. ## Frequently asked questions ### What is the business model of the partnership? Two models. A partner price list with no setup fee and reduced rates for the client, or the standard price list with 10% commission to the agency in the first year, 5% in the second and 3% in the third. The client always contracts the platform directly. ### What happens when I refer a client? Croct can lead the presentations, conversations and negotiations, or train your commercial team to run them. You choose the path that suits the agency. ### Can I use Croct white label? No, because the contract and the payment are made directly by the client. ### Does Croct talk to my client? If the agency wants it to. In most cases both teams work together through the whole cycle. Croct is the expert on the product, your agency is the expert on the strategy, and the client relationship stays with you. ### What do the trainings cover? Developers get API training, implementation practices and day-to-day technical support. The team operating the platform gets features, configuration, dashboards and analysis. The commercial team gets use cases by industry and where the business opportunities are. ### Do I get a dedicated account manager? Yes. Weekly checkpoints during onboarding so the client sees results quickly, and follow-up meetings afterwards to find new opportunities. ### Are the success stories about the client or the agency? Both. Certification starts with a story about the client that names the agency as a business partner. From the second client on, the stories also promote the agency's own work. ### What happens if my client leaves the agency? The client keeps using the platform, since they hold the contract. The agency team's access to that account is revoked. --- Source: /page/personalization-blueprint.md # Free personalization blueprint Before spending more on ads, fix what happens after the click. The blueprint is a free conversion audit, a personalization plan and a prioritized roadmap of what to change first, normally a $1,500 engagement. ## The offer A team goes through your ecosystem rather than a checklist, and you get back: - **Low-hanging fruit.** Three to five proven personalization strategies that historically yield a 10% to 15% conversion uplift within weeks. - **High-intent segmentation criteria.** A data-backed list of the exact audiences to target first to prove value quickly. - **Personalization map.** A visual breakdown of which headers, CTAs and hero sections on your site should become dynamic. Every recommendation comes from a playbook database built over years of growth experiments, filtered for what works in your specific case. ## Who it is for Teams already buying traffic whose conversion rate is not keeping up with it, and teams about to invest in personalization who want a prioritized plan before writing any code. ## The terms The audit covers four areas: - **Messaging fit.** Your blog and rich media, checked for whether your highest-value content intercepts buyers at the right stage of the funnel. - **Position clarity.** Your industry, personas, products and use-case pages, checked for whether the core messaging lands or confuses. - **Campaign consistency.** Your live Meta, Google and LinkedIn ads, checked against the landing pages that receive them. - **Technical DNA.** Your frontend stack and connected software, so the recommendations fit the tools you already run. ## Frequently asked questions ### What does it cost? Nothing. The equivalent engagement is normally $1,500. ### How is this different from asking an AI to audit my site? The automated part is the easy part. This goes through your ads, your content, your personas and your stack, and returns a plan tied to your traffic profile rather than generic advice. ### Do I have to use Croct to get value from it? No. The roadmap is about what to change on your site. Implementing it with Croct is faster, but the analysis stands on its own. --- Source: /personalization.md # Personalization **Server-side personalization means the server decides what each visitor sees and renders it into the HTML before the response is sent.** With Croct, it is possible to change what a visitor sees based on their context and what they are doing, decided before the page leaves the server. No replacement CMS, no render-blocking script, no cost to LCP. ## How it works Three steps. Define the audience from behavior, campaign source, location, device, interests, or first-party data, with no integrations or historical data required. Specify the content each audience should get, in the components you already have. Preview it exactly as visitors will see it, collect approvals, and publish. From there Croct resolves the experience per request, on the server. Pausing or restarting an experience takes no development work. Visitor profiles are built in, so behavioral segmentation does not require a separate CDP. Conditions evaluate against live session data, which means a visitor who viewed pricing twice in the current session can be targeted on that behavior immediately rather than after an overnight sync. ## Features - **Server-side rendering.** Personalized content arrives in the first response, so nothing flickers. By default, crawlers see default content, but this is configurable. This means it is also possible to show them what visitors see. - **Built-in visitor profiles.** Real-time behavioral data without integrating and maintaining a CDP. - **Real-time audiences.** Segments update the moment a visitor qualifies. - **Journey personalization.** Every touchpoint adapts, not just the entry page. - **Custom data targeting.** Pass your own attributes (plan, quota, account age) at request time so personalization can depend on data that never reaches the browser. - **Content placeholders.** Drop a name, a location, or a greeting straight into the copy. - **Component-level resolution.** Only the personalized region is dynamic, so the page shell stays cacheable. - **Cross-device consistency.** An identified visitor gets the same experience on every device. - **Multi-language support.** Personalized content in any language, with no extra development. - **Scheduled launches.** Publish for a holiday, an off-hour, or any window you choose. - **Live preview.** See and share the exact experience before it goes live. - **Personalization analytics.** Segmented dashboards that measure what each experience did. - **A/B testing.** Compare personalized variants to find what each audience responds to. - **Fallback content.** If a request fails, your existing content renders and the page ships. - **Privacy-first.** Compliance rules are enforced while the data still drives the experience. ## Building with it Your CMS stays where it is. Croct sits alongside it and makes the content it holds contextual. Developers mark the slots, and everything after that happens in the interface. 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 ### What is server-side personalization? Server-side personalization means the server decides what each visitor sees and renders it into the HTML before the response is sent. The browser receives a page that is already personalized rather than a generic one that JavaScript rewrites afterward, so there is no flicker, no cost to your Core Web Vitals, and personalized content is visible to search engines. ### How does real-time personalization work on Croct? Real-time personalization on Croct works by using audience segmentation rules to evaluate specific criteria against a visitor's current [context](https://docs.croct.com/reference/cql/context), including their device, pages visited, and real-time behavior. Our engine acts as an abstraction layer that maps complex data points, such as location or intent, to simple business rules. These evaluations are designed for high performance, often occurring with latencies under 40 milliseconds to ensure immediate content delivery. This process allows the platform to turn live data into actions that optimize the user journey in real time. ### Is Croct a CMS or a personalization platform? Both. Croct is a component CMS with personalization as a native capability rather than an add-on, and G2 ranks it #1 in the headless CMS for personalization category. Teams that already run a CMS use Croct as a personalization layer on top of it, while teams that do not use it as their CMS. The integration work is the same either way. ### Do I have to replace my CMS? No. Croct works alongside the headless CMS you already run, including Storyblok, Sanity, Strapi, Contentful, and Prismic, and uses its content as the default. Your schemas stay untouched: we read nothing from your CMS and write nothing back, so you adopt it one component at a time and roll back by removing a single call. ### Do I need to integrate a CDP to segment visitors? No. Most headless CMS platforms handle content delivery and leave visitor data to an external customer data platform, which means buying and maintaining a second system before personalization does anything. Croct does not require a CDP, external integrations, or historical data to get started. We automatically centralize events, traits, and IDs into live, actionable profiles that you can use to build your segments, and you can still connect a CDP to enrich those profiles if you want to. ### Can I personalize content for first-time, anonymous visitors? Yes, you can personalize content for visitors even while they are still anonymous. We leverage real-time anonymous signals, such as campaign source, location, and session activity, to predict intent from the very first page view. This allows you to highlight relevant lead magnets or offers before a user ever identifies themselves. ### What are the most common personalization use cases? Common [use cases](/playbooks) include tailoring content for specific stages of the funnel, such as differentiating messages for leads versus existing customers. Customers also frequently implement geographic targeting, interest-based content for blog readers, and campaign-based consistency for search and social ads. Other popular strategies include revenue optimization through free shipping triggers based on cart value and real-time behavioral interventions to reduce cart abandonment. ### Can I personalize entirely different page layouts, or just text and images? You can personalize both. You can define what each variant displays, whether that is a simple text or image change, a completely different layout, or an entirely different conversion flow. ### Can I personalize elements or components across multiple pages? Yes, you can personalize the entire user journey across multiple elements and pages. You can combine multiple slots across your website to maintain consistent communication from the first interaction through to conversion. ### Can I personalize on data Croct doesn't collect? Yes. You can pass your own attributes, such as subscription plan, quota usage, or account age, as [context](https://docs.croct.com/reference/cql/context) at request time and reference them in your audience conditions. Because evaluation happens on the server, that data drives the experience without ever reaching the browser. ### Does personalization hurt performance? No. Content resolves on the server before the response is sent, with end-to-end response times under 90 milliseconds at the 95th percentile. ### Does personalization break CDN caching? It can with tools that personalize at the route level, since a cached route would serve one visitor's content to everyone. Croct resolves at the component level, so only the personalized region is dynamic, and the rest of the page stays prerendered and cacheable. See [prerendering](https://docs.croct.com/reference/sdk/nextjs/prerendering) for the available strategies. ### Does personalized content get indexed by search engines? It depends. By default, crawlers only see the default content, but this is configurable. This means that, if desired, it is possible to show personalized content for bots. Since content is resolved before the response is sent, crawlers can receive the same HTML a visitor would rather than a generic page that JavaScript rewrites afterward. Client-side personalization leaves crawlers indexing the default content only. ### Can I preview personalized experiences before publishing them? Yes, we provide a [live preview feature](https://docs.croct.com/explanation/content/preview) that allows you to see exactly how personalized content will appear. This enables you to share, review, and perfect experiences to keep your team aligned before they go live. ### Can I schedule personalized experiences to launch and end automatically? Yes, we provide full control over [scheduling launches](https://docs.croct.com/explanation/experience/scheduling) in advance. You can plan experiences to automatically become active or pause based on custom schedules, such as holidays or specific off-hours. ### How does the platform support multi-language personalization? We support multilingual content by enabling you to deliver [locale-specific variants](https://docs.croct.com/explanation/slot#localization) of your personalization without additional development. This enables you to speak your visitors' language and maintain a consistent global strategy across all your personalized slots. ### Does the personalization engine rely on cookies? No. Personalization is evaluated per request from the visitor context, so cookies are not required. You can optionally use a first-party cookie to persist the user ID when you want assignments to stay consistent across sessions, but it is not the default setup and no third-party cookies are used. ### Can marketers publish without developers? Yes. After the slots exist, audiences, content, preview, approval, and scheduling all happen in the Croct interface. Developer involvement is a one-time integration, not a task per experience. ### Do I need to integrate an analytics tool to analyze experience results? No, you do not need external vendors for this. We provide built-in [personalization analytics and dashboards](https://docs.croct.com/reference/analytics/experience/overview) that let you track the performance of your personalized experiences across audiences, devices, and variants. ### What happens if a content request fails? Every slot has [fallback content](https://docs.croct.com/explanation/content/fallback-content) that renders if a request fails or times out, so the page always ships with your existing content rather than an error. ### 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. --- Source: /playbooks.md # Personalization playbooks Knowing that personalization works is easy. Knowing how to start and what to personalize first is not. The playbooks listed below are concrete recipes that walk through all the steps: defining the audience, thinking about the content, and measuring the performance. ## How it works Each playbook takes a signal you already have and turns it into an experience. It names the audience to build, the components to make dynamic, the content to write for each variant, and the goal to measure against, so the work is configuration rather than invention. ## Features - [Search term](https://docs.croct.com/immersion/playbooks/search-terms): Match the page to what the visitor searched for. - [Organic intent](https://docs.croct.com/immersion/playbooks/organic-intent): Adapt content to what organic traffic came looking for. - [Interests](https://docs.croct.com/immersion/playbooks/interests): Use browsing behavior to lead with what someone already cares about. - [Location](https://docs.croct.com/immersion/playbooks/location): Tailor offers, currency, and wording to the visitor's region. - [Marketing campaign](https://docs.croct.com/immersion/playbooks/marketing-campaigns): Carry the ad's message into the site, so the journey stays consistent. - [Leads](https://docs.croct.com/immersion/playbooks/leads): Turn interest into a qualified lead with the right magnet at the right moment. - [Free shipping](https://docs.croct.com/immersion/playbooks/free-shipping): Show shipping offers based on location and cart value. - [Account-based marketing](https://docs.croct.com/immersion/playbooks/abm-campaigns): Keep B2B messaging consistent between ads and website. - [Customers](https://docs.croct.com/immersion/playbooks/customers): Increase satisfaction and expansion for people who already bought. - [Blog readers](https://docs.croct.com/immersion/playbooks/blog-readers): Adapt what someone sees based on the posts they have read. ## Building with it Every playbook runs on the same primitives: an audience, a slot, and content. Developers are involved only for the slots integration. 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 ### Where should customers start? Whichever signal they already have the most of. Campaign data and location are usually the fastest to act on. ### Do playbooks require development work? Only the slots integration. Audiences and content come from 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. --- Source: /pricing.md # Croct pricing Croct is priced per monthly active user (MAU), the number of unique people who interact with your website in a month, regardless of whether a personalized experience or active experiment impacts them. Every plan (even the free one) includes personalization, A/B testing, component CMS for dynamic content, server-side rendering, audience segmentation, and unsampled analytics. ## Plans | Plan | Included MAU | Annual (USD) | Monthly (USD) | Annual (BRL) | Monthly (BRL) | |:-------------|-------------:|-------------:|--------------:|-------------:|--------------:| | Forever-free | 10,000 | Free | Free | Free | Free | | Growth | 20,000 | $100/mo | $120/mo | R$600/mo | R$720/mo | | Growth | 30,000 | $150/mo | $180/mo | R$900/mo | R$1,080/mo | | Growth | 40,000 | $200/mo | $240/mo | R$1,200/mo | R$1,440/mo | | Growth | 50,000 | $250/mo | $300/mo | R$1,500/mo | R$1,800/mo | | Scale | Custom | Custom | Custom | Custom | Custom | Annual plans are billed once a year and shown here as the equivalent monthly amount. Past 50,000 MAU, Growth tiers are 100,000 MAU, 250,000 MAU, 500,000 MAU, 1,000,000 MAU, 2,000,000 MAU, 3,000,000 MAU, etc. For both these Growth tiers and for the Scale plan, pricing is available upon sales requests at /contact/sales. All paid plans offer an optional feature that lets the MAU quota scale beyond the monthly visitors limit, charging only for the overage per 10,000 users. Forever-free needs no credit card. Growth is self-serve and priced by volume tier. Scale is for teams that need custom quotas, event-based segmentation, scheduled publishing, or premium support. ## Billing Annual plans are billed once a year and work out about two months cheaper than paying monthly. Payment is by credit card, and sales can arrange other methods. By default, you can upgrade or downgrade whenever you like, though moving from annual to monthly may be limited, because annual pricing reflects the longer commitment. Go over your MAU quota and you have three options. Upgrade the plan, turn on pay-as-you-go to cover the extra users, or do nothing. If you do nothing, Croct stops serving personalization, default content, A/B test variants and event tracking until you adjust the plan or it renews next month. The admin panel keeps working the whole time. Known bots and crawlers do not count toward the MAU limit on paid plans, because bot filtering leaves that traffic out. Turn bot filtering off and they count as users. ## Plan comparison ### Organization | Feature | Description | Free | Growth | Scale | |:-----------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------------|----------:|----------:|----------:| | [Workspaces](https://docs.croct.com/explanation/workspace/overview) | Organize your business units, projects, or products into dedicated workspaces for efficient management. | 1 | 1 | 1 | | [Application](https://docs.croct.com/explanation/application/overview) | Isolate metrics and development environments with individual applications. | 2 | 4 | 6 | | Members | Invite members to your account for collaborative work. | Unlimited | Unlimited | Unlimited | ### Content | Feature | Description | Free | Growth | Scale | |:----------------------------------------------------------------------------|:-------------------------------------------------------------------------------|-----:|-------:|-------:| | [Components](https://docs.croct.com/explanation/component) | Ensure consistency with reusable components that reflect your design system. | 3 | 30 | 60 | | [Slots](https://docs.croct.com/explanation/slot) | Control your content independently for granular personalization. | 3 | 20 | 40 | | [Instant preview](https://docs.croct.com/explanation/content/preview) | Refine and perfect your content before going live. | Yes | Yes | Yes | | [Auto versioning](https://docs.croct.com/explanation/slot#versioning) | Implement redesigns and feature additions without the risk of breaking things. | Yes | Yes | Yes | | Client-side rendering | Seamlessly integrate personalization in your existing applications. | Yes | Yes | Yes | | Server-side rendering | Eliminate loading screens and flickering for a smoother user experience. | Yes | Yes | Yes | | [Bot filtering](https://docs.croct.com/explanation/workspace/bot-exclusion) | Exclude known-bot traffic from experiences and experiments. | No | Yes | Yes | | Dynamic placeholders | Make your content more engaging and relevant to your audience. | No | No | Yes | | [Localization](https://docs.croct.com/explanation/slot#localization) | Speak the language of your audience through locale-specific content. | No | Add-on | Add-on | | [Scheduling](https://docs.croct.com/explanation/experience/scheduling) | Plan ahead and automate your content delivery with our scheduling feature. | No | Add-on | Add-on | ### Personalization | Feature | Description | Free | Growth | Scale | |:-----------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------|-----:|-------:|------:| | [Experiences](https://docs.croct.com/explanation/experience/introduction) | Engage every visitor with unique, tailored experiences across the whole website. | 1 | 15 | 30 | | [Audiences per experience](https://docs.croct.com/explanation/experience/introduction#define-the-audience) | Compare and analyze metrics for different audiences within the same experience. | 1 | 3 | 5 | | [Audiences](https://docs.croct.com/explanation/audience/introduction) | Segment your users into specific audiences for tailored experiences. | 2 | 15 | 30 | | [Real-time evaluation](https://docs.croct.com/reference/api/service/evaluation/quick-start) | Evaluate queries in real time for programmatic personalization and custom integrations. | Yes | Yes | Yes | ### Experimentation | Feature | Description | Free | Growth | Scale | |:-----------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------|-----:|-------:|------:| | [AB testing](https://docs.croct.com/explanation/experiment) | Test different variations of your content or features to get the best performance. | Yes | Yes | Yes | | [Bayesian experiments](https://docs.croct.com/reference/analytics/experiment/widgets/performance-per-goal) | Drive effective decision-making with clear and reliable experiment results. | Yes | Yes | Yes | | [Cross-device experiments](https://docs.croct.com/explanation/experiment#cross-device-consistency) | Ensure variant stickiness across devices for consistent experiences and reliable results. | No | Yes | Yes | ### Segmentation | Feature | Description | Free | Growth | Scale | |:-----------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------|-----:|-------:|------:| | [User profile targeting](https://docs.croct.com/explanation/audience/examples/user-attributes) | Personalize experiences based on what you know about your audience. | Yes | Yes | Yes | | [Shopping targeting](https://docs.croct.com/explanation/audience/examples/shopping-cart) | Boost sales with personalized shopping experiences based on cart activities. | Yes | Yes | Yes | | [Campaign targeting](https://docs.croct.com/explanation/audience/examples/marketing-campaign) | Maximize marketing investments by optimizing experiences for your campaigns. | Yes | Yes | Yes | | [Session targeting](https://docs.croct.com/explanation/audience/examples/session-activity) | Leverage real-time session insights and activity to improve experiences. | Yes | Yes | Yes | | [Technology targeting](https://docs.croct.com/explanation/audience/examples/technology) | Tailor content based on your visitors' technology profile. | Yes | Yes | Yes | | [Geolocation targeting](https://docs.croct.com/explanation/audience/examples/geolocation) | Deliver regionally relevant content and offers based on visitor's location. | Yes | Yes | Yes | | [Event-based targeting](https://docs.croct.com/reference/cql/expressions/events/overview) | Use historical events and interactions to drive today's personalization. | No | No | Yes | | [Audience estimation](https://docs.croct.com/explanation/audience/estimation) | Estimate your potential audience size based on a given criterion. | No | Yes | Yes | ### Customer data | Feature | Description | Free | Growth | Scale | |:--------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------|------:|--------:|--------:| | [Profile explorer](https://docs.croct.com/explanation/user-profiles/introduction) | Explore individual profiles and the events timeline to understand user behavior. | 1 day | 30 days | 60 days | | [Data retention](https://docs.croct.com/explanation/organization/data-retention) | Choose the data retention period that aligns with your business and compliance needs. | No | Add-on | Add-on | | User profile schema | Guarantee data consistency and integrity across user profiles with automatic validations. | No | Add-on | Add-on | | User profile sync | Keep user profiles in sync for seamless cross-channel experiences. | No | Add-on | Add-on | | [Identity resolution](https://docs.croct.com/explanation/user-profiles/identity-resolution) | Connect separate profiles and keep their data in sync. | No | Add-on | Add-on | ### Analytics | Feature | Description | Free | Growth | Scale | |:-----------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------|-----:|-------:|------:| | [Workspace dashboard](https://docs.croct.com/reference/analytics/workspace/overview) | Capture the big picture with a holistic view of metrics across all applications. | Yes | Yes | Yes | | [Application dashboard](https://docs.croct.com/reference/analytics/application/overview) | Get real-time insights into your application's performance and user engagement. | Yes | Yes | Yes | | [Experience dashboard](https://docs.croct.com/reference/analytics/experience/overview) | Keep track of your experience performance and uncover valuable insights for optimization. | Yes | Yes | Yes | ### Data protection | Feature | Description | Free | Growth | Scale | |:------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------|-----:|-------:|------:| | [Token authentication](https://docs.croct.com/explanation/application/signed-tokens) | Add an extra layer of security to strengthen privacy in every experience. | Yes | Yes | Yes | | [Cross-origin security control](https://docs.croct.com/explanation/application/trusted-origins) | Shield your data and content from unwanted access with cross-origin security controls. | Yes | Yes | Yes | | Application environments | Establish security boundaries between development and production environments. | Yes | Yes | Yes | ### APIs | Feature | Description | Free | Growth | Scale | |:----------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------|-----:|-------:|-------:| | [Content API](https://docs.croct.com/reference/api/service/content/quick-start) | Fetch both static and personalized content programmatically. | Yes | Yes | Yes | | [Evaluation API](https://docs.croct.com/reference/api/service/evaluation/quick-start) | Evaluate queries in real time for programmatic personalization. | Yes | Yes | Yes | | [Event tracking API](https://docs.croct.com/reference/api/service/event-tracking/quick-start) | Track user events, interactions, and behaviors to build comprehensive user profiles. | Yes | Yes | Yes | | [Data export API](https://docs.croct.com/reference/api/service/data-export/quick-start) | Easily export your data for further analysis or custom integrations. | No | Add-on | Add-on | ### Integrations | Feature | Description | Free | Growth | Scale | |:------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------------|-----:|-------:|------:| | [B2B firmographic data enrichment](https://docs.croct.com/immersion/integrations/firmographics) | Enrich profiles with company data from 6sense, Demandbase, ZoomInfo, and Clearbit. | Yes | Yes | Yes | | [Headless commerce](https://docs.croct.com/immersion/integrations/ecommerce) | Connect your storefront with Shopify, Magento, Salesforce Commerce, and VTEX. | Yes | Yes | Yes | | [Third-party analytics tools](https://docs.croct.com/immersion/integrations/analytics) | Connect your data with Google Analytics, Amplitude, and Mixpanel. | Yes | Yes | Yes | | [User behavior tools](https://docs.croct.com/immersion/integrations/analytics) | Integrate session insights from Clarity, Hotjar, and Crazy Egg. | Yes | Yes | Yes | | [Vercel](https://vercel.com/marketplace/croct) | Deploy and personalize your experiences seamlessly with Vercel. | Yes | Yes | Yes | | [Storyblok CMS](https://docs.croct.com/immersion/integrations/cms/storyblok/integration) | Personalize content directly within the Storyblok CMS. | No | No | Yes | ### Support | Feature | Description | Free | Growth | Scale | |:----------------------------------------|:-------------------------------------------------------------------------------------------------------------|-----:|-----------:|-----------:| | [Documentation](https://docs.croct.com) | Learn everything you need to know to get started in no time. | Yes | Yes | Yes | | Community and email support | Reach out via email and join our community for shared knowledge, insights, and support whenever you need it. | Yes | Yes | Yes | | Assisted onboarding | Fast-track your onboarding with dedicated specialist support. | No | 2 meetings | 4 meetings | | Chat support | Connect with our team of specialists via chat for realtime assistance during business hours. | No | Yes | Yes | | Account expert | Leverage industry insights and product expertise to maximize your success. | No | No | Yes | ## Add-ons - [Localization](https://docs.croct.com/explanation/slot#localization): Unlock locale-specific content management for default content, personalized experiences, and A/B tests. - [Scheduling](https://docs.croct.com/explanation/experience/scheduling): Allow to plan ahead and automate content delivery. - [Data retention](https://docs.croct.com/explanation/organization/data-retention): Let customers choose the data retention period that aligns with their business and compliance needs. - User profile schema: Guarantee data consistency and integrity across user profiles with automatic validations. - User profile sync: Keep user profiles in sync for seamless cross-channel experiences. - [Identity resolution](https://docs.croct.com/explanation/user-profiles/identity-resolution): Allow connecting separate profiles and keep their data in sync. - [Data export API](https://docs.croct.com/reference/api/service/data-export/quick-start): Let customers easily export event, session, and user profile data without sampling for further analysis or custom integrations. ## Enterprise For teams with larger volumes, Croct offers custom Enterprise plans with volume-based pricing, premium support, SLA guarantees, and flexible data retention. ## 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 ### Is there a free plan? 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. The plan comparison above lists the features included in the free plan and the options for higher user volumes. ### What is monthly active users (MAU)? The number of unique users who interact with a website in a month, regardless of whether a personalized experience or active experiment impacts them. Each plan has an MAU quota, with the flexibility to purchase additional volume as needed. ### Do web crawlers and bots count toward my MAU limit? By default, known bots and web crawlers do not count toward the MAU limit on paid plans, because the [bot filtering feature](https://docs.croct.com/explanation/workspace/bot-exclusion) excludes that traffic from personalized experiences and experiments. Disable bot filtering and bots are treated as regular users, counting toward the MAU quota. ### What happens the website hits the MAU limit? Customers can upgrade the plan to accommodate more users, enable the Pay As You Grow (PAYG) feature on the current plan to cover the extra users, or do nothing. If they do nothing, the service becomes unavailable to their application, meaning it stops tracking events and delivering personalization, default content, and A/B testing variants, until they adjust the plan or it renews for the following month. The admin panel stays accessible the whole time. ### What is a slot, and how does it work as a content placeholder? A [slot](https://docs.croct.com/explanation/slot) is a context-specific placeholder in an application that defines where content goes and what type of content can be displayed. While [components](https://docs.croct.com/explanation/component) are the reusable building blocks (like a hero section), slots are the specific placeholders (like a home hero) where those components are rendered. ### Are there limits on the number of running experiences or experiments? Quotas vary by plan. The plan comparison above lists the quotas for each plan. ### What if customers need more features or want to increase their quotas? They can upgrade to a higher tier that provides the features and user volume you need. Alternatively, if they have specific needs beyond the standard plans, they can [contact sales](/contact/sales) to discuss add-ons or explore custom plans that may better fit their situation. ### What are the benefits of choosing an annual plan? Annual plans often come with special pricing and financial benefits compared to monthly subscriptions. ### What payment methods are available? Currently, only credit card payments are accepted for subscriptions. If customers have specific payment needs or require a different method, they can [contact sales](/contact/sales) to explore alternative options. ### Can customers switch their plan at any time? They can upgrade or downgrade at any time on all standard plans. Custom plans may have different terms and conditions. Note that switching from an annual plan to a monthly plan may have limitations, as annual plans often include special offers tied to the commitment. ### Can customers cancel their subscription at any time? They can cancel at any time unless they have a special agreement or commitment, such as a custom plan or negotiated contract, which may have specific cancellation terms. ### Is there a partner program if agencies want to manage Croct for multiple clients? Yes, there is a [partner program](https://mkt.croct.com/page/agencies) designed for agencies that manage multiple clients. It is structured to help them shift from one-off projects to recurring revenue by offering conversion rate optimization services. --- Source: /segmentation.md # Segmentation **Audience segmentation means evaluating who a visitor is against your own rules, on the server, before the page is rendered.** A CDP tells you what happened. Croct lets you act while it is happening. Audiences are evaluated in real time, including on the first pageview, and they are available to content and experiments the moment a visitor qualifies. ## How it works Audiences are written in CQL, an English-like query language, so a segment reads as a sentence: `user is returning and location's city's name is "New York"`. They combine real-time behavior, profile traits, and historical data, with more than 100 signals available out of the box across events, location, marketing, session, shopping, user and web technology, plus any custom attribute you define. As you build a segment, live estimates show its volume, so you can tell whether an audience is worth targeting before you write the content for it. Evaluation runs on the server with latencies under 40 milliseconds, which means segmentation happens before the response is sent rather than after the page has painted. ## Features - **Real-time evaluation.** A visitor enters an audience the moment they qualify, including on the first pageview. - **Server-side evaluation.** Segments resolve before render, so there is no flash of the wrong content. - **CQL.** Segments written in readable English, and soon in a query builder. - **100+ built-in signals.** Behavior, location, campaign, session, device, shopping, and profile traits, with no instrumentation. - **Audience estimator.** Live volume estimates while you build. - **Anonymous activation.** Intent predicted from live signals, before anyone identifies themselves. - **Custom attributes.** Your own traits alongside the built-in signals. - **AND/OR logic.** Chain conditions to express the segment you actually mean. - **Recency and frequency.** Narrow a segment by how recently and how often something happened. - **Segmented analytics.** Every dashboard readable by audience. - **Data export.** Profiles and audiences flow to your warehouse or any tool you run. - **Privacy controls.** Rules enforced at the platform level rather than page by page. ## Building with it Segmentation is part of the platform, so there is no CDP to buy, connect, or keep in sync. Audiences created here are immediately usable by personalization and by segmented experiments. 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 ### What criteria can I use to build user segments in Croct? You can build segments using a [wide variety of criteria](https://docs.croct.com/explanation/audience/popular-audiences), including marketing campaign engagement, geographic location, technology and devices used, session data, declared or inferred interests, specific user activities, completed goals, navigation history, shopping cart status, past order history, and much more. ### What types of signals can be used to build audiences? We provide over 100 out-of-the-box [signals](https://docs.croct.com/reference/cql/context) to build high-impact segments. These include behavioral events, geolocation data, marketing campaign sources, session activity, shopping actions, web technology, custom profile attributes, and real-time intent inferred from anonymous signals. ### Do I need a CDP to segment visitors? No. Real-time profiles, segmentation, and data unification are built in, so there is no external customer data platform to buy, connect, or keep in sync, and no historical data needed to get started. You can still connect a CDP to enrich profiles if you already run one. ### Are segments evaluated in real-time as users navigate my site? Yes. We [evaluate audience criteria](https://docs.croct.com/explanation/audience/introduction) against a user's current context, including the pages they visit and their immediate behavior, as they interact with your application. This real-time profiling allows you to trigger immediate actions, and the engine can perform evaluations with latencies under 40 milliseconds. ### Are audiences evaluated on the server or in the browser? On the server. Audience conditions resolve before the response is rendered, which means personalized content arrives in the first HTML response with no flicker and no client-side round trip. Segmentation can also depend on data that never reaches the browser. ### Does it work on anonymous visitors? Yes. Audiences are built from live behavioral signals such as campaign source, location, and session activity, so they apply from the first pageview, before a visitor identifies themselves. ### Can I build segments using AND/OR logic? Yes, you can build highly specific segments by [combining multiple criteria](https://docs.croct.com/explanation/audience/examples/multiple-conditions), mixing and matching events and attributes to fit your exact business goals. Using logical operators like `and`, you can easily chain conditions together, such as `location's city's name is "New York" and cart's subtotal is greater than 100`. ### Can I specify recency and frequency while building segments? Yes, in the Scale plan, you can use [event-based segmentation](https://docs.croct.com/reference/cql/expressions/events/overview) to narrow your audience criteria by specifying recency and frequency, addressing identified gaps, and creating highly specific segments. ### What is the CQL, and how do I use it to define audiences? [Contextual Query Language (CQL)](https://docs.croct.com/reference/cql/introduction) is an English-based query language tailored for personalization and experimentation. It acts as an abstraction layer that turns complex data points into simple, natural-language business rules. You use it to unambiguously define audience criteria, such as `user is returning`, so that both technical and non-technical team members can target specific users without writing complex code. ### Can I segment on data Croct doesn't collect? Yes. Pass your own attributes, such as subscription plan, quota usage, or account age, as [context](https://docs.croct.com/reference/cql/context) at request time and reference them in your audience conditions alongside the built-in signals. ### How much historical data do I need to start? None. Audiences work from the first pageview, using live signals rather than accumulated history. ### Can I estimate the size and relevance of an audience before launching an experience? Yes, you can. We feature an audience estimator that provides real-time audience volume estimates as you build your segments. This helps you validate the size and relevance of an audience before investing time in execution, allowing you to prioritize the segments that drive the most results. ### How do segments impact my dashboards? Segments power our segmented [analytics](https://docs.croct.com/reference/analytics), allowing you to break down insights by audience behavior. This lets you drill down into any metric by audience to uncover hidden opportunities and see exactly which pages, products, or features drive each segment's engagement. ### Is there a limit to how many segments I can create? Yes, it varies by plan (free, growth, or scale). In addition to the plan quota, you can buy extra audience packages as add-ons. ### 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. --- Source: /solutions/acquisition.md # Customer acquisition Generic messaging converts generically. Croct reads what a visitor is doing while they are still anonymous and adapts the page to it, so acquisition improves without raising spend. ## The problem Acquisition strategies rarely target one audience. They target several, through several channels, and the website answers all of them with the same words. The result is a page that speaks to nobody in particular: value that is hard to place, offers that do not match the intent that brought the visitor in, and a cost per acquisition that climbs while conversion sits still. ## How Croct solves it Croct builds a profile from the visitor's behavior, including the first pageview, and resolves the page against it on the server. The hero, the offer, the proof and the call to action can each vary by audience, so the same page answers a returning enterprise evaluator and a first-time visitor from a paid campaign differently. Marketing changes any of it without a release. ## Outcomes VR, personalizing campaign pages by audience instead of building one page per campaign, increased conversion rate by 70%. Their team wanted every campaign's page to match its ad without maintaining thirty separate pages, which is exactly what audiences plus slots replace. Beyond that, the pattern holds: fewer landing pages to maintain, messages that match the intent that brought the visitor in, and experiments that tell you which message did the work. ## 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. ## 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 ### Does this work on anonymous traffic? Yes. Profiles are built from behavior, so audiences work before a visitor identifies themselves, including on the first pageview. ### How long before the first experience is live? Hours rather than months. Setup is one command, and experiences are built in the interface afterwards. ### 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. --- Source: /solutions/geolocation.md # 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. --- Source: /solutions/lead-generation.md # Lead generation A funnel that serves several personas with one message leaks. Croct adapts the site to the persona in front of it, including anonymous visitors resolved to their company, so more of the traffic you already have becomes qualified pipeline. ## The problem Lead generation usually spans multiple personas and multiple industries, and the website speaks to the average of them. The lead magnet that would convert an enterprise buyer is buried under copy written for self-serve users, positioning reads as generic, and cost per lead rises while quality falls. ## How Croct solves it Croct builds a profile from behavior and from the firmographic data your account intelligence tools already resolve. Audiences follow from that: industry, company size, buying stage, campaign, behavior. The site then highlights the lead magnet, the proof and the form that fit the persona, decided on the server. Forms themselves can be part of the experiment. ## Outcomes More of your organic and paid traffic converts, without buying more of it. Firmographic personalization means target accounts see positioning written for them, and the forms they meet can be shorter or longer depending on what you already know about them. ## 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. - **[Firmographic integrations](/integrations).** Your account intelligence provider identifies the account, and Croct acts on it in real time. ## 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 ### Does this work for account-based marketing? Yes. Firmographic data from your account intelligence provider lands in the profile, so audiences can target industry, company size or named accounts. ### Can I personalize the forms themselves? Yes. With [HubSpot](/integrations/hubspot), the form ID lives in a slot, so an experiment or an experience decides which form each visitor sees. ### 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. --- Source: /solutions/ppc-paid-search-optimization.md # Paid search optimization The ad matches the search term. The landing page usually does not, and the pages after it never do. Croct carries the campaign, the ad group and the search term into the experience, so the journey stays relevant past the first click. ## The problem Paid search buys intent, and generic pages waste it. The ad promises something specific, the page answers something general, and the mismatch shows up as bounce. Visitors who do not convert on the first visit come back later to a site that has forgotten why they came, and cost per click climbs to cover the gap. ## How Croct solves it Campaign, ad group and search term are available in the profile while the visitor is still browsing, from the first pageview. Audiences built on them personalize the whole journey rather than one landing page, and the same signals persist when the visitor returns, so a second visit continues where the first left off. Building a page per keyword stops being necessary. ## Outcomes Higher conversion from the same spend, one page serving many keywords instead of many pages serving one each, and a return visit that still reflects the campaign that earned it. ## 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. ## 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 ### Do I need a landing page per keyword? No. Audiences on campaign, ad group and search term let a single page adapt to many keywords. ### Does it work for returning visitors? Yes. The signals persist in the profile, so a visitor who converts on a later visit still gets the experience their original search earned. ### 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. --- Source: /solutions/revenue-optimization.md # 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, 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 ### 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. --- Source: /solutions/social-ads-optimization.md # Paid social optimization Paid social targets precisely and then sends everyone to the same page. Croct carries the campaign, the audience and the ad content into the experience, so the granular targeting you paid for survives the click. ## The problem Social platforms let you split an audience finely, and the website collapses it back into one. The creative sets an expectation the page does not meet, first-visit conversion is rare by nature of the channel, and the generic experience gives returning visitors no reason to finish what they started. ## How Croct solves it Campaign, audience and ad content land in the profile on the first pageview. Audiences built on them let each creative continue into a matching page, and the whole journey after it, decided on the server. New creatives get new experiences from the marketing team, without a release. ## Outcomes Higher return on ad spend from the same budget, creative and landing experience that stay in sync, and a measurable read on which combination actually converts. ## 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. ## 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 ### Which signals can I target? Campaign, audience and ad content, alongside behavior, location and anything else in the profile. ### Do I need a new page per creative? No. One page adapts per audience, so a new creative needs a new experience rather than a new page. ### 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. --- Source: /user-profiles.md # User profiles **A user profile is a live record of everything a visitor has done, kept on the server and available to audiences, experiences, and experiments at request time.** Every click has a story behind it. Croct keeps a profile for each visitor, connects their anonymous history to their identified one, and makes the whole timeline queryable. Profiles are built in, so behavioral segmentation does not require buying, connecting, and maintaining a separate customer data platform. ## How it works Events land on the profile as they happen, from your application, your commerce platform, your data layer, and your own systems. When a visitor identifies themselves, identity resolution merges the anonymous history into the identified profile, so nothing about their journey is lost. Audiences and content read those profiles at request time. Because evaluation happens on the server, profile data drives the experience without being exposed to the browser. ## Features - **Visitor profiles.** Live profiles for anonymous first-timers and returning buyers alike. - **No CDP required.** Events, traits, and IDs are centralized automatically, with no external data platform to integrate. - **Linked journeys.** Anonymous and identified history merged into one continuous story. - **Events timeline.** The full sequence of what someone did, across visits. - **User attributes.** A readable snapshot of statistical, behavioral, and, optionally, personal traits. - **Real-time events.** Engagement, conversion, shopping, web, session, and custom events out of the box. - **Live sessions.** See who is active right now, which makes tracking and debugging concrete. - **Profile schemas.** Typed profiles, so what you store stays consistent. - **Identity resolution.** Fragmented identities are merged and kept in sync with external tools. - **Cross-device consistency.** An identified visitor gets the same content and variants everywhere. - **Custom attributes.** Model the traits your business actually segments on. - **Data retention and export.** Your data, exportable through CSV or the export API. ## Building with it Profiles are populated automatically by the SDKs and the integrations, so most teams write no tracking code. Custom events and attributes are available when you want to model something specific to your business. 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 does Croct build unified user profiles? We centralize events, traits, and IDs into live, comprehensive [visitor profiles](https://docs.croct.com/explanation/user-profiles/introduction). We use an identity resolution process to automatically connect fragmented data from different contexts, such as browsing anonymously on a phone and later logging in on a laptop, keeping the data in sync to provide a complete, unified view of the visitor. ### Do I need a CDP to use profiles and segmentation? No. Most personalization tools and headless CMS platforms leave visitor data to an external customer data platform, which means buying and maintaining a second system before personalization does anything. Croct centralizes events, traits, and IDs into live profiles on its own, with no CDP, external integration, or historical data required to get started. ### Can I bring in my own first-party data from my CRM or CDP to enrich profiles? Yes, you can easily connect your stack and bring in data from your analytics, CMS, CDP, or other external tools using simple integrations. ### What kind of attributes are stored in a user profile? [Attributes](https://docs.croct.com/explanation/user-profiles/attributes) store personal details, behavioral signals, and collected statistics. Out-of-the-box, it includes real-time tags indicating if the visitor is a new, returning, or longtime user, whether they are a buyer, and includes available work and contact information. You can also track and store custom attributes tailored to your specific business needs. ### What is the timeline view, and what insights does it provide about a user's journey? The [events timeline](https://docs.croct.com/explanation/user-profiles/timeline) is a chronological view of a user's sessions and all the events that occurred within them. It provides deep insights into how a user navigates your applications over time, the specific actions they take, and how their behavior and engagement evolve across different visits. ### Can I see live events in the timeline as the visitor browses? Yes. For live sessions, a marker sits on the most recent event with a pulsing dot, indicating the session is currently active and updating in real-time. ### Is cross-device tracking supported for authenticated users? Yes. For identified (authenticated) users, we use their persistent user ID to ensure cross-device consistency. This means they will receive the same personalized content and experiment variants whether they are visiting from a desktop, tablet, or mobile phone. We also track concurrent sessions when a user is active on multiple devices simultaneously. ### What is identity resolution, and how does it connect anonymous and identified data? [Identity resolution](https://docs.croct.com/explanation/user-profiles/identity-resolution) is the process that connects separate profiles for the same visitor and automatically keeps their attributes in sync. When an anonymous user identifies themselves (such as by logging in or signing up), the data previously collected on their anonymous profile is merged into their newly identified profile to preserve the continuity of their journey. For privacy reasons, the reverse never happens; personal data captured on an identified profile never flows back into an anonymous profile. ### Do I have to instrument every event by hand? No. The SDKs and integrations track the common events automatically, so most teams write no tracking code. Custom events and attributes are there when you need to model something specific to your business. ### Can I use profile data that Croct doesn't collect? Yes. You can pass your own attributes, such as subscription plan, quota usage, or account age, as [context](https://docs.croct.com/reference/cql/context) at request time and reference them in audience conditions. Because evaluation happens on the server, that data drives the experience without ever reaching the browser. ### How long is user profile data retained? The [retention period](https://docs.croct.com/explanation/organization/data-retention) varies by plan. On the Scale plan, however, you can control exactly how long data is stored using add-ons. This flexibility lets you retain data only as long as needed to meet your specific business goals and compliance standards. ### How does Croct handle data privacy and compliance? We're privacy-first, so we let you enforce privacy rules while still activating the data you need for performance. We offer flexible data retention controls to meet legal compliance standards and maintain strict privacy boundaries, ensuring that personal data from identified profiles is never mixed with anonymous profiles. ### Can I export visitor profiles through APIs? Yes, we provide a [Data Export API](https://docs.croct.com/reference/api/service/data-export/quick-start) that lets you seamlessly export user profiles, sessions, and events to your data lake, integrations, or custom workflows. CSV export is also available on paid plans. ### 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.