Symptoms: The SharkEyes widget does not appear, or the invisible protection doesn't trigger.
Check the Script Tag:Ensure the <script> tag is placed correctly in your HTML and the URL is correct.
Ad-Blockers:Some aggressive ad-blockers or "Privacy" extensions might block external scripts. Try disabling them to see if the widget appears.
Console Errors:Open your browser's Developer Tools (F12) and check the Console tab. If you see a 404 or Connection Refused error, our CDN might be temporarily unreachable or blocked by your firewall.
Content Security Policy (CSP) Issues
Symptoms:The console shows an error like: Refused to load the script because it violates the following Content Security Policy directive.
If your website uses a CSP header for security, you must whitelist SharkEyes domains to allow the script to run.
Solution:Add the following to your CSP configuration: script-src https://api.sharkeyes.dev; connect-src https://api.sharkeyes.dev
"Form Submission Blocked" (False Positives)
Symptoms:A legitimate user is unable to submit the form and sees an error message from SharkEyes.
Automation Tools: Ensure the user isn't using automation tools, VPNs with high-risk scores, or "Headless" browser modes.
Cookie/Storage PermissionSharkEyes requires access to local browser storage to verify the session. If the user has disabled all cookies/local storage, the check may fail
Conflict with Other Scripts
Symptoms: The "Submit" button doesn't work at all, or other JavaScript on your page stops working.
Event Interference If you have another script that uses event.preventDefault() or event.stopImmediatePropagation() on your form, it might conflict with SharkEyes.
Solution:Ensure the SharkEyes script is loaded with async defer so it doesn't block other resources.