Monitoring
Session replay
The browser SDK can record the page as the user saw it and upload the minute before an error or a bug report. Each project's Session replay setting in the dashboard decides when it records, so it works without code changes, also in Odoo. The recorder is a separate 61 KB add-on fetched from blipit.io only when replay is on, so the core script stays small.
1Choose when it records
Open the project in app.blipit.io and pick a Session replay setting. On errors and bug reports, the default for every project, keeps the last 60 to 120 seconds in the browser's memory and uploads them only when an error is captured or someone sends a bug report, then keeps recording; visits without a problem are never uploaded. All visits, sampled records the share of visits you choose (1 to 100%) from the start, whether or not anything breaks, and keeps the error buffer on the rest. Off loads nothing. Owners, admins and anyone who can edit the project can change it, and browsers pick up the change within about an hour.
2What is visible and what is masked
Masking happens in the browser before anything is sent. Typed values, page text, table cells and record names become asterisks, so a form field shows as Customer: ******. Labels and buttons stay readable so you can follow what the visitor did: form labels, legends, table and list column headers, captions, buttons, tabs, menu items, navigation links and, in Odoo, field labels, the status bar, notebook tabs, the app menu and control panel buttons. Even there, digits, dates, emails, links and @handles are masked, so a button reads Pay $**.**, and title, alt, aria-label and placeholder attributes are masked too. Anything inside a field value, table cell, kanban card, activity or chat stays masked even when it is drawn as a button, and kanban column titles are masked because they can be grouped values. Always masked, even inside a label or button: inputs, text areas, selects and their options, editable areas, table cells and field values, headings, breadcrumbs, the chatter, kanban cards, account, user and profile menus, and search and autocomplete lists. Images, video, audio, canvas, iframes and password fields become empty boxes of the same size, anything with data-blipit-block is blocked, and token-like values in the page URL are redacted. To mask every word as before, turn off Show labels and buttons in replays in the project's Session replay panel. Add data-blipit-mask to an element to always mask it, or data-blipit-unmask to show the text of one you choose; data-blipit-mask wins.
<div data-blipit-mask>Always masked</div>
<span data-blipit-unmask>Plan</span>3Watch a replay
Replays lists recordings by project, with or without errors, and by URL. The player has play, 1x, 2x, 4x, skip inactivity and a red marker per error that links to its issue. An issue whose latest event has a replay shows Watch replay.
4Override it in code
A replay option in Blipit.init wins over the project setting for that site: onErrorSampleRate (default 1) is the share of visits that keep the error buffer, sessionSampleRate (default 0) the share recorded from the start, and labels: false masks all text on that site. replay: false turns replay off on that site whatever the project says.
Blipit.init({
key: "<public key>",
release: "2026.09.28",
replay: { sessionSampleRate: 0.05, onErrorSampleRate: 1 }
});5Mobile apps: Android
Mobile session replay works in Android apps with blipit-android 0.3.0 or newer, and on Huawei devices too, because the SDK uses no Google Play services or Firebase. iOS, React Native and Flutter are coming. The same project setting applies: On errors and bug reports keeps the last 30 seconds in memory on the device and uploads them only when an error happens or someone sends a bug report; All visits, sampled records the share of app sessions you choose in full. Replay needs Android 8.0 (API 26) or newer; older devices still send errors, without replay.
implementation("com.github.blipit-io:blipit-android:v0.7.5")Blipit.init(this) {
key = "<public key>"
project = "<project id>"
}6Ask for consent first
Nothing is captured until your app calls Blipit.setReplayConsent(true); the default is false. Show your disclosure (below) and call it when the user agrees. The choice is stored on the device, so call it again only when it changes. Blipit.setReplayConsent(false) stops recording at once and discards the buffer, so offer it in your app's settings. Blipit.hasReplayConsent() returns the current choice.
allowButton.setOnClickListener { Blipit.setReplayConsent(true) }
replaySwitch.isChecked = Blipit.hasReplayConsent()
replaySwitch.setOnCheckedChangeListener { _, on -> Blipit.setReplayConsent(on) }7What a mobile replay captures
About one frame per second of your app's own screens, encoded on the device as a small H.264 video, plus taps, screen changes, breadcrumbs, the device model, Android version and app version. Other apps, the system UI, notifications and anything while your app is in the background are never captured: recording pauses as soon as the app goes to the background and stops after 30 seconds there. Blipit never uses an AccessibilityService or MediaProjection, so there is no screen-capture prompt and no foreground service. Video quality is lowered on metered (cellular) networks, and everything is sent over HTTPS to Blipit only.
8What is masked on the device
Masking happens on the device before a frame is stored: all text, all images, all text inputs (EditText and Jetpack Compose text fields), WebViews and video players are drawn as solid blocks. Set replayLabels = true in Blipit.init to keep labels and button text readable on View-based screens; text inputs and images stay masked, and Jetpack Compose screens stay fully masked. Add android:tag="blipit-mask" to a view to always mask it.
<TextView
android:id="@+id/balance"
android:tag="blipit-mask" />9Apps for children
Leave replay off in apps aimed at children (Google Play Families policy, COPPA, the Kids category on the App Store). Set childDirected = true in Blipit.init, or call Blipit.disableReplayForChildApp(); replay then never starts, even with consent.
Blipit.init(this) {
key = "<public key>"
project = "<project id>"
childDirected = true
}10Store compliance checklist
- Ask for consent before any capture: call Blipit.setReplayConsent(true) only after the user agrees.
- Show a prominent in-app disclosure before you ask, using the text below.
- Mention Blipit and session replay in your privacy policy; the AppGallery paragraph below works for every store.
- Fill in the Google Play Data safety form and the AppGallery privacy labels with the answers below.
- Keep replay off in apps aimed at children.
- Honour withdrawal: offer a switch in your app's settings that calls Blipit.setReplayConsent(false).
11Google Play Data safety answers
Use these answers in Play Console under App content > Data safety. The labels are the ones the console shows in English.
- App activity > App interactions: Collected, not shared, optional. Purposes: App functionality, Analytics.
- App info and performance > Crash logs: Collected, not shared. Purposes: App functionality, Analytics.
- App info and performance > Diagnostics: Collected, not shared. Purposes: App functionality, Analytics.
- Is all of the user data collected by your app encrypted in transit? Yes.
- Do you provide a way for users to request that their data is deleted? Yes.
12In-app disclosure to paste
Show this before you ask for consent, on its own screen or dialog with Allow and Not now buttons, and change the settings path to match your app.
- This app records a masked video of your screen and your taps for up to 30 seconds before an error or bug report, and sends it to our error monitoring provider Blipit to fix problems. Text, images and typed input are hidden. You can turn this off in Settings.
13Privacy statement for Huawei AppGallery
Paste this into your privacy statement and replace the parts in brackets; it works for Google Play and other stores too. In AppGallery Connect, declare in the app's privacy labels that a third-party SDK collects app activity (interactions) and diagnostics (crash logs), not shared and not used for advertising.
- Error monitoring and session replay. We use Blipit, an error monitoring service operated by Louward Labs FZC LLC (Ajman, UAE), as our data processor. With your consent, the app keeps a short, masked recording of the app's own screens (text, images and typed input are hidden on your device before anything is stored), your taps and screen changes, device model, operating system and app version. It is sent over an encrypted connection (HTTPS) only when an error occurs, when you submit a bug report, or for a small sample of sessions, and is used only to find and fix problems in the app. It is not sold or used for advertising. Recordings are deleted automatically after [7/14/30] days. You can withdraw consent at any time in [Settings > Privacy], and request access to or deletion of your data at [contact].
14App Store privacy label (for the iOS release)
For the coming iOS SDK. In App Store Connect under App Privacy, declare:
- Usage Data > Product Interaction: App Functionality, Analytics.
- Diagnostics > Crash Data and Other Diagnostic Data: App Functionality, Analytics.
- Not linked to the user's identity, unless you call Blipit.setUser; then mark it as linked.
- Not used for tracking.
Good to know
- Replays per month: Free 25, Solo 500, Team 2,500, Scale 5,000, kept 7 days on Free, 14 on Solo and 30 on Team and Scale. Once the month's replays are used, the project setting answers Off until the next month and nothing is billed.
- A recording stops after 60 minutes, 500 segments or 20 MB. Chunks go out every 10 seconds or at 1 MB, gzipped, and the last one when the tab closes.
- On websites the Blipit browser script records replays; in Android apps, the Blipit Android SDK sends them.
- Mobile replays share the monthly allowance and retention of web replays, and their video files are deleted with the replay.
Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.