The Duckie Chrome extension lets support agents use the Duckie widget directly in their browser without requiring a script tag on any website. It automatically injects the widget on pages that match a condition you configure — for example, your Zendesk or Freshdesk agent workspace.
How it works
The extension checks each page the agent visits against the deployment’s configured condition (a localStorage key, cookie, URL parameter, or other browser signal). If the condition passes, it injects the widget automatically. The widget behaves identically to an embedded widget — it collects browser metadata, creates a session, and connects to your agent.
The widget key in the extension identifies your organization and deployment. No per-agent login is required.
Download
Get the extension from the Duckie dashboard:
- Go to Connections → Widget
- Click Get Embed Code
- Open the Extension tab
- Click Download Extension (.zip)
Installation
Self-serve (individual agent)
- Download and unzip the extension file
- Open Chrome and go to
chrome://extensions
- Enable Developer mode (toggle in the top right)
- Click Load unpacked and select the unzipped folder
- Click the Duckie extension icon in the toolbar → Options
- Enter your widget key (found in Connections → Widget → Get Embed Code) and save
The widget will appear on any page where the extension condition passes.
Enterprise (Google Workspace)
IT admins can force-install the extension and push the widget key to all agents without any manual setup.
Step 1 — Force install via Google Admin Console
- Go to Devices → Chrome → Apps & Extensions
- Select the target organizational unit
- Add the extension (by ID or upload the
.crx file)
- Set the install policy to Force Install
Step 2 — Push the widget key via managed policy
On the same extension entry, paste the following into the Policy for extensions field, replacing the values with your own:
{
"widgetKey": {
"Value": "wgt_your_widget_key"
},
"baseUrl": {
"Value": "https://app.useduckie.ai"
}
}
widgetKey and baseUrl are shown pre-filled in the Get Embed Code → Extension tab for your widget.
Agents receive the configuration automatically on their next Chrome sync — no manual entry needed.
If a managed policy key is present, the extension options page is locked and agents cannot change the widget key.
- Go to Deploy → your widget deployment → Edit
- Scroll to Chrome Extension Condition
- Toggle it on and configure:
| Field | Description |
|---|
| Read from | Where to check: localStorage, sessionStorage, Cookie, URL Parameter, JS Expression, or Meta tag |
| Key | The key or name to read (e.g. a localStorage key or cookie name) |
| Expected value | Optional. If set, the value must match exactly. If blank, any truthy value passes. |
| Goal | Source | Key |
|---|
| Inject on any authenticated Zendesk session | Cookie | _zendesk_session |
| Inject only on the agent workspace | JS Expression | window.location.pathname.startsWith('/agent') |
| Inject when a custom flag is set | localStorage | duckie_enabled |
ticketId from localStorage, the agent receives it with every conversation started from that page.
See the website widget page for metadata field configuration.
Troubleshooting
Widget does not appear
- Confirm the widget key is saved in the extension options page
- Check that the deployment has a Chrome Extension Condition configured and toggled on
- Verify the condition passes on the current page (e.g. run
localStorage.getItem('your_key') in the browser console)
- Reload the page after saving a new condition
Widget appears but sends no metadata
- Ensure the metadata field’s localStorage key (or other source) exists on the page before the widget loads
- Set the value before the page loads, not after — embed.js collects metadata on initialization
Managed policy key not applying
- Confirm the agent is signed into Chrome with their managed Google Workspace account
- Policy changes can take a few minutes to propagate; ask the agent to restart Chrome
