Install Coruve on Webflow

• A Coruve project. Your project ID is on Settings → Project in the dashboard. It is not a secret — it ships in the page of every site that uses Coruve, by design.
• Permission to edit the Webflow site’s settings. Look for Site settings → Custom code.

Clicks on links and buttons are already recorded. You only need this if you want a named event — something like pricing_cta_clicked — that you can build a funnel on.

In Webflow, add an element ID to the button, then put this in Footer code (site-wide or on the page that has the button):

<script>
  document.addEventListener("DOMContentLoaded", function () {
    var el = document.getElementById("pricing-cta");
    if (!el) return;
    el.addEventListener("click", function () {
      window.Coruve && window.Coruve.track("pricing_cta_clicked", { plan: "pro" });
    });
  });
</script>

window.Coruve is available as soon as the tracker has loaded, and the snippet queues calls made before that, so an early click is not lost.

Coruve sets no cookies and no cross-site identifier. It does not follow your visitors to anybody else’s site, because it has nothing to follow them with.

It does use your visitor’s browser storage for three things: a session identifier, shared across that visitor’s tabs on your site and expiring after 30 minutes of inactivity; — by default — a small buffer holding events that failed to send, so a visitor on a bad connection is not simply lost; and a cached copy of your project’s capture switches, so the tracker knows what you have turned on without an extra request on every page load. The buffer is capped and expires within a day, and the switches are your settings rather than anything about the visitor.

One option turns all three off — the buffer is cleared and never rewritten, the session identifier falls back to living in memory for the length of a tab, and the switches are re-read from the compiled defaults on every page. Add it to the _CORUVE.init line in your snippet:

_CORUVE.init("proj_YOUR_ID", { apiHost: "https://ingest.coruve.com", offlineBuffer: false });

1. Did you publish? Saving custom code does not deploy it. This is the most common cause by a wide margin.
2. Are you on a paid Webflow Site plan? Custom code is not published on the free staging domain.
3. Did the snippet go in Head code, site-wide? Footer code works too but reports later; a single page’s custom code only covers that page.
4. Is the project ID exactly right? Compare it character for character with Settings → Project. A wrong ID sends events to nowhere and looks identical to no events at all.
5. Are you blocking yourself? A content blocker or your own self-exclusion setting will hide your own visits. Try a different browser.
6. Any console errors? Open your browser’s developer console on the published site. An integrity error means the snippet was altered in transit or edited — re-copy it from your dashboard rather than retyping it.

Still stuck? Tell us what you see and include the published URL.