Platform Compatibility

One script. Every platform.

Cayda's embed code is a single line of HTML. You paste it once, and it handles the rest — regardless of whether your site runs on WordPress, Squarespace, Shopify, or a fully custom stack. Here's how that works.

The problem with "just paste a script"

Most tools tell you to drop a snippet into your site and call it a day. And on a standard HTML website, that works fine — every page loads fresh, the script runs, everything connects.

But modern website builders don't work like that. Platforms like Squarespace, Wix, and some Shopify and Webflow setups use what's called single-page architecture. When someone clicks a link on your site, the platform doesn't load a whole new page. Instead, it swaps out the content and updates the URL in the background. It's faster for visitors, but it means any third-party script only actually runs once — on that very first page. Navigate anywhere else, and the script goes quiet.

What Cayda does differently

Our script is platform-aware. It doesn't just load and hope for the best — it actively listens for the specific way each platform transitions between pages, and adapts accordingly.

When your site navigates to a new page, Cayda detects the transition, cleans up notes from the previous page, rebuilds its interface if the platform replaced part of the page, and loads the correct notes for wherever your team member just landed. This happens automatically, every time, on every page.

How it works on each platform

Squarespace

Squarespace uses an internal system called Mercury for page transitions. When someone clicks between pages, Mercury swaps the content without reloading the browser. Most embedded scripts break here — they load on the first page and never fire again. Cayda listens for Mercury's own transition events, so it knows exactly when a page change happens and responds to it. Your notes show up on every page, not just the homepage.

Webflow + page transitions

Webflow sites that use standard navigation work instantly — each page loads fresh, and so does Cayda. But some Webflow sites use libraries like Barba.js or Swup for smooth animated transitions between pages. These libraries swap page content without a full reload. Cayda detects these transition events too, so it stays active even on heavily customized Webflow builds.

Wix

Wix templates come in two flavors: multi-page (full reloads) and single-page (content swaps). Cayda covers both. On multi-page Wix sites, it works on first load with zero configuration. On single-page templates, our polling system picks up URL changes and keeps everything in sync as visitors navigate.

WordPress & Shopify

These platforms typically do full page reloads on navigation, which means the script re-runs on every page automatically. WordPress users can install our one-click plugin or add the snippet manually. Shopify users add it to their theme layout file. In both cases, Cayda works across your entire site right out of the box.

Custom & static sites

If your site is a React app, a Next.js project, or plain HTML — the same script tag works. For single-page apps that use the browser's History API for routing, Cayda intercepts those navigation events directly. For everything else, there's a lightweight polling fallback that catches any page change within a second.

Three layers of detection

Rather than relying on a single approach and hoping it covers every case, Cayda uses a layered strategy. If one method doesn't apply to your platform, the next one picks it up.

1

Platform events

We listen for framework-specific signals — Squarespace's Mercury loader, Barba.js, Swup, Turbo, and Turbolinks. When one of these fires, we know a page just changed.

2

History API

For sites using standard browser navigation APIs — like React Router or Vue Router — we intercept those calls directly, so we're notified the moment the URL updates.

3

Universal fallback

A lightweight check runs every 800ms to catch anything the first two methods miss — proprietary loaders, hash-based routing, or platforms we haven't encountered yet.

Self-healing UI

Some platforms don't just swap content — they tear out and rebuild entire sections of the page. If Cayda's interface gets removed during one of these transitions, it notices within a second, rebuilds itself, and loads the right notes for the current page. Your session stays active. You don't have to re-authenticate. It just comes back.

None of this affects your visitors

All of this detection and rebuilding happens silently. The script is lightweight, runs only when an authenticated team member is present, and adds no overhead for regular visitors. No cookies, no tracking, no visible changes. Visitors will never know it's there.

Supported platforms

WordPress

WordPress

One click plugin install or manual snippet. Works with any theme.

Shopify

Shopify

Native Shopify app. One click install, no code required.

Squarespace

Squarespace

Works with Ajax / Mercury page loading. No need to disable it.

Webflow

Webflow

Project level custom code. Compatible with Barba.js transitions.

Wix

Wix

Custom Code settings. Works on both SPA and multi page templates.

Google Tag Manager

Google Tag Manager

Deploy as a Custom HTML tag. Fires on all pages via trigger.

Don't see your platform? Cayda's layered detection means it likely works already. And if it doesn't, reach out — we'll make sure it does.

Ready to try it?

Set up takes under two minutes. No credit card required.

Get started free