No build step, no-code and website builders

The CDN route, builders that cannot run npm, and installing by hand.

On a website builder, follow its guide: Webflow, Framer, WordPress, Wix, Shopify, Carrd, Bubble, Google Tag Manager, and any other website, Squarespace included.

My builder will not install from npm. Is there another way?#

Yes. Instead of the npm package you import the SDK module from a CDN, with the exact version pinned in the import URL:

https://esm.sh/@heycatch/sdk@0.8.0

It goes inside a <script type="module"> block in the head of your page, and it carries your own project key, which sits on the Analytics, Install screen until your first install is confirmed, then behind the gear icon in the top right of the Product page. It is not a <script src> tag and there is no window.heycatch global, so a snippet shaped like that is not ours and can break your app at startup.

Pin the version. An unpinned URL re-resolves on every page load.

That route is web only. It does not work inside a mobile app at all: mobile apps have their own install, see the Mobile apps article.

An AI builder gave me a HeyCatch script tag that loads from a CDN and calls a window.heycatch global. Is that the right install?#

No. That snippet is not ours and could never work. There is no <script src> tag install for HeyCatch and our SDK never defines a window.heycatch global, so a builder that produced one invented it. It can also break your app at startup.

Two routes are real.

1. The npm package @heycatch/sdk: import the analytics namespace and call analytics.init with your project key at module scope in your root file, not inside a component or a hook.
2. Where npm is not available, an import of the same module from a CDN with the exact version pinned, https://esm.sh/@heycatch/sdk@0.8.0 today, written as a <script type="module"> block rather than a <script src> tag.

Your project key sits on the Analytics, Install screen until your first install is confirmed; once the install is confirmed, the key sits behind the gear icon in the top right of the Product page. The CDN route covers the web only and does not work for a native build.

Can I install analytics on Webflow, Wix, Squarespace or Framer?#

Yes. Each of these has its own step-by-step guide in this help centre, under Analytics install guides: Webflow, Framer, WordPress, Wix, Shopify, Carrd and Bubble, plus a guide for Google Tag Manager and one for any other website, which is the one to follow on Squarespace. Every guide has the same steps: what you need before you start, where your project key is, the code, where to paste it, publishing, and the "I've installed" check.

The guides cover your web pages only. Short links need one redirect rule on your site; Webflow, Framer and Wix have a redirect screen for it, and the Short links article covers the rest.

My product runs on a no-code platform where I cannot run the install prompt in a codebase. Can I still install analytics?#

Yes, if the platform lets you paste custom code into its head or its tracking field. What you paste is a <script type="module"> block that imports the SDK from a CDN with the version pinned, https://esm.sh/@heycatch/sdk@0.8.0 today, not a <script src> tag. If every click on your site loads a new page, which is how most website builders work, add requestBatching: false to its analytics.init call: without it visits from iPhones get lost. A site that changes pages without a full reload, such as one built on Framer, does not need it, which is why the Framer guide leaves it out. It carries your own project key from the install panel, which is the Analytics, Install screen until your first install is confirmed, then behind the gear icon in the top right of the Product page. Paste it in, save and publish, click around your site, then press "I've installed".

Two limits to expect on those platforms.

1. It covers the web version only. Most no-code builders do not allow custom code in the native iOS or Android build, so in-app behaviour there stays untracked.
2. Signup and payment events need server-side access that these platforms usually do not expose, so your funnel will show traffic rather than conversions.

Each website builder has its own step-by-step guide in this help centre, under Analytics install guides, and the code is in step 2 of every guide.

My project has no build step and cannot install npm packages. Can I still add analytics?#

Yes. Instead of installing the package, import the SDK as a module from a CDN in the head of your page, call analytics.init with your project key and set the install framework to web. It goes inside a <script type="module"> block: there is no <script src> tag and no window.heycatch global.

The code, with your key in place of YOUR_PROJECT_KEY:

<script type="module">
  import { analytics } from 'https://esm.sh/@heycatch/sdk@0.8.0';
  analytics.init({
    projectKey: 'YOUR_PROJECT_KEY',
    requestBatching: false,
    install: { framework: 'web', agent: 'other' },
  });
</script>

Four things matter on that route.

1. Pin the exact version in the import URL, https://esm.sh/@heycatch/sdk@0.8.0 today, because an unpinned URL re-resolves on every page load.
2. If your page sends a Content-Security-Policy, it has to allow both the CDN you import from and in.heycatch.ai, which serves the events endpoint and one static script the SDK loads. Without that the import or the events are blocked with no error.
3. It covers the web surface only, and a native build cannot use it at all.
4. If every click on your site loads a new page, which is how most website builders work, add requestBatching: false to analytics.init. Without it visits from iPhones get lost.

Your project key sits on the Analytics, Install screen until your first install is confirmed; once the install is confirmed, the key sits behind the gear icon in the top right of the Product page.

I do not build with an AI builder. Can I install the analytics SDK by hand?#

Yes. The manual integration reference is at heycatch.ai/agents.md, and for a native Swift, Kotlin or Flutter app at heycatch.ai/agents-native.md. They were written for AI agents so they are terse, but you can follow them manually. You also need your project key. Before your first install is confirmed it sits on the Analytics, Install screen in the sidebar; once the install is confirmed, the key sits behind the gear icon in the top right of the Product page.

Can I install the analytics SDK inside a Chrome extension?#

No. Manifest V3 forbids an extension loading code from a remote origin, so the CDN import cannot run inside one, and there is no local-only or bundled mode to fall back on.

Install it on your product's website instead.