Custom segements

[Anthony-WebsiteSoft]

Which Umbraco Engage version are you using? (Please write the exact version, example: 13.2.0)

13.5.2

Which Umbraco version are you using? (Please write the exact version, example: 13.5.2)

13.9.2

Issue summary

We want to implement a custom segment: region in Umbraco Engage that uses a query parameter for targeting. However, instead of serving the personalized variant result, the setup should always fall back to and display the default variant.

Specifics

ISSUE: we are seeing the default title property value (We take care…)
EXPECTED: We were expecting to see the variant value on the title property created in STEP 1 > Screen 3 (MDU - England…).

Steps to reproduce

We want to implement a custom segment: region in Umbraco Engage that uses a query parameter for targeting. However, instead of serving the personalized variant result, the setup should always fall back to and display the default variant.

We are following below steps for the personalization

Step 1: Create a custom segment called region which uses a region query param
CMS Steps

Screen 1: create a segment with region

Screen 2: Use segment for personalization on page

Screen 3: Content changes for the variants

Step 2 : Code Implementation

Step 3 : Calling CDA endpoints to get page variant
call the engage tracking end point to get the external id

pass the external visitor id in CDA headers and region in query parameters
in region pass England in below screen shot

ISSUE: we are seeing the default title property value (We take care…)
EXPECTED: We were expecting to see the variant value on the title property created in STEP 1 > Screen 3 (MDU - England…).

Expected result / actual result

ISSUE: we are seeing the default title property value (We take care…)
EXPECTED: We were expecting to see the variant value on the title property created in STEP 1 > Screen 3 (MDU - England…).

[cornehoskam]

Hi @Anthony-WebsiteSoft,

Thank you for your issue report. Because I don't have access to the exact code in order to reproduce & analyze the issue myself, let's see if we can figure things out through this way instead!

In step 2 during the code implementation for the Segment Rule, are you able provide me with some debug information about the roleValue & TypedConfig.Role? I'm specifically looking to find out if the IsSatisfied method ever returns True in your scenario, are you able to debug whether that's the case or not?

For your expected JSON result in the Content API, would it be possible to try out any non-custom Segments provided by Engage that you are able to configure (e.g. Time of Day) with the same setup as you have already, and see if that does return the personalized content through the API?

Kind regards,
Corné