Skip to main content
Solved

Can Global Context values be used in the content of a PX Engagement?

  • February 25, 2026
  • 4 replies
  • 24 views

DannyPancratz
Forum|alt.badge.img+9
  1. Global Context exists in the available data for engagements, as it can be used for Audience rules, etc. 
  2. Engagements can show content to users(s) via a Guide, Dialog, etc.

Is there a way to use values from #1 in #2? 

Use case Example: 

Dynamic “Approver” value shown to users. 

  1. Approver value exists in the Global Context
  2. Engagement tied to a specific UI element (ex. disabled button)
    • Content: “This capability is limited to designated approvers only. Reach out to {Global Context Approver Value}”

In this example use case, the global context for the approver value would be unique to each customer company / product subscription. Rather than needing to have bespoke engagements for each customer, we’d prefer to insert that value dynamically into on engagement for all/most users. 

 

Best answer by rschlette

To my knowledge the engagement tokens can only access User and Account attributes

 

If the approver is dynamic, you could use ‘set’ or ‘identify’ on the given page to update it as a User attribute and tokenize it from there, but I don’t know of a way to use GC in the engagement tokens

4 replies

rschlette
Forum|alt.badge.img+2
  • Expert ⭐️
  • Answer
  • February 25, 2026

To my knowledge the engagement tokens can only access User and Account attributes

 

If the approver is dynamic, you could use ‘set’ or ‘identify’ on the given page to update it as a User attribute and tokenize it from there, but I don’t know of a way to use GC in the engagement tokens


DannyPancratz
Forum|alt.badge.img+9
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • February 25, 2026

Thanks for offering a solution, ​@rschlette


rschlette
Forum|alt.badge.img+2
  • Expert ⭐️
  • February 25, 2026

One thing to be cautious about is that those user and account attributes are persistent. So where you can clear/reset global context when you move from page to page, the User attribute will retain the previous value until a new value is passed.

 

So if article A set approver to ‘Rob’, and article B doesn't set an approver, here Rob is still the value for User->approver (or whatever you call the attribute). Handling nulls will require a little testing. There may be a fallback value that you can add to the logic that sets the approver attribute, like an else condition.


DannyPancratz
Forum|alt.badge.img+9
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • February 25, 2026

Incredible call out, ​@rschlette! You’re the best!