Verify the installation
Check that the widget runs on your site, understand the install statuses, and fix the most common problems.
Where to see the status
Nudge shows whether the widget is installed in three places:
- Onboarding, step Install the agent on your site: "Agent detected on …" or "Agent not detected yet".
- Agents › Website Agent › On your site: the status on the Widget row, next to Re-check installation and Copy the snippet.
- The booking form has its own status. See Booking form.
The three statuses
| Status | What it means |
|---|---|
| Live (in onboarding: "Agent detected on …") | A page of your site has loaded the widget. It is installed and running. |
| Not detected | No page of your site has loaded the widget yet. |
| Blocked by CSP | Your site sends a Content Security Policy that would block the widget. This status wins over Live: a past visit does not prove the widget still runs today. |
How detection works
Nudge does not guess: the status is based on what really happened on your site.
- The visit signal. When a page of your site loads the widget, the widget tells Nudge. That is what turns the status to Live. So after installing, open a page of your published site once: until a real page view happens, the status stays Not detected.
- The page check. Re-check installation also opens the home page of your site from Nudge's servers. It reads the page's Content Security Policy (header and
<meta>tag) and looks for the Nudge snippet in the HTML. That is how Nudge can say Blocked by CSP and list the exact sources to add.
After a check, Nudge may add one of these messages:
| Message | What to do |
|---|---|
| "The AskNudge code is on … and nothing blocks it: open a page of your site once, then re-check." | The snippet is in place. Open a page of your site, then click Re-check installation. |
| "The AskNudge code is not in the HTML of … Paste it and publish the site…" | Paste the snippet and publish. With Google Tag Manager or a script added by JavaScript, this message is expected: open a page, then re-check. |
| "We could not open … to check it. Check that the site is published and public." | The page is not reachable from the internet (unpublished, password-protected, private network). |
| "Too many checks in a row. Try again in … min." | The check is rate limited per workspace. Wait the number of minutes shown. |
Check it yourself
- Open your published site (not the editor or preview of your site builder) in a private window, without browser extensions.
- Wait for the chat bar at the bottom of the page.
- If it does not show, open the browser's developer tools, Console tab, and look for the messages below.
| Console message | Meaning | Fix |
|---|---|---|
[AskNudge] Missing data-org or [AskNudge] Missing data-form | An attribute of the snippet is missing or empty. | Copy the snippet again from the app and replace it. |
[AskNudge] Unknown form: workspace/form | The two values do not match a Nudge form. | Copy the snippet again from Agents › Website Agent › Copy the snippet. |
Refused to load…, Refused to connect…, Refused to frame… naming app.asknudge.ai | Your Content Security Policy blocks Nudge. | See Content Security Policy. |
| No message at all | The snippet may not be on the page, or Nudge chose not to show the widget. | See the checklist below. |
To confirm the snippet is on the page, view the page source and search for widget/loader.js.
Why the widget does not show
Go through this list in order:
The snippet is on the published page
The site is published after pasting, the snippet is in the site-wide code (not on one page only), and it is pasted once. Caches (plugin, host, CDN) are cleared.
The Website Agent is on
If the Website Agent is Paused or Inactive in Agents, the snippet loads nothing. Set it back to Active.
Your workspace can serve visitors
The widget only runs with an active plan or trial. It also stops for the rest of the month when your plan's monthly conversations are used up, and comes back on its own on the 1st. Check Billing.
The page is not excluded
Excluded URL patterns (Where it appears on the Appearance screen) and device targeting hide the widget on matching pages. Test on a page that is not excluded.
Cookie consent is not pending
With Wait for cookie consent turned on in the form's widget settings, the widget stays hidden, and does not report the visit, until consent is given. Accept cookies on your site, or see cookie consent for the call your consent tool must make.
You have not already converted in this browser
With Hide if already converted on (the default), a visitor who has already sent the form no longer sees the widget in that browser. If you tested the form yourself, use a private window.
Nothing blocks the requests
A Content Security Policy, an ad blocker or a privacy extension can block app.asknudge.ai. Test without extensions, then see Content Security Policy.