How can we help?Setup, the AI, privacy and billing.

Add your site's address, then paste one script tag anywhere in your site's <head>. Clerion recognises WordPress, Shopify, Webflow, Squarespace, Wix and Next.js from the page itself and shows the exact steps for yours. It works on any other site or framework too. Data starts flowing within about a minute, and your numbers fill in from the first visitor.

If you can paste a line of text, you can install Clerion. There is no tag manager, no event configuration, and no SDK. If someone else edits your site, send them the snippet from the install screen: they get the line and the steps for your platform, and their reply comes to you. Pageviews, performance, errors, and SEO signals are collected automatically from the moment the script loads.

An email address you can confirm a link on, and your site's address. That is all the setup asks for. Then one line goes into your site's head, by you or by whoever edits the site. Every account starts on the 14-day trial the moment you sign up. 14-day trial, no card to sign up. A card is only asked if you start a paid plan trial from the upgrade modal.

Straight away if you import your history (from your site list or Settings), because Clerion writes a first briefing as soon as the import lands. Without an import, Clerion works from the first visitor and the briefing gets sharp once Clerion has about a week of data, rather than guessing from a day of noise. The AI is on the trial and the paid plans.

Open your own site in another tab. The install screen updates on its own, and Clerion emails you when the first visit lands, so you know even if the snippet went in on someone else's machine. The live pulse on Overview updates every 30 seconds, so your visit shows up almost immediately. If nothing arrives, check that the snippet sits inside <head> on the page you loaded and is not injected through a tag manager. Still nothing? Ask Clerion in the app: the AI walks through the likely causes with you, and priority support is one panel away.

No. Pageviews, sessions, clicks, scroll depth, forms, outbound links, file downloads, time on page, and Core Web Vitals are all tracked out of the box. Custom conversion events are there when you want them, not a prerequisite.

Yes, two ways. The moment you add your site's address, Clerion reads your homepage and shows what it can already tell: title, description, main heading, whether robots.txt shuts out AI crawlers like GPTBot and ClaudeBot, structured data and response time. And every account has a sample site called Parsel, an AI support agent with a full year of traffic behind it, so you can read real numbers and a real AI briefing on day one.

For setup, yes. The dashboard needs a bigger screen, so below about 768 pixels wide Clerion doesn't show it. But you can add your site from your phone and email the snippet to yourself or your developer, to paste from a laptop. Tracking on your site carries on regardless, so nothing is lost while you get to a bigger screen.

Yes. A site switcher sits at the top of every screen, and site limits follow your plan: 1 on Free and Solo, 3 on Starter, 10 on Growth, unlimited on Business.

You may see inflated pageviews on that page. Keep one snippet per page, remove the duplicate, and counts return to normal from the next visitor onward.

Yes. The install screen already shows the steps for your platform and can send the snippet to whoever edits your site. If you are still stuck, email hello@getclerion.com with your site and we will tell you exactly where the line goes, or check it for you once it's live.

The easiest way is the free WPCode plugin: open Code Snippets, then Header & Footer, and paste the snippet into Header. If you would rather edit the theme, paste it into header.php just before </head>, in a child theme, since a parent theme update can overwrite header.php.

Open Online Store, Themes, then the ⋯ menu and Edit code. Open layout/theme.liquid and paste the snippet just before </head>. It loads on every storefront page, including checkout-adjacent pages your theme controls.

Go to Site settings, Custom code, and paste the snippet into Head code, then publish. Webflow applies it site-wide, so one paste covers every page.

On Squarespace, open Settings, search for Code Injection, and paste it into Header. On Wix, go to Settings, Custom Code, Add Custom Code, paste it, and pick All pages and Head. Wix only allows custom code on a premium plan with your own domain. Both apply it site-wide.

Paste the snippet inside <head> in app/layout (or pages/_document on the pages router), or render it with next/script using the afterInteractive strategy, then deploy. Client-side route changes are counted as pageviews, so a single-page app behaves like any other site.

Almost certainly. Clerion needs nothing more than the ability to add one line to your HTML head. Framer, Ghost, Astro, Hugo, Laravel, Rails, Django, and hand-written HTML all qualify.

You can, but we would rather you didn't. Ad blockers block GTM itself on a large share of devices, so loading Clerion through it hands back the accuracy you installed Clerion to get. Paste the line directly instead.

Only if you run a strict CSP. In that case allow the Clerion script source and its collection endpoint in your script-src and connect-src directives. The exact hosts are shown with your snippet in the dashboard.

AI founders first: people building AI products who run their own site and have no analyst. It counts referrals from ChatGPT, Perplexity, Claude, Gemini and Copilot as their own channel, writes the reading for you, and needs no consent banner. Indie makers and small teams get the same product.

