Set Up User Context on PrestaShop

Pass the logged-in customer's info using Smarty / Twig theme hooks

Back to User Context
Standard & Pro Plans

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 PrestaShop Exposes the Customer

PrestaShop 1.7+ themes expose a global prestashop JavaScript object that includes prestashop.customer with the logged-in shopper's data: firstname, lastname, email, id. It's available automatically on every front-office page.

Option 1 — Smarty Template Override

Add a small JS block to your theme's global footer. The cleanest location is layouts/layout-both-columns.tpl (or override layout-footer.tpl) — but the easiest is to use the Custom Code feature in admin.

1
PrestaShop admin → Design → Custom Code This is the built-in spot for injecting site-wide scripts without touching theme files.
2
Paste the script below into "Add JavaScript" (HTML_AFTER_BODY) Save. It runs on every storefront page.
<script>
(function() {
  if (!window.prestashop || !prestashop.customer || !prestashop.customer.is_logged) return;

  var c = prestashop.customer;
  window.Asyntai = window.Asyntai || {};
  window.Asyntai.userContext = {
    "Customer name": c.firstname + ' ' + c.lastname,
    "Email":         c.email,
    "Customer ID":   c.id,
    "Group":         c.id_default_group
  };
})();
</script>

Option 2 — Order History via Webservice

To include order history and totals, combine the customer ID from prestashop.customer with a proxy call to PrestaShop's Webservice:

<script>
window.Asyntai = window.Asyntai || {};
window.Asyntai.fetchUserContext = function() {
  if (!window.prestashop || !prestashop.customer.is_logged) return Promise.resolve();
  return fetch('/your-proxy/user-context?customer_id=' + prestashop.customer.id, {
    credentials: 'include'
  })
  .then(r => r.json())
  .then(data => { window.Asyntai.userContext = data; });
};
</script>

Your proxy then calls PrestaShop's Webservice (enabled under Advanced Parameters → Webservice) with an API key, reads orders/customer details, and returns the flat JSON.

Tip: prestashop.customer is only populated on the front office. If you're running multiple storefronts (multishop), each shop has its own customer scope — so the context naturally matches whichever store the visitor is shopping on.

Probleemoplossing

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.