ibexa · julitafalcondusza · Jul 27, 2026
diff --git a/docs/administration/admin_panel/segments_admin_panel.md b/docs/administration/admin_panel/segments_admin_panel.md
@@ -6,7 +6,7 @@ edition: experience
 # Segments
 
 You can use segments to display specific content to specific [users](users.md).
-They're used out of the box in the Targeting and Dynamic targeting blocks in the page.
+They're used out of the box in the Targeting block in the page.
 
 You can collect segments in segment groups:
 
@@ -16,4 +16,4 @@ Each segment group can contain segments that you can target content for.
 
 ![Segment](admin_panel_segment.png)
 
-You can assign users to segments [through the API](segment_api.md#assigning-users).
+You can assign users to segments [through the API](segment_api.md#assigning-users).
diff --git a/docs/administration/project_organization/architecture.md b/docs/administration/project_organization/architecture.md
@@ -31,5 +31,3 @@ The architecture of [[= product_name =]] is layered and uses clearly defined API
 | [Solr Storage Engine](solr_overview.md)             | Transparent drop-in replacement for the SQL-based Legacy search engine.                                                                                                                        |
 | [IO](file_management.md#native-io-handler)          | The IO API is organized around two types of handlers, both used by the IOService.                                                                                                              |
 | [IO Handler](clustering.md#dfs-io-handler)          | The IO Handler manipulates metadata, making up for the potential inconsistency of network-based filesystems.                                                                                   |
-| [Recommendation](enable_personalization.md)         | Recommendation API.                                                                                                                                                                            |
-| [Personalization server](enable_personalization.md) | Personalization server allows displaying recommendations on the website.                                                                                                                       |
diff --git a/docs/administration/project_organization/bundles.md b/docs/administration/project_organization/bundles.md
@@ -83,15 +83,13 @@ To remove a bundle (either one you created yourself, or an out-of-the-box one th
 |ibexa/migrations|[Migration of repository data](data_migration.md)|
 |[ibexa/oauth2-client](oauth_client.md)|Authenticate user through a third-party OAuth 2 server, integration with [`knpuniversity/oauth2-client-bundle`](https://github.com/knpuniversity/oauth2-client-bundle)|
 |[ibexa/oauth2-server](oauth_server.md)|Allow resource access to OAuth 2 client|
-|ibexa/personalization|Functionality for personalized recommendations|
 |ibexa/product-catalog|Product catalog functionality|
 |ibexa/scheduler|Date-based publishing functionality|
 |ibexa/seo|Search Engine Optimization (SEO) tool|
 |ibexa/taxonomy|Taxonomy functionality|
 |ibexa/tree-builder|Tree builder functionality|
 |ibexa/version-comparison|Enables comparing between two versions of the same field|
 |ibexa/workflow|Collaboration feature that enables you to send content draft to any user for a review or rewriting|
-|ibexa/recommendation-client|Client for connecting with the personalization engine **deprecated**|
 |ibexa/commerce-base-design|Standard design and theme for the shop **deprecated** |
 |ibexa/commerce-checkout|Shop checkout functionality **deprecated** |
 |ibexa/commerce-fieldtypes|Shop-specific field types **deprecated** |

diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md
@@ -67,7 +67,7 @@ In the **Transform & Map** section you transform data and map it to a schema.
 At this point, you can map **email** to **email** and **id** to **integer**  fields to get custom columns.
 
 If you have [extended user data export with custom fields](cdp_data_customization.md#export-additional-user-data), those fields appear as additional columns in this section.
-Make sure to add them to your schema in Raptor so they can be used for segmentation and personalization.
+Make sure to add them to your schema in Raptor so they can be used for segmentation.
 
 Next, select **Create schema based on the downloaded columns**.
 It moves you to Schema Creator.

diff --git a/docs/cdp/cdp_data_customization.md b/docs/cdp/cdp_data_customization.md
@@ -12,7 +12,7 @@ It casts their `Value` object to string, thanks to `\Stringable` implementation.
 ## Export additional user data
 
 You can extend user data exported to CDP by attaching custom information, for example user content fields or user preferences.
-Use it for advanced customer segmentation and personalization in marketing campaigns.
+Use it for advanced customer segmentation in marketing campaigns.
 
 To add custom data to user exports, create a class that extends [`\Ibexa\Contracts\Cdp\Export\User\AbstractUserItemProcessor`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Cdp-Export-User-AbstractUserItemProcessor.html) and implement the `doProcess()` method.
 The base class handles user field validation and provides helper methods for working with user content.

diff --git a/docs/cdp/cdp_guide.md b/docs/cdp/cdp_guide.md
@@ -51,9 +51,9 @@ This approach helps you create a single customer view.
 
 To create a personalized customer experience, you need to group your clients into specified audiences.
 [[= product_name =]] comes with a ready solution - segment groups.
-Segment group information is reused by various [[= product_name =]] functionalities, such as [Personalization](personalization_guide.md) or content targeting.
+Segment group information is reused by various [[= product_name =]] functionalities, such as content targeting.
 
-You can [create a segment group]([[= user_doc =]]/personalization/segment_management/) in the back office of [[= product_name =]].
+You can [create a segment group](segments_admin_panel.md) in the back office of [[= product_name =]].
 It serves as a container for all segments data generated by [[= product_name_cdp =]].
 When you create a segment group, you need to provide its name and identifier.
 Be careful while doing so, as after you create the segment group in the back office and connect it to [[= product_name_cdp =]], you cannot change it in any way, including edit its name.

diff --git a/docs/commerce/transactional_emails/extend_transactional_emails.md b/docs/commerce/transactional_emails/extend_transactional_emails.md
@@ -73,7 +73,7 @@ final class TransactionalMailFactoryEventSubscriber implements EventSubscriberIn
 ## Customize Actito end-user profile
 
 The Actito platform offers many features for customer data collection, including segmentation, subscriptions, and interaction tracking.
-This information can be later user for generating statistics, establishing trends, or used to calculate Personalization recommendations.
+This information can be later user for generating statistics or establishing trends.
 To use these features you need to provide profile data to API requests yourself.
 You do it by means of events that are triggered during profile building.
 
@@ -164,4 +164,4 @@ final class ResolveCampaginEventSubscriber implements EventSubscriberInterface
         $event->setCampaign($campaign);
     }
 }
-```
+```
diff --git a/docs/content_management/pages/page_builder_guide.md b/docs/content_management/pages/page_builder_guide.md
@@ -213,18 +213,14 @@ Additionally, Page Builder offers you a selection of ready-to-use page blocks th
 
 A. **Default** blocks:
 
-- Dynamic targeting - embeds recommended items based on the segment the user belongs to.
-- Personalized - displays a list of content items/products that are recommended to end users when specific scenarios are triggered.
 - Targeting - embeds a content item based on the segment the user belongs to.
 
 B. **PIM** blocks:
 
-- Last purchased - displays a list of products that were recently purchased from PIM.
-- Last viewed - displays a list of products from PIM that were recently viewed.
+- Catalog - displays products from a specific catalog to a selected customer group.
 - Product collection - displays a list of specifically selected products.
-- Recently added - displays a list of products that were recently added to PIM.
+- Product embed - displays a specific product.
 
 C. **Commerce** blocks:
 
-- Bestsellers - displays a list of products from PIM that were recently a bestseller.
 - Orders - displays a list of orders associated with a particular company or individual customer.
diff --git a/docs/customer_management/customer_portal_guide.md b/docs/customer_management/customer_portal_guide.md
@@ -179,6 +179,6 @@ Customer portals help you to automate tasks that otherwise would be done by your
 An additional benefit of customer portals is their availability 24/7.
 Thus, reducing the need to allocate resources to extend working hours or hire more employees.
 
-### Localization and personalization
+### Localization
 
-The use of Page Builder in the Customer Portal creation process enables you to create unique experiences for each business customer based on their location, business type, company, or market they operate on.
+The use of Page Builder in the Customer Portal creation process enables you to create unique experiences for each business customer based on their location, business type, company, or market they operate on.
diff --git a/docs/ibexa_products/editions.md b/docs/ibexa_products/editions.md
@@ -30,7 +30,6 @@ Compare all features available in [[= product_name_headless =]], [[= product_nam
 | [Editorial workflow]([[= user_doc =]]/content_management/workflow_management/editorial_workflow/) | &#10004; | &#10004; | &#10004; |
 | [Digital Asset Management]([[= user_doc =]]/dam/ibexa_dam/) | &#10004; | &#10004; | &#10004; |
 | [Product Information Management]([[= user_doc =]]/pim/pim/) | &#10004; | &#10004; | &#10004; |
-| [Personalization](personalization_guide.md) | &#10004; | &#10004; | &#10004; |
 | [Migrations](managing_migrations.md) | &#10004; | &#10004; | &#10004; |
 | [[[= product_name_connect =]]]([[= connect_doc =]]/) | &#10004; | &#10004; | &#10004; |
 | [OAuth client](oauth_client.md) | &#10004; | &#10004; | &#10004; |

diff --git a/docs/ibexa_products/ibexa_commerce.md b/docs/ibexa_products/ibexa_commerce.md
@@ -94,14 +94,6 @@ With this feature you can also [create email campaigns](transactional_emails.md#
 
 ### Use cases
 
-#### Create personalized shipping experience
-
-Use [Ibexa Personalization]([[= user_doc =]]/personalization/use_cases/#ecommerce) to transform your online stores and give your consumers great buying experiences, from initial contact to post-purchase support.
-No matter how complicated your product or sales process are, you can present your offer in an approachable way.
-Creating engaging and personalized shopping experiences with targeted offers and recommendations helps you boost sales.
-Within eCommerce, product recommendations can assist users in finding the exact item that meets their needs.
-Recommendations can be used to propose related, alternative, or complimentary products to users who are unsure what to buy.
-
 #### Use effective merchandising
 
 Merchandising assists in keeping the consistency of the brand and providing customized product recommendations with captivating visuals and powerful search features.

diff --git a/docs/ibexa_products/ibexa_experience.md b/docs/ibexa_products/ibexa_experience.md
@@ -96,7 +96,6 @@ Using this tool, your customers can change their organization details, invite an
 [Segmentation](https://doc.ibexa.co/en/latest/administration/admin_panel/segments_admin_panel/) allows you to split up the user base.
 By assigning users to segments, you can display specific content to selected visitors and tailor the content that they can see.
 One of the tools that you can use right out of the box is the Targeting block that is available in the Page Builder.
-Segmentation is also useful with the [Personalization](personalization_guide.md).
 You can assign users to different recommendation groups and create advanced logic with operators to provide your audience with the best recommendations.
 
 ![Segments](segments.png)

diff --git a/docs/ibexa_products/ibexa_headless.md b/docs/ibexa_products/ibexa_headless.md
@@ -109,8 +109,6 @@ On top of this strong core, [[= product_name_headless =]] brings tools to increa
 
 [[= product_name_headless =]] is a complete Digital Experience Platform (DXP), which comes with the following components to enhance user's journey:
 
-- [Personalization](personalization_guide.md) engine, which allows you to recommend content to end users according to their behavior,
-  or, when authenticated, by matching with their segment/group.
 - Content scheduler, which allows you to establish the future of the content and use events to have a living front application, even when the editorial team is absent or reduced.
 This way, visitors can discover new content at midnight, during weekends or vacations.
 A calendar summarises those scheduled content events.

diff --git a/docs/multisite/siteaccess/siteaccess.md b/docs/multisite/siteaccess/siteaccess.md
@@ -15,7 +15,6 @@ Each SiteAccess can have different:
 - [languages](set_up_translation_siteaccess.md)
 - [tree roots](multisite_configuration.md#location-tree)
 - [repositories](persistence_cache.md#multi-repository-setup)
-- [recommendations](enable_personalization.md#configure-personalization)
 
 Many other settings in the application are also configured per SiteAccess (also known as "SiteAccess-aware").
 

diff --git a/docs/permissions/limitation_reference.md b/docs/permissions/limitation_reference.md
@@ -282,10 +282,6 @@ The Payment Owner (`PaymentOwner`) limitation specifies whether the user can mod
 |"self"|"self"|Users can access only their own payments. |
 |"all"| none |Users can access all payments.|
 
-## Personalization access limitation
-
-The Personalization limitation specifies the SiteAccesses for which the user can view or modify the scenario configuration.
-
 ## Product Type limitation
 
 The Product Type (`ProductType`) limitation specifies whether the user has access to products belonging to a specific product type.

diff --git a/docs/permissions/limitations.md b/docs/permissions/limitations.md
@@ -15,7 +15,7 @@ Limitations consist of two parts:
 - `LimitationType`
 
 Certain limitations also serve as role limitations, which means they can be used to limit the rights of a role assignment.
-Currently, this covers [subtree of location](limitation_reference.md#subtree-limitation), [Section](limitation_reference.md#section-limitation) and [Personalization access](limitation_reference.md#personalization-access-limitation) limitations.
+Currently, this covers [subtree of location](limitation_reference.md#subtree-limitation) and [Section](limitation_reference.md#section-limitation) limitations.
 
 `Limitation` represents the value, while `LimitationType` deals with the business logic surrounding how it actually works and is enforced.
 `LimitationTypes` have two modes of operation in regard to permission logic (see [`Ibexa\Contracts\Core\Limitation`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Limitation-Type.html) interface for more info):

diff --git a/docs/permissions/policies.md b/docs/permissions/policies.md
@@ -49,13 +49,6 @@ Each role you assign to user or user group consists of policies which define, wh
 |                               | <nobr>`edit`</nobr>   | edit a customer group   |
 |                               | <nobr>`view`</nobr>   | view customer groups    |
 
-#### Personalization
-
-| Module                         | Function            | Effect                                                            | Possible limitations                                                                |
-|--------------------------------|---------------------|-------------------------------------------------------------------|-------------------------------------------------------------------------------------|
-| <nobr>`personalization`</nobr> | <nobr>`edit`</nobr> | modify scenario configuration for selected SiteAccesses           | [Personalization access](limitation_reference.md#personalization-access-limitation) |
-|                                | <nobr>`view`</nobr> | view scenario configuration and results for selected SiteAccesses | [Personalization access](limitation_reference.md#personalization-access-limitation) |
-
 #### Roles
 
 | Module              | Function              | Effect                                                                     | Possible limitations |

diff --git a/docs/personalization/api_reference/api_reference.md b/docs/personalization/api_reference/api_reference.md