# Install the website feedback widget > Add a floating or inline widget, select a rating scale, and verify delivery in your inbox. Canonical URL: https://pollenate.dev/docs/widgets/installation/ The standalone widget runs from a script tag. You need an inbox key and an **organization key with collect scope**. A collect key placed in browser code is visible to visitors; do not substitute a read, write, admin or personal key. ## Install a floating widget Place this before the closing `` tag, replacing the two placeholders: ```html ``` Submit a test response and check the inbox. The script is the collector; the inbox key selects its destination. The API key must belong to the destination's organization and, for a brand-scoped key, its brand. ## Choose a type | Type | Input | | --- | --- | | `thumbs` | Down/up, scores 0 and 1 | | `stars` | 1–5 stars | | `csat` | 1–5 satisfaction | | `nps` | 0–10 recommendation scale | | `emoji` | Five sentiment choices, scores 1–5 | | `text` | Written feedback | Floating positions are `bottom-right`, `bottom-left`, `top-right` and `top-left`. Theme accepts `light`, `dark` or `auto`; `auto` follows the system preference. ## Render inline Create the target element before the script. `data-container` selects it and implies inline mode: ```html
``` Use a selector that identifies the intended element. A missing container prevents the inline placement from working as expected. ## Context and impressions `data-context` accepts a JSON object. `data-track-impressions="false"` disables widget impression tracking; it does not disable submissions. `data-strip-query-params="true"` strips query parameters from tracked page URLs. Review any context and page URL before sending it. ```html ``` For troubleshooting, inspect the browser Console and Network panels. `401` points to a missing/invalid key, `403` to access or scope, `404` to routing, and `429` to a rate or daily limit. A blocked network request may be a [Content Security Policy problem](/docs/troubleshooting/csp/). Use [React](/docs/widgets/react/) for component-based lifecycle control and [themes](/docs/workspace/themes/) for appearance.