Set Up User Context on Wix

Pass Wix Members data to your chatbot using Velo's wix-members API

Standard & Pro Plans

Switch platform:

Brugerdefineret Shopify WooCommerce BigCommerce Ecwid OpenCart Magento PrestaShop Odoo WordPress Drupal Joomla Ghost Wix Squarespace Webflow Bubble

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 Wix Exposes the Member

Wix Members are available through Velo's wix-members API. currentMember.getMember() returns the logged-in member — you combine this with wixWindow.rendering.env to make sure the code runs on the live site (not the editor preview).

Setup — Velo Page Code

Enable Dev Mode In the Wix editor, click the top bar → Dev Mode → Turn on Dev Mode. The Code panel appears at the bottom.

Open the masterPage.js file In the Code Files panel → Public → Site → masterPage.js. Code here runs on every page.

Paste the code below and publish Click Publish — Velo page code only runs on the live site.

import { currentMember } from 'wix-members';

$w.onReady(async function() {
  try {
    const member = await currentMember.getMember();
    if (!member) return;  // visitor not logged in

    const profile = member.profile || {};
    const contact = member.contactDetails || {};

    window.Asyntai = window.Asyntai || {};
    window.Asyntai.userContext = {
      "Name":       profile.nickname || (contact.firstName + ' ' + contact.lastName),
      "Email":      member.loginEmail,
      "Member ID":  member._id,
      "Status":     member.status
    };
  } catch (e) {
    // Visitor not a member — do nothing
  }
});

Combining with Wix Stores, Bookings, or CMS

If you run a Wix Store or Bookings, you can enrich the context with the member's order or appointment history. Query those collections in the same handler:

import wixData from 'wix-data';
import { currentMember } from 'wix-members';

$w.onReady(async function() {
  const member = await currentMember.getMember().catch(() => null);
  if (!member) return;

  // Count past orders for this member
  const orders = await wixData.query('Stores/Orders')
    .eq('buyerInfo.memberId', member._id)
    .count();

  window.Asyntai = window.Asyntai || {};
  window.Asyntai.userContext = {
    "Name":         member.profile?.nickname || '',
    "Email":        member.loginEmail,
    "Total orders": orders
  };
});

Velo required: Wix's editor (without Dev Mode) can't access member data client-side. Velo is free on any paid Wix plan — enable Dev Mode once and you unlock wix-members. If you aren't on a paid plan, this feature isn't available.

Tip: Use masterPage.js rather than per-page code — that way the context is set consistently on every page of the site, not just the page you happen to be editing.

Fejlfinding

The AI doesn't seem to know who I am

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).

Context works on some pages but not others

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.

Data is stale after the user updates their profile

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.

Context is truncated

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.

User Context status page shows "Not receiving context"

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.