Guardian JavaScript Implementation and Error Codes

Quickly identify and resolve Guardian JavaScript errors while monitoring implementation bstatus in the Telemetry dashboard.

📌 Note: This is only for users of Privacy Edge Protection & Blocking

⚠️ Install Privacy Edge Protection and Blocking

If you haven't installed the Guardian JavaScript on your website yet follow these instructions to do so.

How to Check the Status of Your Guardian JavaScript Implementation

To ensure the Privacy Edge protection is working, it's crucial that the JavaScript is correctly implemented. You can verify this on the Telemetry dashboard, where the status is displayed at the top right.

Guardian Error

Clicking the button will open a flyout with more details about the error and suggested solutions.

If the JavaScript is implemented correctly, the status at the top right corner will show green, indicating everything is functioning properly.

Guardian JavaScript Error Codes

Several errors can cause blocking issues. Refer to the table below to review them.

Error Code	Error Code Description	Color	How to Remediate Error Code	How to Confirm Error Code Has Been Remediated
not-found	Could not find a guardian script on ${origin}, ensure it is present on your page.	Red	Add the Guardian script element to the site as shown in the Privacy Edge site settings.	Ensure the warning is no longer present on the guardian status panel.
multiple-guardians	Multiple guardians have been found on the page, you should only use one.	Yellow	Ensure there is only one Guardian script tag on the page.	Ensure the warning is no longer present on the guardian status panel.
missing-scripts	Using "async", "defer", or "preload" attributes on scripts can cause the guardian to miss them. Remove the attributes to make sure the guardian can intercept them properly.	Yellow	Remove “async” and “defer” attributes from scripts, to ensure the Guardian can intercept requests caused by the script.	Ensure the warning is no longer present on the guardian status panel.
missing-attributes	The guardian needs to have the "crossorigin" attribute, set to "anonymous".	Red	Add crossorigin=”anonymous” to the Guardian script element.	Ensure the warning is no longer present on the guardian status panel.
wrong-protocol	The guardian needs to be loaded with the "https" protocol.	Red	Ensure the guardian URL starts with https://	Ensure the warning is no longer present on the guardian status panel.
wrong-guardian	The guardian on the site uses the wrong ID, use "${siteId}" instead.	Red	Ensure the Guardian script URL matches the one provided in the Privacy Edge site settings.	Ensure the warning is no longer present on the guardian status panel.
wrong-position	The guardian must be the first script on the page to ensure every other script can be intercepted	Yellow	Reorder your scripts to ensure the guardian always comes first.	Ensure the warning is no longer present on the guardian status panel.
non-blocking	The guardian must not have "async", "defer" or "preload" attributes ensure every other script can be intercepted	Yellow	Remove any “async” or “defer” attribute from the Guardian script element.	Ensure the warning is no longer present on the guardian status panel.