Skip to main content
Kameleoon’s Feature Experimentation capabilities enable you to manage feature rollouts, control access, and run experiments using feature flags across web and mobile applications. This guide walks you through the basic steps of installing and configuring Kameleoon Feature Experimentation

​
Create a project in Kameleoon

Before you begin, create a new project in your Kameleoon account. A project represents your web app, mobile app, or both, depending on whether you want to manage them under a single project. From the feature flag creation page, you can easily add any environments (like production, staging, or development) that you use in your development workflow. To create the project:
  1. Click Admin > Projects, then click New project.
  2. Select Feature Experimentation, or All campaign types if you also run web campaigns from the same project. After you create the project, you can’t change its type.
  3. If you selected Feature Experimentation, select Web / Backend, Mobile app, or both, then click Next.
  4. Enter the project’s main information, then click Next. A project that only has the Mobile app platform has no Main project domain field, and it requires a project name.
    • For All campaign types, the setup form also includes the Installation method and Technical configuration steps before the checklist.
  5. In the Checklist step, open the Install the SDK task to see the Project sitecode. Click Mark as completed, then click Complete setup when you finish your tasks.
For the full list of options, see Create a project. Each project has a sitecode, a unique identifier you need to initialize the Kameleoon SDK. The Install the SDK task shows it, and the Sitecode column of the Projects page lists it.
If you’re running experiments across multiple platforms (web and mobile), you can use the same sitecode for all SDKs to share flags and avoid duplication.
Don’t create a separate project for each environment (development, staging, production). Use a single project and add your environments within it instead. Creating separate projects per environment means you can’t share goals and targeting rules across your deployment pipeline. For details, see Manage environments.

​
Install an SDK

Kameleoon provides a variety of SDKs for different environments:
  • Server-side SDKs: Java, Node.js, Python, Go, PHP, C#, Ruby
  • Mobile SDKs: Android, Flutter, iOS, React Native
  • Client-side SDKs: JavaScript, React
  • Advanced SDK tools: Edge toolkits, OpenFeature compatibility, SDK API (see API credentials)
Select the SDK appropriate for your stack. You’ll find installation instructions in Kameleoon’s developer documentation. To install an SDK, typically you will:
  • Provide credentials (client_id and client_secret) via a configuration file available in server-side SDKs. To learn how to retrieve API credentials, refer to this article.
  • Provide your project’s sitecode for initialization.
  • Specify the environment (for example, production, staging) in the SDK configuration to match your development workflow.
  • Choose between polling and streaming modes, which determine how the SDK fetches flag updates, either by regularly checking for changes (polling) or receiving them in real time (streaming). Note that streaming is a premium option.
You should check the SDK compatibility table to see which features and methods are available for each SDK. Since Kameleoon regularly adds new features and support for additional languages, the minimum required version for certain features may vary by language. The compatibility table shows which features each SDK supports and the version needed to implement them in your frontend or backend. For a full version history, refer to the changelog in the SDK GitHub repository. You should subscribe to email notifications to stay updated on new releases.

​
Start using feature flags

With the SDK initialized, you can now:
  • Create feature flags in the Kameleoon app.
  • Roll out features progressively using targeting rules, percentage rollouts, or user attributes.
  • Run experiments on feature flag variations and analyze their impact.
For more information on feature flags, refer to these articles: