Troubleshooting Dynamic Context Not Reaching the Agent

Use this guide when setContext() or ctx_ URL parameters appear to work, but the Marketing Agent does not use the expected visitor data.

Quick Checks

Confirm Dynamic Context Ingestion is enabled.

1. Confirm every key matches a configured variable name.

2. Set context before the conversation starts.

3. Inspect the success and message values returned by setContext().

4. Confirm every value is a supported simple type.

Check the API Result

setContext() reports validation and encryption failures in its resolved result.

const result = await window.AISeller.setContext({
  name: "Jordan",
  company: "Northstar Labs"
});

console.log(result.success, result.message);

Do not treat the absence of a thrown exception as proof that context was stored. Continue only when result.success is true.

Check Timing

Context is attached when the conversation is created. Set it before showAndConnect() or before the visitor starts the conversation.

const result = await window.AISeller.setContext({ name: "Jordan" });

if (result.success) {
  window.AISeller.showAndConnect();
}

Context set after the conversation starts applies only to a later conversation.

Check Variable Names

Compare each JavaScript or URL key with the variable configured in Docket. Treat names as exact, including capitalization.

For URL ingestion, remove the ctx_ prefix before comparing. For example, ctx_company_name maps to company_name.

Check Value Types

Supported values are strings, numbers, booleans, and null.

const result = await window.AISeller.setContext({
  name: "Jordan",
  employees: 500,
  isCustomer: true,
  renewalDate: null
});

Nested objects, arrays, files, functions, dates, and undefined values return success: false.

Check Script Readiness

In the browser console, verify that the required methods are available:

typeof window.AISeller?.setContext
typeof window.AISeller?.showAndConnect

Both checks should return "function". If they do not, confirm the Docket deploy script loaded successfully and is not blocked by a Content Security Policy, consent manager, ad blocker, or network rule.

Check for an Unintended Reset

resetContext() replaces pending visitor context with an empty object. Search your website code for reset calls that run after setContext() or during route changes.

await window.AISeller.setContext({ name: "Jordan" });
await window.AISeller.resetContext(); // The pending context is now empty.

Verify the Fix

1. Open the deployed experience in a private browser window.

2. Set documentation-only context and confirm success: true.

3. Start a new conversation.

4. Ask a question that should use one configured variable.

5. Confirm the agent uses the value according to the variable description.

6. Reset context and confirm a second conversation does not reuse the first visitor's values.

Symptom Reference

Related Articles

• Using the AISeller JavaScript API

• Setting Up Dynamic Context Ingestion

• Passing Context via URL Parameters to Marketing Agents

• Passing Form Data to a Marketing Agent

• Security Guidelines for Passing Visitor Context