Websites and builders
Any other builder
Stickybeak works with builders that let you add a <script> tag. Add it once in a shared site setting, then publish.
Find the code setting
Look in site settings for Custom code, Code injection, Head code, Header scripts, Tracking code, Analytics, SEO → Advanced or Integrations. Paste this in the head for every page:
<script
defer
data-site="YOUR_SITE_ID"
data-domain="example.com"
src="https://app.usestickybeak.com/_cfw/s.js"
></script>Use the site ID and domain from Stickybeak Settings. The end of the body also works.
Check what the builder supports
| Option | Result |
|---|---|
| Site-wide head or body field | Best option. |
| Per-page code | Add it to every page or a shared template. |
| Embed or HTML block | Works only when placed directly in the page. Stickybeak does not run in an <iframe>. |
| Google Analytics or Meta Pixel ID only | Cannot load Stickybeak. |
Field strips data- attributes | Use the script-building version. |
Publish and verify
Custom code usually runs only on the published site. The domain must match the one in Stickybeak; preview and staging domains do not count unless you add that domain. Open the published site in a private window, then follow Verify your install.
Track goals
If the builder supports custom attributes, add data-goal to a button or link. Otherwise redirect forms or checkout to a thank-you page and add ⚙ Settings → Goals → a page visit. See Custom goals.
Client-side navigation
Stickybeak records history.pushState and back or forward route changes. Hash-only changes are not new pageviews. See Single-page apps.
Troubleshoot
- Check whether custom code needs a paid plan.
- Do not use an iframe embed.
- Publish after changing code.
See Troubleshooting.