Morph DocsSnippet Issues
Troubleshoot Morph runtime snippet problems — not connected, key mismatch, and more.
The Morph runtime snippet is a <script> tag injected into your Framer site's <head>. If it's not working, personalization won't appear on your published site.
"Not connected" status
The plugin can't find a Morph snippet in your project's custom code.
Fix: Go to the Account tab in the plugin and click Add Snippet. This injects the runtime script into your Framer project's <head> section.
"Key mismatch" status
A Morph snippet exists but it's using a different site key than your current account.
Common causes:
- You signed in with a different Morph account
- You rotated your API key and the snippet wasn't updated
- The project was shared and another user connected their account
Fix: Click Update Snippet in the Account tab. This replaces the old site key with your current one.
Snippet not working after publish
If the snippet shows as "Connected" in the plugin but personalization isn't working on the published site:
-
Check browser DevTools — open your published site, open DevTools (F12), go to the Network tab, and look for a request to
/api/runtime/. If it's returning a no-op script (/* morph: inactive */), your account may be paused or the site is deactivated. -
Check the Console — look for any JavaScript errors from the Morph runtime.
-
Verify rules are active — paused or draft rules won't be included in the runtime script.
-
Hard refresh — browsers may cache the old runtime. Try Ctrl+Shift+R (or Cmd+Shift+R on Mac).
Manually checking the snippet
You can verify the snippet by going to your Framer project settings → Custom Code → Head. You should see something like:
<script src="https://app.morph-app.com/api/runtime/YOUR_SITE_KEY" defer></script>If it's missing or has the wrong URL, use the plugin's Account tab to re-inject it.