Use custom code only when you understand its source and purpose. Test it on a draft or duplicate project before relying on it publicly.
Steps
- For an embed in one location, use an HTML element. For code intended to run throughout the website, inspect the global code editor and place it in the appropriate section.
- Use the provider’s current embed snippet and replace only the documented identifiers. Keep private API credentials and account secrets out of browser-visible code.
- Preview the page: Sitejet does not execute custom JavaScript directly in the editing canvas. An empty editor placeholder alone is not proof of failure.
- If preview or live output fails, inspect the browser’s console and failed network requests. Check HTTPS resource addresses, required dependencies, and any consent controls before changing layout.
- Remove or disable only the new snippet in a saved test copy to establish whether it causes the problem. Check mobile layout and keyboard access after it works.
Check the result
Publish and repeat the test as a visitor, including the expected behavior before and after any relevant consent choice.
Before you continue
Code that depends on an external service can stop working independently of Sitejet. Do not bypass a visitor’s consent choice or remove unrelated security controls to load an embed.
Documentation for this guidance: help.sitejet.io — 24275957454999 Use custom HTML CSS and JavaScript code.