In the US federal government, yes. An executive order signed on 29 September 2026 directs agencies to say super intelligence, or SI, in place of artificial intelligence. It binds government documents, not companies. Nothing in Clerion changes: the AI traffic channel, the briefings and the quotas are the same product under either name, and Clerion is reachable at clerion.si as well as getclerion.com.

Clerion reads your site's signals: traffic, conversions, errors, SEO changes, and writes a short briefing with the highest-impact fix at the top. It runs when you open a tab, not on a schedule, and opens with a verdict you can click to unfold the whole thing. Press Find patterns whenever you want it done again. You can also ask questions any time with ⌘K or the Chat tab.

No. The AI never types a figure itself. It chooses which metric matters and Clerion fills in the value from your actual data, so every number in a briefing is real. Every sentence is also clickable and opens the real numbers behind it.

Every change is scored by estimated impact on your sign-ups or revenue, based on how many visitors it touches and where it sits in your funnel. The biggest leak goes on top, and you can always open the pages and sessions behind the ranking.

Press Cmd+K anywhere in Clerion for the spotlight, or open the Chat tab for a longer conversation. Type the question as you would say it, for example "why did mobile bounce go up last week?". Answers are grounded in your own data, come with suggested follow-ups, and your recent chats sit in the sidebar.

Real ones. "Give me a Facebook ads plan for my weakest regions." "What happened on 12 July and why the spike?" "Give me a mobile conversion fix list." "Which SEO fixes are worth my weekend, and draft the missing meta descriptions." "Which bug should my developer fix first? Write the ticket." "Write the traffic section of my investor update."

When you open a tab, not on a schedule. There is no daily or weekly send. Closed date ranges are kept for about a month; a rolling window is carried for up to a fortnight unless the numbers move by five percent or more. Press Find patterns for a fresh read at any time.

No. Clerion stores no personal data in the first place, and none is sent to the AI. It reads aggregate signals: pages, sources, devices, geographies, errors, and performance.

Yes, once you tell it. Adding a site only asks for the address, so Clerion starts from a general brief. In Settings you pick an industry from 10 supported categories and write an owner's brief: your goal in a sentence plus a little context. Both go into every briefing, which is why the advice reads like it is about your site rather than a generic checklist.

Yes, in Settings. You write your goal in a sentence and a short description of the site, starting from one of ten industry presets, and you can change both whenever you like. Every briefing is ranked by how far a finding sits from that goal.

One piece of written intelligence: a briefing, a signal, an error diagnosis, or a site audit. Ask Anything questions are counted separately, so asking questions never uses up your briefings.

Every claim is clickable. It opens the underlying view with the real numbers, the pages, and the sessions that produced it, so you can check the AI's reading rather than take it on faith.

Third-party frontier models, accessed under commercial terms. No personal data is sent to them, and the model layer is a meaningful part of what paid plans cost, which is why pricing can move if model prices do.

Clerion speaks English, German, French, Spanish, Italian and Dutch. The app, the AI's briefings and answers, and every email follow your account's language. It is picked up from your browser when you sign up, and you can change it any time in Settings.

Ad blockers block Google Analytics on a large share of devices, so GA undercounts. Clerion isn't blocked, which is why sites that switch typically see 10 to 40% more visits. Your new numbers aren't inflated; the old ones were missing people.

Yes, and most teams do at first. The two scripts don't conflict. Run both for a few weeks, get comfortable with the gap between them, then switch the old one off.

By a keyed hash computed in memory from request attributes, never a stored identifier on the visitor's device. Nothing is written to their browser, and the raw inputs are discarded rather than saved.

Yes. Bots and crawlers are detected, excluded from your numbers, and never counted toward your billing. Overview shows you how many were blocked, so you can see the noise you are not paying for.

Because definitions differ between analytics tools, and Clerion also measures scroll depth and active time rather than treating every single-page visit as a failure. Compare trends inside one tool rather than absolute figures across two.

Country, region, and city level, derived through an EU-based lookup service under a data processing agreement. It is not precise location, and it is never stored against a visitor's IP address.

The visitor pulse refreshes every 30 seconds, so it reads as live without hammering your browser. Signals and briefings are written when you open the view they belong to.

Yes. Referrals from ChatGPT, Perplexity, Claude, Gemini, Copilot and other AI assistants are measured as their own traffic channel, next to direct, organic, social, email, paid and referral. Most tools leave these visits buried inside referrers; Clerion breaks them out so you can watch the channel grow.

Yes, from your site list or Settings, whenever you like. Export your reports from Google Analytics 4 and drop the CSV in. Coming from Plausible, Fathom, Matomo, Simple Analytics, Umami or anything else, ask priority support inside the app and we bring the history across for you. The GA4 file is parsed in your browser and never leaves it. Only daily and monthly totals and capped top lists are sent, up to about two years of daily rows and ten years of monthly. One import per site, replaceable, and deletable whenever you want.

