Set Up User Context on WooCommerce

Pass the logged-in customer's info to your chatbot using WooCommerce hooks

Standard & Pro Plans

Switch platform:

Niestandardowy 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 WooCommerce Exposes the Customer

WooCommerce builds on WordPress's authentication system — wp_get_current_user() returns the logged-in user, and WC()->customer gives you WooCommerce-specific data like order history, total spent, and customer segmentation. Inject these into window.Asyntai.userContext via a small PHP snippet hooked into wp_footer.

Setup — PHP Snippet via Code Snippets

Install a snippets plugin Code Snippets, WPCode, or FluentSnippets — any of these let you add PHP without touching your theme files.

Paste the snippet below and activate it Set it to run everywhere (frontend only is fine).

Log in as a test customer and open chat Ask "what's my email?" — the AI should confirm the logged-in customer's email.

add_action('wp_footer', function() {
  if (!is_user_logged_in()) return;

  $u = wp_get_current_user();
  $customer_id = $u->ID;

  $context = [
    'Customer name'  => $u->display_name,
    'Email'          => $u->user_email,
    'Role'           => implode(', ', $u->roles),
  ];

  if (class_exists('WooCommerce')) {
    $context['Total orders'] = wc_get_customer_order_count($customer_id);
    $context['Total spent']  = wc_price(wc_get_customer_total_spent($customer_id));
    $last_order = wc_get_customer_last_order($customer_id);
    if ($last_order) {
      $context['Last order'] = '#' . $last_order->get_order_number()
        . ' — ' . $last_order->get_status();
    }
  }

  echo '<script>window.Asyntai=window.Asyntai||{};window.Asyntai.userContext='
    . wp_json_encode($context) . ';</script>';
}, 100);

Wskazówka: The priority 100 on wp_footer makes sure the snippet runs after most themes have output their content, so window.Asyntai exists when this runs.

Adding Cart Data

Current cart contents are available via WC()->cart — useful for abandoned-cart style conversations:

if (function_exists('WC') && WC()->cart && !WC()->cart->is_empty()) {
  $context['Cart total'] = WC()->cart->get_cart_total();
  $context['Cart items'] = WC()->cart->get_cart_contents_count();
}

Adding Subscription Data (WooCommerce Subscriptions)

if (function_exists('wcs_get_users_subscriptions')) {
  $subs = wcs_get_users_subscriptions($customer_id);
  $active = array_filter($subs, fn($s) => $s->has_status('active'));
  if ($active) {
    $sub = reset($active);
    $context['Subscription'] = $sub->get_status()
      . ' — renews ' . $sub->get_date('next_payment');
  }
}

Rozwiązywanie problemów

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.

Dokumentacja