Skip to main content

Dynamic “conversation attribute” segments for Knowledge Base access (volatile per conversation)

We run separate web apps under the same FeatureBase account and need Knowledge Base access to change based on the user’s active app/tab context (e.g., current_app = "A" vs current_app = "B"), and reset back to “All Users” when the widget/tab is inactive.


Today, the only option is using identify()/boot() customAttributes, but rapid updates are blocked by the SDK’s caching/rate-limiting behavior (e.g., “Skipping identify because the same data was sent in the last 600s”), making real-time segmentation impossible for multi-tab workflows.

Please add dynamic segments driven by per-conversation/per-session attributes (not persistent user properties), so we can manage KB permissions using volatile context (active app, tab focus, widget open state) without fighting identify() caching or risking rate limits.

Post type
💡 New feature

Log in to comment and vote

No comments yet

Be the first to share your thoughts.