Question 1

Why is the Engage widget not showing on my website?

Accepted Answer

The most common causes are a performance plugin delaying or rewriting the embed script, or an existing Content Security Policy (CSP) blocking the Engage script or API calls. Paste the snippet before , exclude widget.js from delay/defer optimizations, and purge site caches. If your site already sends a CSP, add the Scale2Rev host from your Engage Deploy page to script-src and connect-src, and allow 'unsafe-inline' in style-src. Do not create a new CSP for Engage.

Question 2

How do I know if CSP is blocking Engage?

Accepted Answer

Open browser DevTools → Console and look for refused script or connect errors mentioning Content-Security-Policy. Check the page response headers for a Content-Security-Policy header that omits your Scale2Rev host.

Question 3

Where should I paste the Engage embed code?

Accepted Answer

Paste the snippet from Engage → Deploy immediately before the closing tag on every public page. Use the exact Tenant ID and Site ID from that page.

Question 4

Why does Engage only load after I click the page, or show tenantId is required in the console?

Accepted Answer

WordPress performance plugins such as Flying Press, WP Rocket, and LiteSpeed can delay JavaScript until user interaction. The optimizer may rewrite your embed tag and inject a second script copy without data-tenant-id and data-site-id. Engage reads those attributes from the script tag that loads widget.js, so the launcher stays missing or fails after a click. Exclude your Scale2Rev host (for example scale2rev.com/widget/widget.js) from Delay JavaScript, combine, and defer settings, then purge the plugin cache — not only your browser cache.

Question 5

Does Engage work on Netlify or WordPress with caching plugins?

Accepted Answer

Yes, after the embed script is excluded from delay/defer optimizations and any existing CSP headers allow your Scale2Rev host. On WordPress, exclude the Scale2Rev widget script from JavaScript minify, combine, and Delay JavaScript in Flying Press, WP Rocket, LiteSpeed, or similar plugins, then clear site cache.

Widget not loading

Quick answers

Check for an existing Content Security Policy

Confirm the embed snippet

Caching and performance plugins

Symptom: launcher missing until click, then console errors

Not the same as missing knowledge base pages