Set Up User Context on Bubble
Pass Current User data to your chatbot using an HTML element
What You're Setting
User Context is a client-side JavaScript object. On every page where the widget loads for a logged-in user, you attach an object to window.Asyntai.userContext describing who they are. The widget sends this with each message, so the AI can reply with their name, order status, plan tier, or anything else relevant.
Keys act as labels the AI sees, so make them descriptive — use "Customer name" or "Loyalty points", not just "name" or "points".
window.Asyntai = window.Asyntai || {};
window.Asyntai.userContext = {
"Customer name": "Sarah Chen",
"Email": "sarah@example.com",
"Subscription plan": "Pro",
"Loyalty points": 1840,
"Last order": "#8847, out for delivery"
};
Two ways to set it
Either assign synchronously (if data is already on the page), or provide a fetcher that runs when the chat opens. The second option is better for performance — user data is only loaded when someone actually opens the chat.
// Option A — synchronous (data already available)
window.Asyntai.userContext = { "Customer name": "Sarah", ... };
// Option B — async fetch on chat open (better performance)
window.Asyntai.fetchUserContext = function() {
return fetch('/api/chat-context/')
.then(r => r.json())
.then(data => { window.Asyntai.userContext = data; });
};
Security & size: Never include passwords, credit card numbers, API tokens, or anything sensitive — this data is on the client and visible to anyone inspecting the page. Context is capped at 2,000 characters on Standard and 10,000 characters on Pro; if you exceed it, the tail is truncated.
How Bubble Works
Bubble's Current User is available in any HTML element via dynamic expressions. Drop an HTML element on a reusable header or the page, and use Bubble's dynamic text to inject the logged-in user's fields directly into a <script> block.
Option 1 — HTML Element with Dynamic Expressions (no plugins)
<script>
window.Asyntai = window.Asyntai || {};
window.Asyntai.userContext = {
"Name": "[Current User's Name]",
"Email": "[Current User's email]",
"Plan": "[Current User's Plan]",
"Credits": [Current User's Credits]
};
</script>
Bracketed placeholders become Bubble dynamic expressions. Wrap string fields in quotes; numeric fields can go unquoted.
Escape special characters: If a user's Name or email might contain a quote, ampersand, or angle bracket, Bubble's :formatted as JSON-safe modifier handles escaping for you. Or just avoid putting HTML-unsafe data in the fields at all.
Option 2 — Toolbox Plugin (cleanest)
The free Toolbox plugin adds a "Run JavaScript" action. On a page-load workflow, trigger Run JavaScript with a composed string — this gives you Bubble's full type system for data transforms (formatting dates, joining lists, etc.) before it hits the DOM.
// In a "Run JavaScript" action on page load,
// use Bubble dynamic data inside a workflow-composed script:
window.Asyntai = window.Asyntai || {};
window.Asyntai.userContext = {
"Name": "[Current User's Name]",
"Email": "[Current User's email]",
"Member since": "[Current User's Created Date:formatted as 2021-01-01]"
};
Tip: Bubble SPAs don't reload between pages — which means the HTML element only runs its dynamic expressions when the reusable element first renders. Put it in your app's Header reusable so it's present on every page.
Probleemoplossing
Open your browser DevTools → Console → type window.Asyntai.userContext after the page loads. You should see your object. If it says undefined, your script didn't run — check the script order (context must be set after the widget script loads, or be re-set whenever the user logs in).
The widget reads window.Asyntai.userContext on every message. If a page loads fresh (no SPA routing), you need to set context on that page too. For single-page apps, set it once after login and update it whenever user data changes.
Re-assign window.Asyntai.userContext with the fresh data after any update. The next message the user sends will include the updated values — no page reload needed.
You're over the size limit (2k chars Standard, 10k Pro). Trim verbose fields — keep order history to last 2-3 items, truncate long descriptions, drop fields the AI doesn't need.
Visit the User Context settings page while logged in as a test user, then send a chat message. The status refreshes within a few seconds. If still empty, check the browser console for JavaScript errors and verify the object is set before the chat message is sent.
Privacy reminder: Only share fields relevant to the conversation. Passing a customer's full purchase history when they just want to ask a general question is wasteful and can confuse the AI. Scope context to what helps.