Docs

Session recordings and heatmaps

Watch how a visitor behaved on your landing: mouse movement, scrolling, clicks and taps, played back like a video. This works much like Microsoft Clarity or Yandex Webvisor, except the recordings stay on your own server. Each landing also gets a click heatmap and a scroll map.

Since v1.8.3 recordings also cover whole sites, not just landings: an organic site (SEO traffic, your own service pages) with the tracker script on every page records across pages β€” one visit is one recording, with page transitions in the player and a click heatmap per page. See Recording a whole site below.

Switching it on

  1. Open the landing β†’ Session recording tab.
  2. Tick Record sessions on this landing.
  3. Choose what share of visitors to record: 5 / 10 / 25 / 50 / 100 %. Visitors are picked at random, but the choice is fixed per click (one click is either always recorded or never).
  4. Choose how long to record: until you switch it off, or 1 hour / 24 hours / 3 days / 7 days. When the time runs out, recording stops by itself and the recordings already made stay.
  5. Click Save, the usual landing save button.

The tab shows a live estimate built from the landing's real traffic over the last 24 hours, for example: "about 120 recordings a day, roughly 18 MB".

Bots and safe-page visitors are never recorded. The server decides before the page is sent, so those visitors don't even get the recorder script.

Recording a whole site (organic traffic)

