Revert predef variations docs

website/docs/advanced/migration-from-launchdarkly-translation.mdx

@@ -349,7 +349,7 @@ we are happy to raise your limits temporarily so you can fully explore the produ
         There is no way to emulate this behavior in ConfigCat, so a placeholder value is used as follows:
         <ul>
           <li>boolean flag: `false`</li>
-          <li>string flag: `"_"`</li>
+          <li>string flag: `""` (empty string)</li>
           <li>json flag: `"null"`</li>
           <li>number flag: 0</li>
         </ul>
@@ -718,39 +718,6 @@ we are happy to raise your limits temporarily so you can fully explore the produ
         Comma is replaced with semicolon in comparison value list items.
       </td>
     </tr>
-
-    <tr id="translation-issue-T028">
-      <td>T028</td>
-      <td>🔴&nbsp;HIGH</td>
-      <td>
-        A feature flag variation value was changed.
-      </td>
-      <td>
-        LaunchDarkly allows variation values that are not valid in ConfigCat. More specifically, the empty string in the
-        case of string feature flags.
-      </td>
-      <td>
-        Problematic variation values are changed into valid ConfigCat values, and if necessary, they are made unique by
-        adding a number suffix.
-      </td>
-    </tr>
-
-    <tr id="translation-issue-T029">
-      <td>T029</td>
-      <td>🔵&nbsp;LOW</td>
-      <td>
-        A feature flag variation name was changed.
-      </td>
-      <td>
-        LaunchDarkly may allow longer variation names than ConfigCat. Also, LaunchDarkly enforces looser rules than
-        ConfigCat with regard to variation name uniqueness.
-      </td>
-      <td>
-        Names that are too long are truncated at the maximum length. Then the effective name (the truncated name or,
-        if no name is specified, the variation value) is checked for conflicts, and if necessary, it is made unique
-        by adding a number suffix.
-      </td>
-    </tr>
   </tbody>
 </table>
 

website/docs/integrations/amplitude.mdx

