Set Up User Context on Drupal
Pass the logged-in user's info using drupalSettings or a Twig template
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 Drupal Exposes the User
Drupal renders a drupalSettings JavaScript object on every page. It always includes drupalSettings.user.uid (0 for anonymous visitors). For other fields (name, email, roles), add them via a small custom module using hook_js_settings_alter — that way they're available site-wide.
Option 1 — Tiny Custom Module (recommended)
asyntai_context.module:
<?php
use Drupal\Core\Asset\AttachedAssetsInterface;
function asyntai_context_js_settings_alter(array &$settings, AttachedAssetsInterface $assets) {
$user = \Drupal::currentUser();
if ($user->isAuthenticated()) {
$account = \Drupal\user\Entity\User::load($user->id());
$settings['asyntai'] = [
'user' => [
'Name' => $account->getDisplayName(),
'Email' => $account->getEmail(),
'Roles' => implode(', ', $user->getRoles()),
'Member since' => date('F Y', $account->getCreatedTime()),
],
];
}
}
function asyntai_context_page_attachments(array &$attachments) {
$attachments['#attached']['library'][] = 'asyntai_context/bridge';
}
asyntai_context.libraries.yml:
bridge:
version: 1.x
js:
js/asyntai-bridge.js: {}
dependencies:
- core/drupalSettings
js/asyntai-bridge.js:
(function (drupalSettings) {
if (!drupalSettings.asyntai) return;
window.Asyntai = window.Asyntai || {};
window.Asyntai.userContext = drupalSettings.asyntai.user;
})(drupalSettings);
Option 2 — Twig in Your Theme's html.html.twig
If you can edit theme templates, add the script straight into your theme's html.html.twig — faster, no module needed:
{% if logged_in and user is defined %}
<script>
window.Asyntai = window.Asyntai || {};
window.Asyntai.userContext = {
"Name": "{{ user.getDisplayName()|escape('js') }}",
"Email": "{{ user.getEmail()|escape('js') }}",
"Roles": "{{ user.getRoles()|join(', ')|escape('js') }}"
};
</script>
{% endif %}
Sfat: If you're on Drupal Commerce, extend Option 1 to include the user's current cart and order count — load them with entityTypeManager in the hook before assembling $settings['asyntai'].
Depanare
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.