Pass a value with the custom event that means someone paid, for example trackEvent('purchase', { value: 49, currency: 'USD' }). Clerion credits each payment to the source of the visit it came from, so ChatGPT and the other assistants get their own row beside search and social. On the default cookie-free setup Clerion keeps no identifier between visits, so someone who came from ChatGPT and later paid after typing your address counts under Direct. With the consent banner on, visitors who accept are credited to their first visit in the period instead. The full setup is in the guide: getclerion.com/docs/revenue-by-source. Clerion does not connect to Stripe or another payment provider, so it shows revenue from your events, not MRR, churn or refunds.

Add data-exit-question to your snippet with the pages you care about, for example data-exit-question="/pricing,/signup", or "*" for every page. When a visitor on one of those pages moves the pointer up to leave, after at least five seconds there, a small card asks why, with five answers: too expensive, not sure what it does, missing a feature, something broke, or just looking. Each visitor is asked once per page. It shows on desktop only, because phones have no leaving gesture to read. The answers appear on the Custom events page and in your briefing. The full guide: getclerion.com/docs/exit-question.

Add one call to the end of your deploy job: a POST to https://api.getclerion.com/api/v1/deploys with your account key as a Bearer token and a body of {"websiteId": "site_...", "label": "v1.8"}. The Errors page then sets each deploy's error rate and conversion rate for the 24 hours before against the 24 hours after, and the briefing can name the deploy behind a change. A deploy under six hours old is marked as still settling. The account key comes from Your model on every plan, and replacing it there stops the old one everywhere. The full guide: getclerion.com/docs/deploy-markers.

Three or more clicks on the same element, each within 0.7 seconds of the last, count as one burst. Clerion records them on any element, not only links and buttons, so an image or a label that looks clickable and does nothing shows up. The Errors page lists them by page and element, with the number of sessions. The full guide: getclerion.com/docs/rage-clicks.

Revenue by source, deploys, rage clicks and exit answers are read from the raw events of the period, up to 150,000 events per site. A busier site over that in the range you picked sees a note instead of the cards. A shorter date range can bring them back.

Pages, entry and exit pages, referrers, countries, regions, cities, languages, timezones, device types, operating systems, browsers, ISPs, connection types, screen resolutions, and pixel density. There is also an interactive world map and a user flow graph.

Click any row in any table and every view filters by it. Filters combine, live in the URL, and are shareable, so "mobile visitors from Germany on the pricing page" is three clicks and a link.

Today, 7, 30 or 90 days, 12 months, or any custom range inside your plan's memory, each comparable against the previous period, week, month, quarter or year. Ask for a range longer than your plan holds and Clerion clamps it and offers the upgrade rather than failing quietly.

Yes. Custom conversion events report uniques, completions, conversion rate, and summed monetary value, so you can see revenue next to the traffic that produced it.

Yes: sessions to product views to cart adds to checkouts, with the conversion rate at each step. Ready-made commerce events cover product views, add to cart, checkout start, search, and wishlist.

Tag your links with UTM parameters and Clerion breaks out source, medium, campaign, content, and term. On-site search queries, outbound link clicks, and file downloads are captured alongside them.

Yes. Average scroll depth, active time on page, and clicks per session sit next to the raw counts, so you can tell a page that gets read from a page that gets loaded.

A GitHub-style 52-week activity heatmap shows the shape of your year, with best-day records, growth streaks, and your projected monthly pace beside it.

Yes. Load time, first paint, and time-to-interactive are scored against Core Web Vitals thresholds, with an AI note on how to improve them. Clerion also detects your stack: framework, CMS, HTTPS, and PWA status.

Yes. Filters and date ranges live in the URL, so any view you are looking at is a link you can paste to someone else.

No. The same one-line snippet captures JavaScript exceptions and console errors passively, so broken checkouts and failing scripts surface in the same place as your traffic.

As a log viewer under Observability, with ERROR, WARN and INFO levels, deduplicated by fingerprint, searchable, and cross-referenced with how many sessions each one affected. Worst first, and Diagnose writes an explanation for any single error when you ask for one.

Yes. Each error carries breadcrumbs of the visitor's last actions leading up to it, which is usually the difference between reproducing a bug and guessing at it.

The snippet reads each page's titles, headings, meta tags, canonical, Open Graph tags, word count, links, and schema markup. That powers a health read on your whole site, Healthy, Fair, or Needs Work, with a diagnosis per page.

Yes. Every error diagnosis has a copy-the-fix-prompt button, and you can ask Clerion to write the ticket, with the likely cause on your stack included.

