Will ClikSora slow my site down?

The script is 14.8 KB gzipped and loads asynchronously, so it never blocks rendering. rrweb is only downloaded when session recording is switched on for your project.

Does session recording work with a single-page app?

Yes, with no router integration. ClikSora detects History API route changes itself, so React, Vue, Angular and Next.js apps report page views and user journeys correctly out of the box.

Can my team see visitors' passwords?

No. Password and card fields are blocked at capture — they are not masked after the fact, they never enter the recording at all. Every other input is masked in the browser before anything is transmitted.

Who on my team can watch session recordings?

Whoever you choose. The viewer role gets analytics but not replay, because a recording is the visitor's own screen. You can grant or withhold replay access per person.

What happens to recordings over time?

They are deleted permanently once past your retention window, which you set per project. Deletions are logged, so you can always show what happened to a recording.

Does ClikSora share data with third parties?

No. ClikSora uses rrweb for DOM recording and runs its own analytics engine. There is no Google Analytics, PostHog or Matomo in the path.

Built on rrweb 2.2.0

See what your visitors actually do

Session replay, heatmaps and analytics for your website — from one script tag. No backend integration, no tag manager, no code changes to your pages.

Start free — no card needed Try it on yourself

14.8 KB gzipped · one tag to install · no code changes

Session replay · USER_1001 · 5:03

2:01 / 5:03 Page Click

Drops into anything that serves HTML

Plain HTML Core PHP Laravel WordPress CodeIgniter React Vue Angular Next.js

Three ways to see the same visit

Numbers tell you something changed. Recordings tell you why. ClikSora collects both from the same script, automatically.

Session replay

Watch a real visit back, pixel for pixel. Jump straight to a click, a page change or a JavaScript error from the timeline — no scrubbing through dead air.

•Seek, speed control and skip-idle
•Markers for clicks, pages and errors
•SPA route changes stitched in

Heatmaps

Where people click, and how far down they read. Desktop and mobile are kept apart — a click at the same coordinate means something different in each.

•Click density per page
•Scroll depth and drop-off
•Separated by device and viewport

Automatic analytics

Visitors, sessions, pages, clicks, scroll depth, journeys and devices — collected without you defining a single event.

•Page views, including SPA routes
•Rage clicks and dead ends
•Your own events via track()

Installed in about a minute

Paste one tag before </head>. That is the whole integration — there is no server-side SDK and nothing to call from your code.

1 Add your website Name it and enter your domain. You get a project key straight away.
2 Paste the snippet Into your layout, your theme header, or public/index.html.
3 Watch it verify itself The install page waits for your first event and confirms it live.

Identifying your users is optional: ClikSora.identify('USER_1001') ties sessions to your own IDs when you want it. Read the SDK reference →

layout.html

<!DOCTYPE html>
<html>
<head>
  <title>Your website</title>

  <!-- ClikSora -->
  <script
    src="http://localhost/cliksora/sdk/v1/cliksora.min.js"
    data-project="YOUR_PROJECT_KEY"
    async></script>

</head>

async — never blocks your page rendering.

Private by default, not by configuration

Masking happens in the visitor's browser, before anything is sent. The real values never exist in a recording — not on our servers, not in a backup, not in an export.

Every input masked

Text, email, phone and number fields are replaced before transmission. On by default, for every project.

Credentials never captured

Password, hidden, one-time-code and card-autocomplete fields are blocked outright, along with Stripe and Razorpay payment frames.

Tokens stripped from URLs

The URL fragment goes unconditionally — OAuth and SPA tokens live there — and sensitive query parameters are redacted.

Browser signals respected

Do Not Track and Global Privacy Control are honoured. No project setting can override a visitor who has opted out.

Consent when you need it

Switch a project to consent-required and nothing records until your own banner allows it.

Retention you control

Recordings are deleted permanently when their window closes. Set it per project, down to a single day.

ClikSora uses rrweb for DOM recording and nothing else. Your visitors' data is not passed to Google Analytics, PostHog, Matomo or any other analytics platform — there is no third party in the path.

Pricing

Priced on recorded sessions. Start free, and move up only when you outgrow it.

Free

One website, for trying ClikSora out.

Free

1,000 sessions/month
1 website
7-day recording retention
1 team member
Heatmaps included

At the limit: collection pauses until the month resets.

Start free

Starter

Two websites and a month of recordings.

INR 999 /mo

10,000 sessions/month
2 websites
30-day recording retention
3 team members
Heatmaps included

At the limit: analytics continue, new recordings pause.

Choose Starter

Growth

Five websites, ninety days of history.

INR 2,999 /mo

50,000 sessions/month
5 websites
90-day recording retention
10 team members
Heatmaps included

At the limit: everything continues — extra sessions at INR 50 per 1,000.

Choose Growth

Business

Twenty websites, six months of history.

INR 9,999 /mo

200,000 sessions/month
20 websites
180-day recording retention
50 team members
Heatmaps included

At the limit: everything continues — extra sessions at INR 40 per 1,000.

Choose Business

Every plan includes session replay, heatmaps, automatic analytics and the full privacy controls. Change or cancel whenever you like — a downgrade that would put you over your new limits is refused rather than quietly deleting anything.

Questions people actually ask

Will ClikSora slow my site down?: The script is 14.8 KB gzipped and loads asynchronously, so it never blocks rendering. rrweb is only downloaded when session recording is switched on for your project.
Does session recording work with a single-page app?: Yes, with no router integration. ClikSora detects History API route changes itself, so React, Vue, Angular and Next.js apps report page views and user journeys correctly out of the box.
Can my team see visitors' passwords?: No. Password and card fields are blocked at capture — they are not masked after the fact, they never enter the recording at all. Every other input is masked in the browser before anything is transmitted.
Who on my team can watch session recordings?: Whoever you choose. The viewer role gets analytics but not replay, because a recording is the visitor's own screen. You can grant or withhold replay access per person.
What happens to recordings over time?: They are deleted permanently once past your retention window, which you set per project. Deletions are logged, so you can always show what happened to a recording.
Does ClikSora share data with third parties?: No. ClikSora uses rrweb for DOM recording and runs its own analytics engine. There is no Google Analytics, PostHog or Matomo in the path.

Find out what your analytics is not telling you

Add one tag, then watch a real visit back. Free to start, no card.

Create your account