Clerion
  • What it doesFeaturesUse cases
    Set upQuickstartMCP serverSecurity
  • Docs
  • Pricing
  • Privacy-first toolsPlausibleFathomMatomo
    Large platformsGoogle AnalyticsMixpanelCloudflare Web AnalyticsPostHogAmplitude
  • LearnGuidesWritingHelp centreChangelog
    CompanyAbout usContact
Sign inStart free trial
  • What it doesFeaturesUse cases
    Set upQuickstartMCP serverSecurity
  • Docs
  • Pricing
  • Privacy-first toolsPlausibleFathomMatomo
    Large platformsGoogle AnalyticsMixpanelCloudflare Web AnalyticsPostHogAmplitude
  • LearnGuidesWritingHelp centreChangelog
    CompanyAbout usContact
Sign inStart 14-day trial

Getting started

  • Introduction
  • Quickstart
  • Install on your platform
  • Import your history
  • Check your installation

Tracking

  • Custom events
  • Revenue by source

Visitor insight

  • Exit question
  • Rage clicks

Releases

  • Deploy markers

Integrations

  • MCP server

Reference

  • Script tag
  • JavaScript API
  • Configuration options
  • Consent banner
  • Dashboard filters
  • Export and retention
Docs menu

Getting started

  • Introduction
  • Quickstart
  • Install on your platform
  • Import your history
  • Check your installation

Tracking

  • Custom events
  • Revenue by source

Visitor insight

  • Exit question
  • Rage clicks

Releases

  • Deploy markers

Integrations

  • MCP server

Reference

  • Script tag
  • JavaScript API
  • Configuration options
  • Consent banner
  • Dashboard filters
  • Export and retention

Docs / Reference

View as Markdown

Configuration options

The script tag starts the tracker with its defaults, and those defaults suit almost every site. When you need to change one, load the script with data-disabled="true" so the tag does not start a tracker, then start your own:

<script src="https://api.getclerion.com/sdk/clerion-analytics.js" data-disabled="true"></script>
<script>
  window.addEventListener("load", () => {
    window.clerion = new ClerionAnalytics({
      apiKey: "YOUR_API_KEY",
      websiteId: "YOUR_WEBSITE_ID",
      trackScroll: false,
      exitQuestion: ["/pricing"],
    });
  });
</script>

Assign it to window.clerion so custom events and the rest of the JavaScript API work as documented. Start exactly one tracker per page.

Required

OptionWhat it is
apiKeyYour tracking key, starting cle_. The tracker throws without it.
websiteIdYour site id, starting site_.

What is tracked

All on by default.

OptionDefaultWhat it controls
autoTracktrueEverything below, plus pageviews and session starts. false records only what you send yourself.
trackClickstrueClicks on links and buttons, with the element's tag, id and classes. Never its text.
trackScrolltrueScroll depth, at the thresholds below.
scrollDepthThresholds[25, 50, 75, 100]The depths, in percent, at which a scroll event is recorded.
trackFormstrueForm focus and submit, by form id or name. Never the values.
trackOutboundtrueClicks on links to other sites, with the destination.
trackFileDownloadstrueClicks on links to files such as PDFs and images.
trackPerformancetrueLoad time and Core Web Vitals.
trackErrorstrueJavaScript errors and console errors, with the visitor's last actions.
exitQuestion[]Paths on which leaving visitors are asked why. See Exit question.

Rage clicks are recorded whenever autoTrack is on; there is no switch for them alone.

Sending

OptionDefaultWhat it controls
enableBatchingtrueEvents are queued and sent together, five seconds after the last one, or at once when the page is hidden or closed. false sends each event as it happens.
heartbeatInterval120000Milliseconds between flushes of anything still queued. Two minutes.
sessionTimeout1800000Milliseconds of inactivity after which the next action starts a new session. Thirty minutes.
apiUrlderivedWhere events are sent. Derived from the script's own address; leave it unset.

Sampling

Leave these at their defaults for anything you count as a conversion.

OptionDefaultWhat it controls
samplingRate1.0The share of visitors whose events are recorded. Errors, session starts and ends, and pageviews are always recorded. Custom events and rage clicks are not, so a rate below 1 undercounts them.
detailedEventsSamplingRate0.1For visitors who are sampled, the share of clicks, scroll depths and form focuses that are kept. Keeps high-volume events light.

Consent and privacy

OptionDefaultWhat it controls
requireConsenttrueWhether a recorded refusal stops tracking. With the consent banner, a visitor who clicks Reject is not tracked.
allowWithoutConsenttrueBefore a visitor has chosen, track the session without keeping anything between visits.
consentCookieNameclerion_consentThe cookie the banner writes and the tracker reads.
consentCookieExpiry365Days a choice, and the visitor id that comes with acceptance, are kept.
ignorePrivacySignalsfalseGlobal Privacy Control and Do Not Track stop tracking. Set true only with your own legal basis for it.

Debugging

OptionDefaultWhat it controls
debugfalseLogs each batch of events to the console as it is sent, and any tracker error.
sourceMapUrlnullWhere the tracker can fetch source maps to resolve error stack traces.
enableSourceMapResolutiontrueWhether it tries.

From the script tag

The tag itself reads only data-api-key, data-website-id, data-api-url, data-auto-track, data-debug, data-disabled and data-exit-question. Every other option needs the pattern at the top of this page. See Script tag.

PreviousJavaScript APINextConsent banner

Something missing or wrong here? Write to hello@getclerion.com, or ask from inside the app.

On this page

  • Required
  • What is tracked
  • Sending
  • Sampling
  • Consent and privacy
  • Debugging
  • From the script tag

Clerion (“Clerion”), at getclerion.com and clerion.si, is website intelligence for AI founders: web analytics, AI-assistant traffic, conversions and revenue by source, SEO and AI-readiness, speed and errors from one script tag. It finds the patterns in the data, ranks what changed and tells you the fix. AI is now also called SI, super intelligence; the channel is the same. It sets no cookies, stores no personal data, needs no consent banner, and holds data in the EU.

Every briefing is written from your own numbers, and every figure in it comes from your data rather than from the model. Clerion is a software product and does not provide marketing, legal or advisory services. We have no ad budget: if Clerion helps you, telling a friend does more for us than any campaign could.

© 2026 Clerion. Independent and self-funded.

XLinkedInMedium

Product

  • Features
  • Use cases
  • Docs
  • Quickstart
  • MCP server
  • Pricing
  • Sign in

Compare

  • vs Google Analytics
  • vs Plausible
  • vs Fathom
  • vs Matomo
  • vs Mixpanel
  • vs Cloudflare
  • vs PostHog
  • vs Amplitude

Resources

  • Learn
  • Writing
  • Help centre
  • AI crawler checker
  • What is SI?
  • What is Clerion?
  • Changelog
  • Sitemap

Company

  • About us
  • CareersHiring
  • Brand
  • Contact
  • Security
  • Privacy policy
  • Terms

Compliance

  • GDPR
  • Schrems II
  • ePrivacy
  • PECR
  • COPPA
  • CCPA
  • Our data journey