As explained in the previous article, some Audience Targeting rules do not have a direct equivalent in Liferay DXP 7.2 and, therefore, they cannot be migrated automatically. Here are the recommended solutions for each rule type.
Some User Attributes, like Gender or Age, do not have a direct equivalent in Liferay DXP 7.2. User Attributes retrieved from external sources like Facebook also do not have a replacement. To replace these, you must create a custom user field and use that to define your new Segment.
For Session attributes that do not have a direct equivalent, the recommended solution is to use a URL field for the current URL or a previously visited URL on your site as criteria, or to use a Cookie for more advanced session tracking needs.
In Liferay DXP 7.2 analytics is now managed through Analytics Cloud. You can learn more about creating behavior based rules in the Analytics Cloud documentation.
Audience Targeting segmentation features could be extended using custom rules. As part of the upgrade planning process, the function of any such rules should be re-evaluated with the new Segmentation features of Liferay DXP 7.2 in mind.
First, check the Segmentation reference if any new criteria fields can replace their function. In particular, custom fields, URL fields, and cookies might help you migrate your custom rules with little to no additional development.
If none of them cover your requirements, follow the development guide for instructions on how to add new criteria fields and contributors.
With Audience Targeting, you could display personalized content with the User Segment Display Content portlet or by using Asset Publisher with the Segments filter enabled. In Liferay DXP 7.2, you must choose the most appropriate personalization option for your use cases.
The User Segment Content Display portlet was used to display existing content based on segment membership rules. In Liferay DXP 7.2, you can cover the same use case by defining manual content sets with variations for your different audiences and applying it to an asset publisher. See the documentation for creating personalized Content Sets. With this feature, you can assign any number of assets to the Content List for the given audience, and then use the Asset Publisher to define how content is displayed on the page.
Finally, if you want to display a dynamic list of content for your different audiences based on a filter in the same way you did with in Audience Targeting with the Segments filter in the Asset Publisher, you can create a dynamic content set with variations for your audiences and apply it to an asset publisher.
In addition, the new Experience-based Content Page personalization feature may fulfill a use case that you were previously solving with one of the methods previously available.