ダッシュボードに戻る

ドキュメント

Asyntaiの使い方を学ぶ

機能
Ask AI バー AI 検索バー WordPress のための AI 検索 AI Search for Joomla AI Search for Webflow AI Search for Ghost AI Search for Moodle AI Search for TYPO3 AI Search for Craft CMS AI Search for Grav AI Search for Concrete CMS AI Search for October CMS AI Search for ProcessWire AI Search for Odoo AI Search for Bagisto AI Search for Medusa AI Search for OpenCart AI Search for BigCommerce AI Search for Magento ウェブサイトクロール 知識のギャップ 商品カード 動的商品カード ダイナミック画像 ユーザーコンテキスト カスタムツール リンクパラメータ ライブモニタリング オペレーター対応 エスカレーション AI通知 デイリーレポート リアルタイムデータフィード リアルタイムデータフィードMax チームメンバー シングルサインオン 二要素認証 画像を含める 画像認識 翻訳ウィジェット ローカライズ AIの透明性 リード スマートリード獲得 サポートチケット チャットのカテゴリ 予約 埋め込み ページの除外 ブロックされたIP データ保存ポリシー ゼロ保存モード 個人情報マスキング 出力クラシファイア Access Tags ウィジェットのバージョン固定 監査ログ よりスマートなモデル 思考モードを有効化 返信候補 フォローアップメッセージ 音声テキスト変換 トランスクリプトのダウンロード 埋め込みチャット iframe による埋め込み

Set Up User Context on BigCommerce

Pass the logged-in customer's info using your Stencil theme

Back to User Context
Standard・Pro・Enterprise プラン

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": "[email protected]",
  "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 BigCommerce Exposes the Customer

BigCommerce's Stencil themes expose a customer global in Handlebars templates. When a shopper is logged in, you get customer.name, customer.email, customer.id, customer.phone, and customer.customer_group_id — enough to build a rich context object.

Option 1 — Stencil Theme Edit

1
Download your active theme BigCommerce admin → Storefront → My Themes → Advanced → Download current theme. (If you're using Page Builder only, skip to Option 2.)
2
Open templates/layout/base.html This is the master layout — script added here runs site-wide.
3
Add the Handlebars block below just before </body> Re-upload the theme and apply it.
{{#if customer}}
<script>
  window.Asyntai = window.Asyntai || {};
  window.Asyntai.userContext = {
    "Customer name": {{{json customer.name}}},
    "Email": {{{json customer.email}}},
    "Customer ID": {{customer.id}},
    "Customer group": {{customer.customer_group_id}}
  };
</script>
{{/if}}

The json helper is BigCommerce's built-in way to output a Stencil value as a JavaScript-safe JSON literal — it handles quotes and special characters so you don't have to escape manually.

Option 2 — Script Manager (no theme edit)

If you'd rather not touch the theme, BigCommerce's Script Manager lets you inject client-side JavaScript that reads the Customer ID from the visible DOM or a BigCommerce JS object.

1
Go to Script Manager BigCommerce admin → Storefront → Script Manager → Create a Script.
2
Use fetchUserContext to hit a proxy Point the fetcher at an endpoint on your domain that reads the session cookie and returns the JSON — the cleanest way since Script Manager doesn't expose the customer object directly.
<script>
window.Asyntai = window.Asyntai || {};
window.Asyntai.fetchUserContext = function() {
  return fetch('/api/my-user-context', { credentials: 'include' })
    .then(r => r.json())
    .then(data => { window.Asyntai.userContext = data; });
};
</script>

Your /api/my-user-context endpoint (hosted anywhere, even on a small Cloudflare Worker or external server) verifies the session and returns the customer JSON. Use the BigCommerce Customers API with a server-side token to look them up.

ヒント: Option 1 (Stencil edit) is faster to implement — no proxy needed. Option 2 is better if you're locked out of theme edits or want to include data BigCommerce doesn't expose in Handlebars (e.g. recent orders from the Admin API).

トラブルシューティング

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.