Troubleshooting

Check that the script tag has a valid data-project key and sits before </body>. Open the browser console and look for [PinMarks] messages. Also check the project's domain restriction and your visibility settings.

Screenshots use a fallback chain: the PinMarks browser extension (if installed), the browser's own screen capture (if turned on for the project), a server-side render, and finally an in-browser DOM capture. Cross-origin iframes and some CSS effects may not render in the last fallback. Installing the extension gives the most accurate result. For sites behind a login popup, set Basic Auth under Widget → Screen capture.

Your Content Security Policy probably blocks the script. Allow the PinMarks domain in script-src and connect-src, and exclude widget.js from JS minification, combining and delay in caching plugins.

Open Project → Widget → Developer tools. Console logs are on by default (last 100 entries). Network requests need the Pro plan or above and only record failed requests (status 400+ or network errors).

Confirm data-project matches the key in Settings exactly. In the browser Network tab, a POST to /api/feedback that returns 4xx means the key is wrong or the project is inactive.