No. Clerion stores no cookies and no personal data by default, so there is nothing for visitors to consent to under GDPR, CCPA, or PECR. If you choose to enable the optional consent mode for persistent visitor recognition, Clerion ships its own customisable banner.

No. No device fingerprinting, no cross-site tracking, no personal data stored, and no cookies by default. That is the design, not a setting you have to find. The only cookie Clerion can write is the consent record, and only if you enable the optional banner and a visitor accepts.

On EU infrastructure. Location lookups also run through an EU-based service under a data processing agreement, so your visitors' data stays in the same jurisdiction.

Never in raw form. IP addresses are hashed and discarded in memory, and no raw address is written to the database at any point.

Yes, both are honoured automatically. Visitors who signal that they do not want to be tracked are not tracked, with nothing for you to configure.

Yes, by construction rather than by configuration. No personal data, no cookies, EU storage, right-to-erasure deletion, full export, and automatic purging past your retention window. The detail is on our GDPR compliance page.

Each has its own page setting out how Clerion meets it, linked from the footer under Trust and compliance. The short version is the same in every case: there is no personal data to argue about.

Very little. Because Clerion collects no personal data, most sites add a single sentence noting that anonymous, aggregate analytics are collected. We provide suggested wording in the dashboard you can paste directly.

Email hello@getclerion.com and tell us what your legal team needs. We will send the paperwork and answer questions about our processors directly.

No. We never sell or share analytics data with third parties, and we do not build an advertising profile from it. Your data exists to answer your questions.

Only as a landing place. Every account starts with the 14-day trial. 14-day trial, no card to sign up. A card is only asked if you start a paid plan trial from the upgrade modal. When it ends without a plan you keep one site on a free tier with 30 days of memory and no AI. It is a safety net, not a plan we sell.

One visitor loading one page once. We filter bots before counting, so crawlers don't eat your limit. Plan limits are monthly: Solo 25,000, Starter 100,000, Growth 350,000, and Business 1,000,000.

Solo $14, Starter $29, Growth $59, and Business $99 a month, or 20% less paid yearly. They differ by pageviews, sites, AI volume, and history: Growth and above include unlimited AI, with 13 months of history on Growth and 24 on Business. Every plan, free included, connects your own model over MCP.

Every plan includes every screen and the AI. Moving up gets you more pageviews, more sites, more AI and longer memory, not a feature you were locked out of.

Yes. Annual works out at a little over two months free against the monthly price, and you can switch between the two in the app.

Tracking never stops and nothing is throttled. At 80% of your pageview allowance we send one heads-up email for the month with the next tier alongside it, and that is the whole of it.

Yes, from inside the app. Upgrades apply immediately and are prorated; downgrades take effect at your next invoice. Cancelling asks what went wrong and offers a word with the founder first. Cancel during the trial and you drop to free straight away with tracking carrying on. Resume any time and your plan comes back. Your data stays exportable either way.

Payment runs through Dodo Payments in an overlay, so you never leave Clerion. Changing plan, updating your card, downloading invoices and cancelling are all in the app, without emailing anyone.

It might. A meaningful part of paid pricing is the cost of third-party AI models, which we do not control. If prices move, we email you before anything changes on your account.

Email hello@getclerion.com. Cancelling keeps your access until the end of the period you paid for, and if something was billed in error we will put it right.

Tell us about your project at hello@getclerion.com. We are a small team and we would rather look at your situation than publish a rule that fits nobody.

By plan: 30 days on Free, 90 days on Solo, 12 months on Starter, 13 months on Growth, 24 months on Business. Data past your window is purged automatically, which is part of how Clerion stays compliant by default.

Email and password, with strong-password enforcement and email verification, or sign in with Google. Both reach the same account.

Yes. Every report has an export in Settings, as CSV or JSON, filtered by site and date range, up to five a day. There is also a self-serve full data export for GDPR. Your data is yours and there is no export tier.

Delete the account from Settings and your data is removed permanently. That is right-to-erasure deletion, not a hidden archive we keep on a backup tape.

Delete the one line you pasted. Nothing else is left behind: no cookies, no local storage, no leftover requests.

A usage page shows exactly where you stand on pageviews, sites, AI quotas, and data retention, with the date your monthly allowance resets.

There is a full trackEvent API for sending your own events, plus ready-made commerce events. A read API for pulling your data out programmatically is on the roadmap; export handles it in the meantime.

Use the built-in panel in the app to send bug reports and feature requests without leaving what you were doing. Priority support is on every plan, and a real person replies. Anything urgent can go straight to hello@getclerion.com.

Email hello@getclerion.com and a person who works on the product will answer, usually within a day. There is no ticket queue and no first-line script.