Skip to main content
DannyPancratz
DannyPancratz
VIP ⭐️⭐️⭐️⭐️⭐️
Jul 15, 2025 1:59 PM UTC
Solved

How to get Product Mapper UI Element Feature Being Used Right Now to work for Engagement Audience Logic?

Is it even possible to leverage the Product Mapper {Feature} Is Being Used Right Now for features that are mapped as UI element rules? 

Since these features are tracked on clicks, when/how would the “right now” be defined? 

From my testing, it does not seem to be working when the mapped UI element is just present on the screen. 

I suspect Being Used Right Now works only for URL based features. 

    rschlette
    rschletteAnswer
    Expert ⭐️
    Jul 15, 2025 2:08 PM UTC

    Right Now will work for click events mapped with UI element rules as well. After each click event, PX will send a request to the SDK to reevaluate the user for active engagements. So when the user clicks, the click request gets sent to PX, and the inapp request evaluates the audience logic.

     

    One caveat I’ve seen is when the PX tag is deployed via Segment.io, sometimes there is a delay/lag between the events themselves, and when the events arrive in PX. That lag makes real time qualification impractical or at least unpredictable. 

     

    Are you seeing adoption data for the feature in question?

    View in thread

    7 replies

    DannyPancratz
    DannyPancratzAuthor
    VIP ⭐️⭐️⭐️⭐️⭐️
    Jul 15, 2025 2:04 PM UTC

    supporting my hypothesis 

    I suspect Being Used Right Now works only for URL based features. 

     

    1. I mapped a UI element feature for the step directly before when I want the poll to show automatically. 
    2. I set the audience logic for an automatic engagement to equal {feature from step 1} is being used right now

    When I tested in the Preview mode, clicking on the feature does not trigger the automatic guide. 

    Edit: comment lower in the thread indicates Preview can be unreliable for this type of audience logic. My hypothesis was wrong. 

    Translate
    FYI: I am no longer active in this community
    rschlette
    rschletteAnswer
    Expert ⭐️
    Jul 15, 2025 2:08 PM UTC

    Right Now will work for click events mapped with UI element rules as well. After each click event, PX will send a request to the SDK to reevaluate the user for active engagements. So when the user clicks, the click request gets sent to PX, and the inapp request evaluates the audience logic.

     

    One caveat I’ve seen is when the PX tag is deployed via Segment.io, sometimes there is a delay/lag between the events themselves, and when the events arrive in PX. That lag makes real time qualification impractical or at least unpredictable. 

     

    Are you seeing adoption data for the feature in question?

    Translate
      rschlette
      rschlette
      Expert ⭐️
      Jul 15, 2025 2:12 PM UTC

      Sorry, we were posting simultaneously. Since you’re seeing adoption data for the feature in question, I’d recommend not relying on Preview mode. Real time evaluation is best tested in a live engagement. Just limit the audience to your user id.

      Translate
        DannyPancratz
        DannyPancratzAuthor
        VIP ⭐️⭐️⭐️⭐️⭐️
        Jul 15, 2025 2:18 PM UTC

        Thanks, ​@rschlette! This is overall good news. 

        I’ll test in a live env and report back. I’ve confirmed the feature usage data is coming through. 

        Translate
        FYI: I am no longer active in this community
          DannyPancratz
          DannyPancratzAuthor
          VIP ⭐️⭐️⭐️⭐️⭐️
          Jul 15, 2025 2:31 PM UTC

          That did the trick. Thanks again, ​@rschlette!

           

          Translate
          FYI: I am no longer active in this community
          rschlette
          rschlette
          Expert ⭐️
          Jul 15, 2025 2:33 PM UTC

          Awesome! As far as I’ve ever seen, Preview mode will not evaluate audience logic or triggers (aside from showing the badge if applicable). I’m glad that worked!

          Translate
            link_black
            link_black
            Gainsight Employee ⭐️⭐️
            Jul 15, 2025 9:32 PM UTC

            Thanks for helping ​@rschlette and for posting ​@DannyPancratz!

             

            Engagement “preview” mode does not use any Audience Logic at all, it just renders the Engagement on the URL you specify through the “preview” option (Dialog, Survey, Slider) or you are on with the Edit in-app Guide feature when you select the “preview” option there.  

             

            My go to option is…

            1. Add my email/ID into the existing Engagement Audience Logic, select “once per visit” in the Engagement Qualification Scope, and then launch it.
            2. Login to the PX tracked application as my test user, which creates a new session/visit, and match the Engagement Audience Logic.  That should trigger the Engagement to play.
            3. To repeat the testing process, you can simply delete the apt.sid cookie in your browser that is associated to your application’s domain (this tracks the PX session) and then refresh the page and match the Engagement Audience Logic again.  This should trigger the Engagement to play again.

             

            Here are some additional resources for testing in-app Engagements…

             

            https://support.gainsight.com/PX/Engagements/Tutorials/How_to_Test_In-app_Engagements_in_Gainsight_PX

             

            https://support.gainsight.com/PX/Engagements/Engagement_Best_Practices/07_Test_and_Deploy_Engagements

             

            Happy PX-ing!!

             

             

            Translate
            -- Link
              Terms & ConditionsAccessibility statement