Set Up User Context on Ghost
Pass logged-in Ghost Member info to your chatbot using the Members API
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 Ghost Members Work
Ghost Members is Ghost's built-in membership and subscription system. When a visitor is signed in, Ghost sets a session cookie and exposes member data via /members/api/member/ — a small client-side fetch gives you the full member object.
Setup — Code Injection
<script>
window.Asyntai = window.Asyntai || {};
window.Asyntai.fetchUserContext = function() {
return fetch('/members/api/member/', { credentials: 'include' })
.then(r => r.ok ? r.json() : null)
.then(member => {
if (!member) return; // visitor is not signed in
window.Asyntai.userContext = {
"Name": member.name || '',
"Email": member.email,
"Member status": member.status, // e.g. free, paid, comped
"Member since": new Date(member.created_at).toLocaleDateString(),
"Subscription": member.subscriptions && member.subscriptions[0]
? (member.subscriptions[0].plan.nickname + ' — ' + member.subscriptions[0].status)
: 'Free',
};
});
};
</script>
We use fetchUserContext (rather than setting userContext directly) so Ghost's member endpoint is only called when someone actually opens the chat — keeping page loads fast.
Vihje: Ghost's /members/api/member/ returns a 204 No Content for anonymous visitors. The script handles this by returning null — so the chat still works for non-members, just without personalization.
Passing Newsletter or Label Data
Ghost Members can be tagged with labels or subscribed to newsletters — both are returned by /members/api/member/. Add them to the context if they help the AI tailor answers:
"Labels": member.labels ? member.labels.map(l => l.name).join(', ') : '',
"Newsletters": member.newsletters ? member.newsletters.map(n => n.name).join(', ') : '',
Privacy: The member payload is returned with credentials: 'include' — meaning it only works for the visitor's own session. You're not exposing other members' data. Safe to include in public-facing code.
Veaotsing
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.