Contextual Help Based on User Metadata
Kesavan M
The customer wants the widget to deliver content based on metadata such as persona, study, site, and solution. Since their UI changes dynamically, URL-based mapping alone is not sufficient.
Log In
Mohamed Shakheen
Hi Kesavan
Understood. You want the widget to deliver context-specific content based on metadata such as persona, study, site, and solution, rather than relying solely on URL-based mapping. Given that your UI is dynamically rendered, the current URL-driven rules are not sufficient, and the widget will need a more flexible way to consume and act on metadata.
To assess feasibility and define the right approach, I need a few details:
- How will the metadata be exposed to the widget?
Will it be provided via your application’s JavaScript variables, API response, data layer, or another mechanism?
- Is the metadata available at the moment the widget loads, or does it change after the page renders?
- Do these metadata values remain consistent during the session, or can they change dynamically as the user navigates?
- Should the widget adapt instantly when metadata changes, or only on reload?
- Do you expect the widget to support multiple metadata combinations (e.g., persona + site + solution), or is it typically one key attribute driving content?
- How granular should the mapping be -
Article level, category level, or curated content groups?
Once we have clarity on these implementation details, we can evaluate how to extend the widget to support metadata-driven content delivery.