Install Coruve on Framer

• 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.
• Edit access to the Framer project’s settings. Look for Site settings → General → Custom code.

A Framer site navigates on the client: moving from / to /pricing does not reload the browser, so a script that only reports on page load reports your whole site as one visit to one page.

The Coruve tracker watches the browser’s own history API — it wraps pushState and replaceState and listens for the back button — so each route change is recorded as its own page view. You do not need to instrument anything, and there is no router integration to install.

If you would rather send page views yourself, turn the automatic ones off:

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

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 Framer, give the element a name or ID you can select, then add this to the end-of-body custom code field:

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

This listens on the document rather than on the element itself, which matters on Framer: elements are added and removed as you navigate, and a listener attached to one that later gets replaced stops firing silently.

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? Custom code does not run on the canvas or in preview. This is the most common cause by a wide margin.
2. Did the snippet go in the head field? The end-of-body field works too but reports later.
3. 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.
4. Only ever one page view? Check you pasted the whole snippet. Route changes are handled by the tracker file itself, so a partial paste that loads nothing will still record the first page and nothing after it.
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 or edited — re-copy it from your dashboard rather than retyping it.

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