Install ClickCues, verify it, start collecting feedback.
Use this guide to connect one project, confirm the widget is reaching that project, send your first report, and troubleshoot the most common setup issues.
Before you start
You need a ClickCues project, access to the website where the widget should load, and the install snippet from the exact project that should receive feedback.
Open your project in Project Settings → Install Widget. Every project has its own public widget token, so avoid reusing a snippet from a different workspace or test project. Regenerating that token also invalidates the current guest feedback link for the project until you update it.
Usually no developer workflow required If your platform has a shared custom-code field, site settings area, or footer script area, you can usually install ClickCues without changing your build pipeline. Custom app shells, restrictive CSP rules, and authenticated environments may still need developer help.
Install the widget
Paste the snippet once before the closing </body> tag in your site template or global layout so it loads on the pages where you want feedback.
<script src="https://rpojgouloqkzbgaxfxyr.supabase.co/functions/v1/get-widget?token=YOUR_PROJECT_TOKEN&v=2.4.1"></script>Preferred placement
Install the script once in the shared template that renders your published pages, then publish the site before testing.
Shared code areas
If your CMS or builder provides a site-wide code area, use that single placement instead of pasting the script into multiple pages.
- Use the project-specific token shown in Project Settings. The live token you copy is a project-scoped UUID, even though the guide shows a placeholder.
- Publish or load the actual page after adding the script. Builder previews do not always behave like the final page.
- Install the snippet only once per page. The widget guards against duplicate initialization, but keeping one script tag avoids confusing setup issues.
- If you regenerate the project token later, replace the snippet on the site so new page loads use the current token.
Verify the connection
After the site is published, run the connection check from Project Settings → Widget Connection Check. The check looks for recent widget heartbeat events for this project, recent runtime errors, and whether detected domains line up with the configured project URL.
Run the check
Open the selected project, run the check, and use the result as a signal that the widget has recently loaded for that project.
Successful result
A connected result means the project recorded recent successful heartbeats. It does not inspect your page source or prove which snippet is currently installed in the DOM.
If it fails
Reload the live page, confirm you are testing the intended project, and rerun the check after the page has had a chance to load the widget again.
Use the live route you want reviewed On sites with client-side routing or dynamic shells, open the actual published route you want clients to review before running the connection check again. The check looks back across recent heartbeat data, including the most recent 24 hours.
Submit the first feedback item
Once the widget is installed, open the website, launch the ClickCues feedback launcher, and submit a short test note from the page you want reviewed.
Open the installed page
Visit the page where the widget script is installed and make sure the ClickCues launcher appears in the configured position.
Leave a quick note
Open the widget, add a short title, and submit the report. The current widget supports click-to-pin feedback and optional screenshots or file attachments when the page can capture them.
Confirm it reached the dashboard
Return to that project in ClickCues and confirm the new item appears in the New column. New submissions are created with backlog status and should show up on the board shortly after submission.
Guest feedback is supported Clients do not need to create a ClickCues account just to submit feedback through the embedded widget or the project feedback link. Name and email are optional in the current guest-link flow.
Find and manage feedback
New submissions are created with backlog status. In the customer-facing workflow, that shows up in the New column. From there, your team can open the item, reply, assign it, set priority, and move it through the board workflow.
New
Newly submitted feedback starts here after it is created with backlog status.
To Do
Move accepted work here when it is ready to schedule.
In Progress
Use this when someone is actively working on the issue.
Resolved
Use this when the feedback item has been completed or closed in the workflow.
- Open a feedback item to review the title, details, screenshot, and any stored page or browser context.
- Reply in the dashboard when you need follow-up or want to document a decision.
- Assign a teammate and set priority so work does not get stuck in review.
- Move the item between the available workflow states as work progresses. Status changes persist through the current dashboard flow.
Troubleshoot setup
Most setup issues come down to one of these problems: the page never loaded the widget, the wrong project token was installed, the project is paused or disabled, the current domain is not allowed, or the page is outside the widget targeting rules.
Widget does not appear
Confirm the snippet was added once, the page actually loaded the script, the project widget is enabled, and the page is not excluded by targeting rules or a feedback deadline.
Connection check fails
Open the page again to trigger a fresh heartbeat, then rerun the check. The result may still reflect older heartbeat history if the project loaded successfully earlier.
Wrong project receives feedback
Replace the installed snippet with the one from the project that should receive the feedback, then reload the page so future events use that token.
Script installed more than once
Remove duplicate script tags from templates, page builders, or tag managers so you have one clear installation path to debug.
Strict Content Security Policy
If external scripts are blocked, review your CSP and confirm the page can load the ClickCues widget script and the network requests it makes.
Builder-specific code areas
Use one site-wide placement, publish the site, then verify from the final URL instead of relying on an editor preview.
Allowed domains or local testing
If your project has an allowed-domains list, make sure the tested hostname is covered. Localhost and local testing hosts are treated as valid test environments.
Guest link still works
The project feedback link stays independent from widget enabled and pause states, but it stops working if the token is regenerated, the workspace becomes read-only, or the feedback deadline has closed.
Still stuck? Email evander@clickcues.com and include the project name, the page URL you tested, and what the connection check reported.