Smartedit Personalization - User segment mapping

[former_member624984]

I am new to personalization module, and have added the required personalization extensions as per Hybris help pages and have followed the steps -

1. Created a new customization and enabled it.
2. Created a new target group and enabled it.
3. Created a new user segment.
4. Selected customization and changed a component, catalog sync done. Changes seen on smartedit.
5. Mapped a registered user to this new segment used in the customization.

Post this on trying to login as user to view the customized page, I don't see the changes seen on storefront.

In backoffice, personalization --> user in segments , I see that user is mapped only to USER_REGISTERED segment with 10.5 as affinity and user is removed from the segment created in step 3 above.

I am using the OOTB personalization configuration settings.

Why is the user getting removed from segment automatically?

Are there any further steps to be done that I am missing to retain the user mapped to the new segment and customization to work?

It would be helpful if there are any pointers on how can I proceed further.

Thanks

[crescenzorega]

Hi,

try reading this configuration page

Set Up a Personalization Configuration

I hope it will help you

Regards,

Crescenzo Rega

[former_member624984]

Thanks, I am referring to this link https://help.sap.com/viewer/9d346683b0084da2938be8a285c0c27a/1811/en-US/0e1c3eb7b46f4465a471cee582af... and having the same configuration as mentioned but the issue that I am facing currently is everytime user logins, user mapping from segment is removed.

[crescenzorega]

Hi,

tried to verify the impex, inside the personalizationsampledataaddon extension there are examples

resources/import/contentCatalogs

• apparel-deContentCatalog
• apparel-ukContentCatalog
• electronicsContentCatalog
• powertoolsContentCatalog

cms-addon-extra.impex files

We have set a personalization on a registered user by showing a custom banner on the homepage, and it works.ù

Regards,

Crescenzo Rega

[former_member624984]

Hi, Thanks I did verify this impex, and I have created the similar impex with segment, userToSegment, customizationgroup, customization

Issue is when the user logs in, user gets the normal storefront banner instead of custom banner. On analyzing found 2 things

1. User is retained to USER_REGISTERED segment, but removed from custom segment. Below is the image, when from impex user was assigned to both segments. Only during login, user gets removed from custom segment only. User link for that custom segment is empty.
2. Secondly, found no console errors but found these lines as WARN statements logged -

INFO () () process :defaultPersonalizationCalculationProcess(VERSION:b71509f420381fdb6dd5afd397db172b3431929e4f6c86da0526338d2cd09be) on cluster id :0

WARN () () [DefaultBaseSiteConsumedDestinationLocatorStrategy] Failed to find consumed destination for the given id [CxIdentityServiceClient] and the current base site
WARN () () [DefaultCxProfileIdentifierStrategy] Failed to get profile identifier. Check if yaas configuration for CxIdentityServiceClient is properly defined. Error message: Failed to find consumed destination for the given id : {}CxIdentityServiceClient

What could be the possible issue here? Also how is the affinity of 10.5000000 always being calculated for USER_REGISTERED segment?

Any advice regarding this

Thanks!

[crescenzorega]

try reading these guides maybe they can help you

Set Up Personalization with Context-Driven Services Foundation

How to Run Remarketing Campaigns Leveraging the Web Push Notification Channel (Part 1/4)

Context-Driven Services Foundation Services Clients

[former_member624984]

These warning statements are seen in both OOTB 1811 and 1905 version. In 1905 customization is working fine and user retains in the custom segment added, along with its entry in USER_REGISTERED segment. As of now, I have observed the user link mapping getting removed from custom segment only on 1811 versions. What version are you using, crescenzorega ? Is this a known issue specific to 1811 versions?

[crescenzorega]

Hi Sandhya M,

we started with the 1905 version, now we are on the 1905.24.