Start troubleshooting by identifying the affected domain, page, environment, and product component. Check whether the issue involves installation, authentication, scanning, reporting, or remediation before changing site settings.
Installation or script does not load
- Confirm the licensed domain and account-specific installation code.
- Check browser Network and Console for failed script requests.
- Review Content Security Policy, caching, tag-manager publish status, and duplicate installation.
- Test a clean browser session and the correct environment.
See Install Pluro on WordPress (Theme header.php) and Install Pluro via Google Tag Manager (GTM).
Scan or report access problems
- Confirm the page is registered/licensed and the scan completed.
- Check the user’s Organization Hub role and domain assignment.
- Try opening the specific report using the entity menu.
See HTML Report page functionality.
Dynamic page or SPA issues
A site that changes content without a full reload may need additional testing for initialization, route changes, and dynamic content. The SPA article includes example API placeholders and must not be copied as an official integration API without verification. See Pluro Accessibility in SPAs (React & Angular).
Behavior Scan extension issues
Check extension enablement, authorization, page URL, and recording scope. Never send secrets or unredacted logs. See Pluro Behavior Scan Support.
Before contacting support
- Record the exact error message and steps to reproduce.
- Include the page URL only if it is not confidential.
- Specify browser, environment, and extension version where relevant.
- Sanitize logs and screenshots to remove private information.
Product verification before publication: Verify current support contact channel, error texts, script URL and current fixes for each documented issue.