@@ -253,8 +253,6 @@ you have to send the `user_id` property as well to identify your user. You can u
 :::note
 For Text feature flags with lengthy values (e.g., JSON), send the `variationId` instead of the `value` as the `variant` to Amplitude.
 The `variationId` is a hashed version of the feature flag value, accessible on the ConfigCat Dashboard by enabling the _Show VariationIDs to support A/B testing_ setting. Learn more [here](https://app.configcat.com/product/preferences).
-
-For more information about Variation IDs, see [Variation ID for analytics](/advanced/variation-id-for-analytics).
 :::
 
 4. Deploy your application and wait for feature flag evaluations to happen so Experiments in Amplitude could be populated.

website/docs/integrations/google-analytics.mdx

@@ -76,8 +76,6 @@ While our documentation primarily provides code examples for JavaScript-based SD
 
 :::note
 For Text feature flags with lengthy values (e.g., JSON), send the `variationId` instead of the `value` as the `exp_variant_string` to Google Analytics. The `variationId` is a hashed version of the feature flag value, accessible on the ConfigCat Dashboard by enabling the _Show VariationIDs to support A/B testing_ setting. Learn more [here](https://app.configcat.com/product/preferences).
-
-For more information about Variation IDs, see [Variation ID for analytics](/advanced/variation-id-for-analytics).
 :::
 
 4. **Deploy your application** and wait for feature flag evaluations to occur. This process might take 1-2 days for the `experience_impression` events to populate in Google Analytics.

website/docs/integrations/mixpanel.mdx

@@ -259,8 +259,6 @@ you have to send the [distinct_id](https://docs.mixpanel.com/docs/tracking-metho
 :::note
 For Text feature flags with lengthy values (e.g., JSON), send the `variationId` instead of the `value` as the `Variant name` to Mixpanel.
 The `variationId` is a hashed version of the feature flag value, accessible on the ConfigCat Dashboard by enabling the _Show VariationIDs to support A/B testing_ setting. Learn more [here](https://app.configcat.com/product/preferences).
-
-For more information about Variation IDs, see [Variation ID for analytics](/advanced/variation-id-for-analytics).
 :::
 
 4. Deploy your application and wait for feature flag evaluations to happen so Experiments in Mixpanel could be populated.

website/docs/integrations/segment.mdx

@@ -421,8 +421,6 @@ you can integrate with other languages by sending an event to Twilio Segment wit
 :::note
 For Text feature flags with lengthy values (e.g., JSON), send the `variationId` instead of the `value` as the `value` to Twilio Segment.
 The `variationId` is a hashed version of the feature flag value, accessible on the ConfigCat Dashboard by enabling the _Show VariationIDs to support A/B testing_ setting. Learn more [here](https://app.configcat.com/product/preferences).
-
-For more information about Variation IDs, see [Variation ID for analytics](/advanced/variation-id-for-analytics).
 :::
 
 4. Deploy your application and wait for feature flag evaluations to happen so feature flag evaluation events can be sent to Twilio Segment.

website/docs/main-concepts.mdx

@@ -28,22 +28,6 @@ A _Feature Flag_ is a _Setting_ of type Bool.
 | Whole Number   | Integer      | Any whole number within the range of `Int32`.                                      |
 | Decimal Number | Double       | Any decimal number within the range of `double`.                                   |
 
-### Free-form values vs predefined variations
-
-ConfigCat supports two value-modes for feature flags:
-- **Free-form values**: Allows you to enter a feature flag's exact value each time you set it. Best for simple, one-off configurations or quick experiments.
-  <p>
-    <img src="/docs/assets/predefined-variations/free-form-create_192dpi.png" alt="Clone feature flag" width="1366" height="768" decoding="async" loading="lazy" />
-  </p>
-- **Predefined Variations**: Allows you to define a set of reusable values upfront when creating a feature flag. These variations can then be selected from a dropdown when setting up flag rules. Choose this mode to ensure consistency across rules, prevent typos in complex values (like JSON configurations), and provide self-documenting configurations for your team.
-  <p>
-    <img src="/docs/assets/predefined-variations/predefined-variations-create_192dpi.png" alt="Clone feature flag" width="1366" height="768" decoding="async" loading="lazy" />
-  </p>
-
-:::tip
-Learn more about [predefined variations](/advanced/predefined-variations), including when to use this value-mode, how to convert between the two value-modes, and best practices.
-:::
-
 ## Config
 
 A _Config_ is a collection of _Settings_. _Configs_ help you organize settings around topics, or around your software components. A _Config_ is like an online version of a traditional config file.

website/docs/news.mdx

@@ -10,38 +10,6 @@ Here, you'll find all the latest updates, enhancements, and new features we've a
 
 {/* This page must be in sync with the news page on the Dashboard: https://github.com/configcat/app/blob/master/src/app/home-module/news/news.component.html */}
 
-## Predefined variations are here!
-
-#### Feb 19, 2026
-
-You asked for a structured way to reuse feature flag values, so we built **predefined variations**.
-
-Instead of typing the same values again and again, define them once.
-Then select them from a dropdown when you build targeting rules.
-
-Small change. Big difference.
-
-This helps teams:
-- Keep values consistent across environments and rules
-- Prevent typos and invalid values
-- Reuse complex values such as JSON objects
-- Add clear labels and hints for teammates
-
-You stay in control.
-
-You can also convert existing flags from free-form values to predefined variations, and back, without breaking your applications in production.
-
-Predefined variations are available in all plans.
-They extend ConfigCat's powerful targeting capabilities without adding complexity.
-
-Learn more in the [Predefined Variations documentation](./advanced/predefined-variations.mdx).
-
-<p>
-    <img src="/docs/assets/predefined-variations/usage_192dpi.png" alt="Predefined variations" width="1366" height="768" decoding="async" loading="lazy" />
-</p>
-
----
-
 ## Feature flag evaluation in GitHub Actions
 
 #### Feb 2, 2026

website/sidebars.ts

@@ -35,7 +35,6 @@ const docs: SidebarConfig = [
         ],
       },
       'advanced/data-governance',
-      'advanced/predefined-variations',
       {
         label: 'Targeting',
         type: 'category',
@@ -59,7 +58,6 @@ const docs: SidebarConfig = [
           'targeting/feature-flag-evaluation',
         ],
       },
-      'advanced/variation-id-for-analytics',
       'advanced/caching',
       'advanced/troubleshooting',
       'zombie-flags',

website/src/pages/index.js

@@ -29,8 +29,6 @@ const features = [
     links: [
       { url: 'api/reference/configcat-public-management-api', title: 'Public Management API' },
       { url: 'advanced/data-governance', title: 'Data Governance - CDN' },
-      { url: 'advanced/predefined-variations', title: 'Predefined Variations' },
-      { url: 'advanced/variation-id-for-analytics', title: 'Variation ID for analytics' },
       { url: 'advanced/caching', title: 'Polling modes & Caching' },
       {
         url: 'advanced/team-management/team-management-basics',