Diagnose script loading and blocked requests
Use this guide when the banner or declaration does not load, or an integration remains unavailable after the relevant consent choice.
First confirm the affected page and whether its saved regional rules should display a banner.
1. Find the first relevant failure
Open the browser’s Network and Console panels, then reload the page. Look for the main Passiro script copied from Implementation and any failing resources it needs. Record the request status, initiator and console message. A successful download alone does not prove that the script executed or that consent behavior is correct.
2. Follow the actual error
Resource absent: inspect the published HTML and installation method. Check whether the CMS removed the code, the wrong template is being used, or an optimizer delays insertion.
HTTP 404: compare the requested URL with the current code from your account. Do not fix a path by guessing a different endpoint.
HTTP 401 or 403: investigate the affected service’s authentication or access rules. Do not assume these statuses automatically mean an Allowed Domains error.
HTTP 5xx or timeout: note when it happened, check the service status and repeat a controlled test. Record whether the issue affects one page or multiple page types.
CSP violation: identify the blocked resource and directive, then use the dedicated CSP guide. A report-only message does not itself block a resource.
Mixed-content or certificate error: use the intended HTTPS resource and fix the underlying deployment problem. Do not bypass the browser warning.
Client blocking or CORS error: investigate the reported cause. Compare a clean profile and the integration’s supported loading method; do not disable browser security as a fix.
3. Separate loading failures from intentional consent behavior
An optional integration can be deliberately blocked before acceptance. Compare no-choice, rejection and acceptance of the intended category. If it fails only after acceptance, inspect its initialization and consent-update handling. If it runs before the expected permission, check script order and consent controls.
Expected result: the loading issue is tied to a reproducible cause, corrected at its source, and followed by installation and consent tests.