# window.aeoSettings Configuration Reference

> Canonical source: [window.aeoSettings Configuration Reference](https://www.answer.cloud/pages/window-aeosettings-configuration-reference-hosted/)

Configure the current answer.cloud embed, including nested chat options, analytics tracking, page buttons, and site search.

`window.aeoSettings` is the configuration object read by the current answer.cloud embed bundle. Keep this API name even though the product is called answer.cloud. Define it before loading `https://app.answer.cloud/embed.js`; the old `embed/loader.mjs` URL is not the current installation path.

## Minimal external-site example

```html
<script>
  window.aeoSettings = {
    organization_id: 123,
    chat: {
      enabled: true,
      button_text: "Ask our AI",
      button_text_color: "#1A1B1C",
      intro_text: "How can we help?"
    }
  };
</script>
<script src="https://app.answer.cloud/embed.js"></script>
```

Replace the example organization ID with your own. Hosted and companion pages receive a generated configuration; use the platform’s widget settings instead of adding this snippet again.

## Top-level settings

| Setting | Purpose |
| --- | --- |
| `organization_id` | Routes the integration to the intended organization. |
| `site_id` | Selects a site where an explicit site target is needed. |
| `organization_sub`, `organization_domain` | Supply organization domain information used by features such as page buttons. |
| `base_url` | Overrides the application backend; the normal default is `https://www.answer.cloud/`. |
| `css_path` | Loads a public custom stylesheet in both the host document and chat iframe. |

Scope custom CSS to the widget so it does not change the rest of your website. Keep the attribution link available.

## Chat settings

`chat.enabled === true` enables chat. Put `button_text`, `button_text_color`, and `intro_text` inside the `chat` object. The current default trigger text color is `#6f7071`. `button_color` is not read as a color setting by the current bundle; use a scoped custom theme for other appearance changes.

## Analytics settings

Analytics events are enabled unless `analytics.enabled` is explicitly `false`. Setting that flag to false stops event collection, but the bundle can still initialize session and first-touch state. Use `analytics.tracking: false` when the integration must also avoid initializing that tracking state.

```js
analytics: {
  enabled: false,
  tracking: false,
  track_forms: false
}
```

The form-event option is `analytics.track_forms`, not `form_tracking`. Test your consent flow and the resulting browser behavior; these flags alone do not establish compliance with every privacy requirement.

## Page buttons and site search

`button.enabled === true` enables page-button injection. Its options include `subdomain` and `button_selector`; ensure the generated text destinations actually exist for the site.

`site_search.enabled === true` enables site search. Options include `button_text`, `form_selector`, `input_selector`, and `results_selector`. Point selectors at existing elements and verify the rendered results.

Chat, page buttons, and site search require explicit true flags. The current embed is a bundled script; these options control initialization rather than fetching the obsolete module loader.

See the [installation guide](https://www.answer.cloud/pages/how-to-install-the-answer-cloud-ai-chat-widget-on-your-website-hosted/) for platform setup and verification.