For a site that is not a landing β€” a service site living on SEO, direct and social traffic β€” recording is switched on at the campaign level:

  1. Put tracking.js on every page of the site, between <head> and </head> (the snippet is in the campaign's Tracking tab). Use tracking.js for this β€” kclient.js and kclient.php don't support multi-page sessions or the consent API.
  2. Open the campaign β†’ Integrations tab β†’ Session recordings card.
  3. Same settings as a landing: the share of visitors (for a busy site 5–10 % is usually enough β€” every page of a visit costs disk), how long to record, and a live estimate from the campaign's real traffic.
  4. Tick Multi-page site: one click per visit if you also want the visits glued β€” see the next section.

A visit is then recorded across pages: the player shows the transitions, the list shows how many pages the visitor opened and which was first and last, the click heatmap gets a page selector (each page has its own map), and the recordings list can filter by campaign, by traffic source (Google / Bing / Yandex / social / direct), by a page substring and by multi-page only.

The campaign switch also covers clicks that reach a landing without its own recording settings β€” but a landing you have ever configured for recordings keeps full control of its own clicks (its switch off means off).

One click per visit

Without this, every page of the site registers its own click in the campaign β€” the same as it always was. With Multi-page site: one click per visit ticked, a visitor moving through the site's pages is one click: statistics stop being inflated by page views, and the recording glues into one session.

The glue has guards, so a paid click is never swallowed by a remembered one:

For EU visitors, session recording needs the visitor's consent. Tick Start only after cookie consent in the campaign card, and until the visitor agrees nothing is written β€” not even clicks for the heatmap. The recorder wakes up from your cookie banner with one call:

window.OrbitraReplay && OrbitraReplay.consent();

The window.OrbitraReplay && … guard matters: tracking.js defines the stub OrbitraReplay on every page, but your banner can fire before it loads β€” the guard makes that safe. Two equivalent alternatives:

Once given, the consent is remembered, so later pages of the visit record from the start. Clearing it when the visitor withdraws is your banner's job. Consent mode gates what is written; the form-field masking described under Privacy works in every mode.

Where recording works

WhereHow
A landing uploaded to Orbitra (ZIP / editor), or an action landing "Show HTML"Automatic
An external landing with tracking.js / kclient.jsAutomatic: the script loads /replay.js when the Click API response says this click is recorded
An external landing with kclient.phpAutomatic: a current kclient.php prints the recorder tag at the end of the page. You can also place it yourself with <?php echo $client->replayScript(); ?>
A whole site with tracking.js on every pageAutomatic (v1.8.3): the campaign-level switch in the campaign β†’ Integrations covers every page of the visit
A campaign that redirects straight to the offerNot possible: there is no page to record

Multi-page gluing (?_subid= continuation) and the consent stub exist only in tracking.js; kclient.js and kclient.php record their single page but don't glue visits and don't expose OrbitraReplay.

Watching recordings

βš™ β†’ Logs β†’ Session recordings. Filters: landing, campaign, period, device (desktop / mobile), traffic source (Google / Bing / Yandex / social / direct, derived from the referrer), a page substring (matches the entry or the last page of the visit), multi-page only, minimum duration, went to offer, converted, with rage clicks. Each row shows the time, country and device, landing and campaign, duration, clicks (with a πŸ”₯ badge for rage clicks), scroll depth, the outcome (conversion / went to offer / left) and the file size; multi-page visits show a "N pages" badge with the first β†’ last path.

Every column header sorts the list (click again to flip the direction), and the list is paged with a page-size selector at the bottom.

Deleting. Tick rows to select them, or tick the header box to select the whole page. A bar appears with Delete (N) and Clear selection. When there are more pages, it also offers Select all recordings matching these filters (N), which selects every recording behind the current filters on all pages at once. So "delete all mobile bounces under 5 seconds from landing X" is: set the filters β†’ tick the header β†’ Select all matching β†’ Delete. Each row also has its own trash icon, and the storage panel has Delete this landing's recordings and Delete all recordings.

The player has play/pause, a timeline with red marks at every click, speeds of 1Γ— to 8Γ—, and Skip inactivity, which jumps over pauses where nothing happened. The click card in the traffic log also gets a Session recording button when that click was recorded.

Rage click: three clicks within 0.7 s on the same spot. Usually it means a button or element doesn't respond, which is worth fixing.

Click heatmap and scroll map

Open it from the landing's recording tab, from the campaign's recordings card, or with the Click heatmap button in the recordings list once a landing or campaign is selected.

The page behind the map is drawn from the newest recording of that device type (for a picked page β€” from its frame inside that recording). No request goes to the live site and no click is logged.

What to look for

A few ways recordings pay off in day-to-day buying:

Recording 10 % for a day or two is usually enough to see the pattern. You don't need 100 % running all the time.

Storage limits

The limits are shared by everything that records β€” landings and campaigns alike. They are shown on the landing's recording tab, on the campaign's card and under the size button in the recordings list:

Safety rails that cannot be switched off:

A typical recording takes 50–300 KB (it is the page structure plus changes, not video). The card shows the average of your real recordings and how many fit in the chosen limit.

Cleanup runs at most once a minute, driven by incoming recordings and by opening the list. There is no cron to add and no server command to run after the update.

Privacy

Troubleshooting

The tab says "Recording is on" but the list stays empty.

"The recording is too short to play". The visitor left before the first page snapshot was sent (usually under a second). This is normal for a share of bounces.

Multi-page visits still show as separate clicks. The One click per visit glue needs all three: the switch ticked in the campaign card, tracking.js (not kclient) on every page, and the visitor actually navigating the site β€” an entry from an ad, a bookmark or another site starts a new click on purpose, so paid clicks are never glued. Also check the 30-minute window: after a long pause the next page starts a new click.

The replay looks unstyled or images are missing. The replay loads images and fonts from the landing's own URLs. If the landing's files were deleted or replaced after the visit, old recordings can't show them.

New recordings stopped. Check the storage card: if the server disk has less than 1 GB free, recording pauses until you free space or lower the limit.

A recording shows LIVE. The visitor is still on the page. Batches arrive every few seconds, so the recording keeps growing until they leave (30 minutes at most).

Technical notes

← Previous
Conversion popups
Next β†’
Content gallery
View source on GitHub: github.com/fenjo26/Orbitra.link/wiki
All guides
Docs

Quick start: your first campaign

The short path: install the tracker, create a campaign, and get your first clicks and conversions in under an hour.

Read guide β†’
Docs

Installation and updates

Install Orbitra on a fresh Ubuntu or Debian server with one command, and update to new versions safely.

Read guide β†’
Docs

Migrating from Keitaro

Move campaigns, offers, sources and domains from Keitaro to Orbitra in one click β€” what transfers and what to check.

Read guide β†’
Docs

Migrating from Binom

Move campaigns and streams from Binom to Orbitra: what transfers automatically and what to set up by hand.

Read guide β†’
Docs

Feature overview

Everything Orbitra can do: campaigns and streams, cloaking, landings, PWA, postbacks, costs, reports and integrations.

Read guide β†’
Docs

Campaigns and streams

The complete reference: campaign settings, stream types, schemas, rotation, filters, test links and every option explained.

Read guide β†’
Docs

Cloaking

Full cloaking reference: detection layers, global settings, per-stream filters, verdicts and reports.

Read guide β†’
Docs

Browser check

How the JS check catches bots, VMs and emulators through contradictions in the browser environment.

Read guide β†’
Docs

Landing pages

Landing types, the {offer} macro, the JS adapter, LeadForge and multi-offer landings β€” the complete reference.

Read guide β†’
Docs

PWA and Web Push

Build installable PWA apps and collect push subscribers: settings, icons, events and notifications.

Read guide β†’
Docs

PWA Funnel

A multi-step PWA funnel: install prompts, event tracking and re-engagement notifications.

Read guide β†’
Docs

Conversion popups

Show real conversion events as on-page popups: setup, triggers and placement.

Read guide β†’
Docs

Session recordings and heatmaps

Replay real visits and see click and scroll maps. Storage limits and privacy notes.

Read guide β†’
Docs

Content gallery

Central storage for icons, screenshots and creatives used across PWAs and landings.

Read guide β†’
Docs

Creatives library

Store creatives with subid tracking and test them across campaigns.

Read guide β†’
Docs

External PWA and Telegram channels

Publish PWAs to external domains and run Telegram channels as a traffic source.

Read guide β†’
Docs

Postbacks and conversions

Incoming postbacks, conversion statuses and types, and outgoing S2S postbacks to your traffic source.

Read guide β†’
Docs

Costs

Import spend from Facebook, TikTok and Google Ads, or update it via API and cron β€” and how the revenue aggregator works.

Read guide β†’
Docs

Push and pop networks

Working with push and pop traffic sources: feeds, zone optimization and the zone killer.

Read guide β†’
Docs

Facebook / Meta

Cost import from Meta Ads and the Conversions API: server-side events with deduplication.

Read guide β†’
Docs

Dolphin / Fbtool

Receive Facebook costs through the Dolphin (Fbtool) API in real time.

Read guide β†’
Docs

FB comment cleaner

Bulk-moderate comments under Meta ads: hide, delete and filter by keywords.

Read guide β†’
Docs

Traffic sources and affiliate networks

Catalog of 50+ traffic sources and 440+ networks: templates, parameters and postback URLs.

Read guide β†’
Docs

Reports, logs and metrics

The report builder, saved reports, click logs and every metric explained.

Read guide β†’
Docs

Domains and SSL

Add domains, DNS, free Let's Encrypt certificates, redirects, parking and every switch on the page.

Read guide β†’
Docs

Cloudflare

How to run campaign domains through Cloudflare: DNS, SSL modes and what to turn off.

Read guide β†’
Docs

Administration

Users, roles and permissions, security settings, geo databases, updates and system health.

Read guide β†’
Docs

Telegram bot

Manage the tracker from Telegram: stats, conversions and alerts in chat.

Read guide β†’
Docs

MCP: an AI assistant in the tracker

Connect Claude or any MCP client to Orbitra and manage campaigns with plain-language commands.

Read guide β†’