# UXCam

> UXCam is a mobile-first product analytics and session replay platform for iOS and Android apps, with a newer web product alongside it. A native SDK autocaptures screens, gestures, and events with no tagging plan, and the dashboard turns that capture into session replays, touch heatmaps, screen flow diagrams, funnels, retention curves, and automatic UX issue detection for crashes, application-not-responding freezes, rage taps, and unresponsive gestures. The distinguishing fact in a category dominated by web-first tools is that UXCam was built for native apps first and treats the web as the extension, rather than the other way round. There is a permanent free plan of 3,000 sessions per month and a 14-day trial with 100,000 sessions, but UXCam publishes no dollar price for any paid tier: Starter, Growth, and Enterprise are all quoted.

- Category: Product Analytics & Session Replay (https://saastracker.org/categories/product-analytics)
- Website: https://uxcam.com
- Starting price: $0 on the permanent free plan (3,000 sessions per month); every paid tier is quote-only
- Free plan: 3,000 sessions per month that reset monthly and do not expire, two app keys, one dashboard capped at six reports, unlimited user licenses, chat support, and session recording, user analytics, and event analytics with basic issue filters for crashes, rage quits, and freezes. Heatmaps, advanced dashboards, app flow analytics, funnels, advanced filters, data export, rule-based recording, and third-party integrations are excluded.
- Free trial: 14 days with access to all platform features, 100,000 sessions, and 100,000 videos, no credit card required
- Founded: 2013, HQ: San Francisco, California, United States, Ownership: Independent, privately held and lightly venture-backed
- Profile last reviewed: 2026-08-30
- Canonical profile: https://saastracker.org/products/uxcam

## Overview

Almost every well-known tool in behaviour analytics started on the web. Hotjar, FullStory, Microsoft Clarity, LogRocket, and Heap all began as a JavaScript snippet, and their mobile SDKs arrived later as a port of a web-shaped architecture. UXCam went the other way. It was founded in 2013 to record what happens inside a native app, and everything about the product reflects that: sessions are structured around screens rather than URLs, heatmaps plot taps and swipes rather than mouse positions, the issue detector understands an Android ANR and an iOS crash, and the SDK is a mobile artefact measured in kilobytes rather than a tag manager entry. For a company whose product is an app, that difference is not cosmetic.

The working model is autocapture. You add the SDK, and without writing a single tracking call UXCam begins recording sessions, naming screens, drawing gesture heatmaps, and assembling the screen flow diagram that shows where people actually go. Custom events and user properties exist for the things autocapture cannot infer, such as a purchase value or a plan tier, but a team with no analytics engineer gets a usable picture in an afternoon. This is the same argument Heap and FullStory make on the web, applied to a surface where instrumenting events is considerably more painful because every change ships through an app store review.

The last two years have widened the product in two directions. In March 2025 UXCam shipped a web product analytics offering, extending the mobile feature set to sites and web apps, with heatmaps for web following in July 2025. In January 2026 it launched Tara AI, an assistant that watches sessions on your behalf, flags friction, and delivers a daily brief of what is breaking, which is aimed squarely at small teams that have replay data and nobody with time to watch it. Alongside those, multi-region data storage arrived in July 2025 (US and EU, with the United Arab Emirates added in November 2025), and an MCP integration in November 2025 that shortens SDK setup.

The honest counterweight is commercial rather than technical. UXCam does not publish a price for any paid plan. The free tier is real and permanent but deliberately thin, excluding heatmaps, funnels, app flow analytics, exports, and integrations, so the features that make the product interesting sit behind a sales conversation. Metering is on sessions captured, which means cost scales with how much people use your app rather than how many people you have, and the caps are hard: quotas reset monthly with no rollover, and reviewers report waiting out a month when they run out. UXCam remains independent, has raised only about $5.1M across early rounds, and reports roughly 79 employees, which is a smaller and more focused company than most of the names it is compared against.

## How it works

1. You add the UXCam SDK to your app. Native Android and iOS are the primary targets, with wrappers for React Native, Flutter, Cordova, Kotlin Multiplatform, Xamarin and MAUI, and NativeScript, plus a web snippet installable directly or through Google Tag Manager, Shopify, or WordPress. Integration is documented as a five minute job for a simple app, and the SDK is under 300 KB by UXCam's own figure, though verified reviewers consistently say a real integration with occlusion rules and screen tagging takes longer than the marketing number.

2. From the first launch the SDK autocaptures sessions: screens visited, gestures made, session duration, device and OS, app version, and connectivity. Screen names are detected automatically on native platforms and can be tagged manually where the automatic name is unhelpful, which matters because screen names are the spine of every downstream report. Custom events and user properties are added in code for the business facts autocapture cannot see.

3. Before any of that reaches a dashboard you configure privacy. Text fields are occluded automatically, individual views can be marked sensitive on Jetpack Compose and SwiftUI, whole screens can be hidden by inclusion or exclusion list, and blur rules can be applied per screen. Recording rules and random sampling then decide which sessions get captured at all, which is both a privacy control and the main lever you have over the session bill.

4. In the dashboard, quantitative and qualitative views are joined. Dashboards, funnels, retention reports, and segments answer how many, while session replay, heatmaps, and the screen flow diagram answer why. The link between them is the point: a funnel step with a 40 percent drop becomes a filtered list of replays of people who dropped, and a heatmap of the screen where they dropped, without leaving the tool.

5. Issue analytics runs continuously in the background, flagging crashes, UI freezes and ANRs, rage taps, rage quits, and unresponsive gestures, and pushing alerts to Slack or Microsoft Teams. Tara AI sits on top of the same data, watching sessions daily and writing a plain-language brief of what broke and where. Outbound, a REST API exposes sessions, users, and events, replay links can be attached to Intercom and Zendesk tickets, and event data can be enriched into Mixpanel, Amplitude, Segment, and Firebase.

## Best for

Product, design, and engineering teams at small and mid-sized companies whose primary product is a native iOS or Android app, who want session replay, touch heatmaps, screen flows, and crash and rage-tap diagnosis without writing a tagging plan, and who can either live inside the 3,000-session free tier or are willing to get a quote for anything more.

## Not the right fit for

- Teams whose product is a website or a web app first. UXCam's web offering only shipped in March 2025 and is the newer, thinner half of the platform; Microsoft Clarity, Hotjar, FullStory, and LogRocket all have far more history on that surface, and Clarity costs nothing.
- Buyers who need a published price to budget against. Every paid tier is quoted, so there is no way to model a year of cost from the website, and a small team that outgrows 3,000 sessions has to book a call rather than click upgrade.
- Companies that want diagnosis and remedy from one vendor. UXCam shows you the broken onboarding step but has no in-app guides, tooltips, checklists, surveys, feature flags, or experimentation engine, so acting on the finding means a second product such as Pendo, Appcues, or Amplitude.
- High-volume consumer apps on a fixed budget. Because the meter is sessions captured rather than users or events, a highly engaged audience is expensive by definition, and reviewers report the bill rising with usage in a way that is hard to forecast before you have run a month of real traffic.
- Engineering teams whose main need is frontend forensics. UXCam surfaces app logs and crash context, but it does not offer the console output, network waterfall, and application state inspection that LogRocket built its product around.

## Features

### Session replay and qualitative analysis

The part of the product UXCam is actually known for: watching what happened inside the app.

- **Native mobile session replay**: Video reconstruction of a user's session inside a native app, with a timeline marked by screen changes, gestures, events, crashes, and rage taps, so you can jump to the moment something went wrong rather than scrubbing through a recording.
- **Gesture heatmaps**: Touch, swipe, and scroll heatmaps drawn per screen rather than per page, including area selection to interrogate a specific region and filtering by gesture type or event. Heatmaps came to the web product in July 2025 and are excluded from the free plan.
- **Screen flow and journey analytics**: A diagram of the paths users take between screens, with path highlighting, drop-off points, and the ability to open the replays or the heatmap for any node. Screenburst extends this into conversion analysis and lets a funnel be built directly from an observed path.
- **Session and user segmentation**: Filters built on autocaptured properties (device, OS, app version, country, connectivity, session length, gesture count) plus custom event and user properties, so you can narrow thousands of recordings to the twenty that matter before watching any of them.
- **Recording rules and random sampling**: Conditional capture based on screens visited, events fired, crashes, duration, location, app or SDK version, and device model, plus percentage sampling. This is the main cost control, with the caveat that UXCam's own documentation warns retention analytics becomes unreliable under sampling.
- **WebView and hybrid support**: Documented handling for WebView content inside native apps and for hybrid frameworks, which matters for the large number of apps whose checkout or help centre is a wrapped web page.

### Quantitative product analytics

The charts side, which is competent but not why anyone chooses UXCam over Mixpanel or Amplitude.

- **Custom dashboards and templates**: Widget-based dashboards with team sharing, grouping by day of week, time of day, or hour, and five curated templates added in December 2025 for teams that do not want to design a dashboard from scratch. The free plan allows one dashboard with a maximum of six reports.
- **Funnels**: Ordered and unordered funnels with configurable conversion windows, cloning, and the ability to switch between session-based and user-based counting. Each step links straight to the replays behind the drop-off, which is the feature that justifies having funnels and replay in the same tool.
- **Retention and cohorts**: Retention curves with saved cohorts, answering whether a behaviour in the first session predicts return visits. Reliable only on unsampled data, which is a real constraint if you have turned sampling on to control cost.
- **Event analytics**: Trend and breakdown analysis on autocaptured and custom events, with the ability to create an event and a report directly from a session replay rather than shipping instrumentation first.
- **Users and activity filters**: A user-level view with performance and activity metrics, plus activity filters that segment by what someone did rather than only by what they are, added in April 2025.
- **Alerts and issue notifications**: Customisable alerts on metric thresholds and automatic notifications for crashes and issues, delivered to Slack or Microsoft Teams, so a spike surfaces without anyone opening the dashboard.

### Issue detection and AI analysis

Automatic diagnosis of app friction, and the layer that watches sessions when nobody on the team has time to.

- **UX issue detection**: Automatic flagging of rage taps, rage quits, unresponsive gestures, UI freezes, and application-not-responding events, each linked to the replays where they occurred. Basic issue filters for crashes, rage quits, and freezes are included even on the free plan.
- **Crash and ANR reporting**: Crash and handled-exception reporting with the session that produced it, plus a documented Firebase Crashlytics integration so a crash record in Crashlytics carries a link to the replay of the minute before it.
- **App logs**: In-app log capture for tracking errors and reproducing bugs against a specific session. Useful, but well short of a full frontend debugging surface with network and state inspection.
- **Tara AI product analyst**: Launched January 2026. Tara watches sessions daily, identifies friction patterns and drop-off points, answers plain-language questions such as why users abandon onboarding, and issues a daily brief. Prompt suggestions were added in February 2026. UXCam does not publish which plans include it or what usage limits apply.
- **Screen performance metrics**: Per-screen metrics on engagement time, gesture counts, and issue frequency, which is how you find the one screen responsible for a disproportionate share of frustration signals.

### Privacy, administration, and data access

The controls a buyer checks before an SDK that records screens goes into a production app.

- **Occlusion and masking**: Text fields are hidden automatically, individual views can be marked sensitive including on Jetpack Compose and SwiftUI, entire screens can be excluded or included by rule, blur rules can be applied per screen, and gesture recording can be disabled on hidden screens. This is the single most important configuration step and it is on you to get right.
- **Multi-region data storage**: Data can be stored in the United States or the European Union, chosen when an app is created, with the United Arab Emirates added in November 2025. Enterprise customers can set the region per app; everyone else inherits the region of their first app. Regions cannot be changed or migrated afterwards without deleting the app and re-keying the SDK.
- **Data export and REST API**: Documented REST endpoints for sessions, users, and events with filtering and pagination, plus formatted export of sessions, screens, events, and users for BI use. Both are excluded from the free plan.
- **Single sign-on and access control**: SSO has been available since April 2021 and multi-factor authentication is offered from the entry paid tier. Role granularity is a documented weak point: reviewers report that only the account owner can perform some actions, including stopping recording to prevent an overage.
- **Consent and compliance tooling**: Documented GDPR and CCPA guidance including consent management, opt-out, and deletion handling. UXCam states SOC 2 Type 2 certification and describes GDPR, CCPA, PCI, and HIPAA alignment; infrastructure runs on AWS with AES-256 encryption at rest and TLS in transit.
- **Data retention controls**: Session data and video are retained on separate clocks, with video always the shorter of the two. Enterprise reaches 60 months. Note that UXCam's own help articles state different free-plan retention figures in different places, so confirm the number in writing before you rely on it.

## Use cases

- **Two-person mobile startup with no analyst**: A fintech app is live on both stores, signups are steady, and nobody can explain why account verification completes for barely half of new users. There is no event instrumentation and no engineering time to add any. Outcome: The SDK goes in during one afternoon. Autocapture names the screens, the screen flow diagram shows a loop between the document upload screen and the camera permission prompt, and twenty replays make the cause obvious. The whole investigation fits inside the free plan's 3,000 sessions.
- **Product manager at a 40-person e-commerce app company**: Checkout conversion fell four points after a release and the analytics tool shows the drop but not the reason. Crash reporting is clean, so it is not an outright failure. Outcome: A funnel filtered to the new app version isolates the failing step, the touch heatmap on that screen shows repeated taps on a payment field that no longer responds, and the rage tap filter surfaces every affected session. The fix ships in the next release rather than the next quarter.
- **Support lead at a subscription app**: Tickets say the app froze or it did not work, with no reproduction steps, and engineering closes half of them as not reproducible. Outcome: The Intercom and Zendesk integrations attach the user's replay to the ticket, and the ANR and freeze detectors group the complaints into two device-specific issues. Support stops guessing and engineering gets a session to watch instead of a sentence to interpret.
- **Design team validating a redesign on Android and iOS**: A navigation redesign is being rolled out and the team wants evidence about behaviour rather than opinion, but has no budget for moderated research. Outcome: Screen flow analytics compares paths before and after, gesture heatmaps show which of the new tab targets are actually hit, and Tara AI's daily brief flags an unresponsive gesture pattern on smaller Android screens that nobody thought to look for.

## Pricing

Session-based metering. UXCam bills on the number of sessions captured per month rather than on seats, events, or monthly active users, and every paid tier is quoted rather than published. Four levels exist: a permanent free plan, then Starter, Growth, and Enterprise. Only the free plan's limits are documented publicly. Sessions reset on the subscription anniversary with no rollover, and usage beyond an allowance is billed in blocks of 1,000 sessions at a rate UXCam does not publish.

- **Free**: $0 per month, permanent. 3,000 sessions per month, reset monthly, no expiry and no card required; Two app keys, one dashboard with a maximum of six reports; Unlimited user licenses and chat support; Session replay, user analytics, event analytics, and basic crash, rage quit, and freeze filters. Genuinely usable for a pre-launch or early-stage app, but the exclusions (heatmaps, funnels, app flow, exports, integrations) remove most of what differentiates UXCam from a free web replay tool.
- **Starter**: Quote only no published price. Reported at up to 10,000 sessions per month, with overages billed per 1,000 sessions; Reported at 2 production apps and 5 user licenses; Session replay, heatmaps, frustration signals, and unresponsive gesture tracking; Reported at 1 dashboard, 3 funnels, and basic retention. UXCam publishes no dollar figure. The session, app, and seat limits here come from third-party readings of UXCam's plan comparison rather than from a vendor rate card, so treat them as directional and confirm in writing.
- **Growth**: Quote only no published price. Custom monthly session volume negotiated in the quote; Full analytics feature set including funnels, retention, app flow, and exports; Unlimited user licenses; 12 months session data retention, extendable. This is the tier most small and mid-sized app companies will actually be sold, and the point at which the absence of published pricing starts to matter.
- **Enterprise**: Quote only annual contract. Fully custom session volumes, seats, and retention up to 60 months; Per-app data residency selection across US, EU, and UAE regions; Advanced security and administration, SSO, and dedicated support; Everything in Growth.

Add-ons:

- Additional session volume (Billed in blocks of 1,000 sessions, rate not published): Overages appear on the invoice automatically once a plan allowance is exceeded; there is no rollover of unused sessions.
- Extended data and video retention (Negotiated within the quote): Session data retention is extendable above the Growth default, reaching 60 months on Enterprise. Video retention is always shorter than session data retention.
- Per-app data residency (Enterprise only): Non-enterprise accounts inherit the region of their first app for every subsequent app, and no app can be migrated between regions later.

Billing notes:

- All plans and services are billed in United States dollars regardless of where the customer is located. Credit cards are accepted; enterprise customers can pay by ACH or wire transfer.
- The meter is sessions captured, not users or events, so cost tracks engagement. A small audience that opens the app ten times a day can cost more than a larger audience that opens it weekly.
- Session allowances reset on the subscription anniversary and do not roll over. Verified reviewers report exhausting a quota mid-month and losing recording until the reset, and note that only the account owner can stop recording to head off an overage.
- Vendr's procurement data reports a median annual UXCam contract of $20,991, in a narrow observed range up to $21,949. That is directional buyer data from mid-market and enterprise deals, not a list price, and says nothing about what a ten thousand session account pays.
- Some third-party software directories list UXCam as starting at $199 per month. UXCam does not publish that figure anywhere on its own site, and it should be treated as an unverified legacy listing rather than a quote you can hold the vendor to.
- Retention figures are documented inconsistently in UXCam's own help centre: the pricing FAQ describes 12 months of session data with 3 month video retention on the free plan, while the data retention article states 6 months for both. Get the number that applies to your plan confirmed in writing.

Value assessment: UXCam's value is easiest to judge at the two ends and hardest in the middle. At the free end it is a strong offer for a small app team: 3,000 sessions a month, unlimited seats, no card, no expiry, and a 14-day full-feature trial with 100,000 sessions if you want to see what the paid product does before deciding. At the enterprise end, Vendr's reported median around $21,000 a year is broadly in line with Pendo, Heap, and FullStory contracts, and buyers at that level are used to a procurement cycle. The problem is the middle, which is where most small businesses live. A team that grows past 3,000 sessions cannot self-serve an upgrade, cannot model the cost, and cannot compare UXCam against Mixpanel's published per-event rate or LogRocket's published $176 a month without first booking a call. On raw capability for a native app the product earns its keep, particularly the combination of autocapture, gesture heatmaps, and issue detection that no web-first tool matches. On purchasability it is the weakest option in this comparison set, and that is a real cost to a small buyer even when the software is good.

## Strengths

- Genuinely mobile-first rather than mobile-ported: native Android and iOS SDKs with wrappers for React Native, Flutter, Cordova, Kotlin Multiplatform, Xamarin and MAUI, and NativeScript, and reports built around screens and gestures instead of pages and clicks.
- Autocapture removes the tagging plan. Screens, gestures, sessions, and device context are recorded without instrumentation, which is worth far more on mobile than on web because every instrumentation change otherwise waits on an app store release.
- Automatic UX issue detection is unusually good for the price band: rage taps, rage quits, unresponsive gestures, UI freezes, ANRs, and crashes are surfaced and linked to the exact replays, and even the free plan includes the basic filters.
- Small SDK footprint. UXCam publishes a figure under 300 KB with memory use under 1 MB and documented low CPU and bandwidth impact, which is the objection mobile engineers raise first about any recording SDK.
- A free plan that does not expire plus a 14-day trial with all features and 100,000 sessions, no card required, which is a fairer evaluation path than most quote-only vendors offer.
- Serious privacy tooling for a recording product: automatic text field occlusion, sensitive view marking on Jetpack Compose and SwiftUI, screen-level hide rules, per-screen blur, conditional recording, and data storage in the US, EU, or UAE.

## Limitations

- No published pricing for any paid tier. Starter, Growth, and Enterprise are all quoted, so a small business cannot budget, compare, or upgrade without a sales conversation, and the widely repeated $199 per month figure appears only in third-party directories.
- The free plan is deliberately thin. Excluding heatmaps, funnels, app flow analytics, advanced filters, exports, and integrations removes most of what makes UXCam distinctive, so the free tier is closer to a demonstration than to a working product.
- Session metering has hard edges. Quotas reset monthly with no rollover, overages are billed in undisclosed 1,000-session blocks, and reviewers report both losing recording mid-month and being unable to stop capture because only the account owner holds that control.
- A session ends when the app is backgrounded, which reviewers say fragments a single real user journey across several recorded sessions. That inflates the metered count and makes some journey analysis harder to reason about.
- The web product is the newer and weaker half. It launched in March 2025 with heatmaps following in July, so a web-first buyer is choosing an eighteen month old offering over Microsoft Clarity, Hotjar, FullStory, or LogRocket, all of which have far deeper web histories and, in Clarity's case, cost nothing.
- Diagnosis without remedy. There are no in-app guides, tooltips, checklists, surveys, feature flags, or experimentation tools, so acting on what UXCam finds requires a second vendor, and the quantitative analytics layer is noticeably less capable than Mixpanel or Amplitude.
- Recurring product complaints in verified G2 and Capterra reviews: a dashboard interface that several reviewers describe as slow and dated, sessions that occasionally fail to record or arrive delayed, and an integration that takes materially longer than the five minute claim. Data region is also locked at app creation, with no migration path.

## Comparisons

- **UXCam vs Smartlook**: The closest direct comparison, because Smartlook is the other behaviour analytics product that treated native mobile as a first-class recording surface rather than a port. The differences are commercial and organisational rather than functional. Smartlook publishes its pricing, starting free at roughly 3,000 monthly sessions and moving to paid plans from around $55 a month, and it is now part of Cisco, which means enterprise backing but also the roadmap uncertainty that follows any acquisition. UXCam is independent, quote-only above the free tier, and has pushed harder on mobile-specific diagnostics such as ANR detection, rage taps, and unresponsive gestures, plus the Tara AI analyst layer. A small team that wants to know its price before it commits should start with Smartlook; a team whose central problem is diagnosing friction inside a native app, and which is willing to take a quote, will usually find UXCam's mobile depth and issue detection better.
- **UXCam vs Mixpanel**: These two answer different questions and are commonly run together rather than against each other. Mixpanel is the quantitative tool: funnels, retention, cohorts, and breakdowns at population scale, driven by a deliberate event schema, metered on events with a free tier of 1 million events a month and a published per-event rate above it. UXCam is the qualitative tool: it shows you the screen, the gesture, the rage tap, and the replay. Mixpanel's mobile session replay exists but is a companion to its charts, and its analysis interface is considerably stronger than UXCam's dashboards and funnels. Choose Mixpanel if the questions are about conversion and retention across a large population and you want a price you can calculate; choose UXCam if the questions are about what specifically is broken on screen four of your Android onboarding. Teams with budget for both usually instrument Mixpanel for the numbers and install UXCam for the evidence.
- **UXCam vs Amplitude**: Amplitude is the platform play and UXCam is the specialist. Amplitude bundles product analytics, session replay, feature flags and experimentation, in-app guides and surveys, and a customer data platform under one event meter, with a permanent free tier of 2 million events a month and a self-serve Plus plan that scales a long way before anyone has to call sales. Its mobile SDK support is solid but its architecture and its centre of gravity are cross-platform and event-centric, not app-centric. UXCam has none of the flags, experiments, or guides, and its quantitative layer is thinner, but its gesture heatmaps, screen flow diagrams, and mobile issue detection have no equivalent in Amplitude. The practical rule: if you want one vendor and one invoice for the whole product stack, Amplitude wins on breadth and on published self-serve pricing; if your product is an app and your recurring question is why users are struggling on a specific screen, Amplitude will not answer it and UXCam will.
- **UXCam vs LogRocket**: This is the clearest mobile versus web split in the set. LogRocket is a web-first session replay and frontend debugging platform, and it is exceptional at the engineering job: console output, network waterfalls, JavaScript exceptions, performance timings, and Redux, NgRx, or Vuex state at every moment of the session. It also publishes its prices, free at 1,000 sessions a month and Core from around $176 a month at 25,000 sessions. UXCam offers nothing comparable in frontend forensics, but LogRocket's mobile story is far behind UXCam's on native app specifics such as ANR detection, gesture heatmaps, and screen flow. Buy LogRocket if a developer needs to reproduce a bug in a web application; buy UXCam if a product team needs to understand behaviour inside a native app. A company with a substantial product on both surfaces will plausibly end up with both, and should be honest with itself that neither covers the other well.
- **UXCam vs Microsoft Clarity**: The uncomfortable comparison, because Clarity is free forever with no traffic limits, no sampling, and no paid tier, and it now ships mobile SDKs for Android, iOS, Flutter, and React Native alongside its web recorder. For a small business that wants session recordings, click and scroll heatmaps, and automatic rage click and dead click detection at zero cost, Clarity is the honest first stop, and any UXCam evaluation should begin by asking what Clarity does not do for you. The answers are real: Clarity's mobile support is a comparatively recent addition to a web-first product, it has no funnels and retention depth to speak of relative to a product analytics tool, no screen flow analytics of UXCam's kind, no ANR or unresponsive gesture detection, no data residency choice, and no support commitment because there is no contract. If your app is small or your budget is zero, use Clarity. If mobile friction diagnosis is a core part of how your product team works, UXCam is meaningfully deeper and you are paying for that depth.
- **UXCam vs Countly**: Two answers to the same discomfort about sending mobile behaviour data to a third party. Countly's answer is architectural: an open source server you can install yourself for free, a managed private cloud from around $175 a month, or a fully self-hosted commercial edition where the vendor never sees your data, plus push notifications, surveys, and A/B testing that UXCam does not offer at all. UXCam's answer is configuration: occlusion rules, conditional recording, and a choice of US, EU, or UAE hosting, but always as a hosted service. On visual, qualitative analysis there is no contest, because Countly has no session replay comparable to UXCam's and no gesture heatmaps. Regulated buyers, EU public sector, and anyone with a hard no-third-party-data rule should look at Countly and accept the loss of replay; teams whose priority is seeing what users actually did on screen should choose UXCam and spend the setup time on masking rules.

## Implementation

- Setup time: UXCam documents a five minute SDK install per platform, and adding the dependency and initialising with an app key genuinely is that fast. A production-ready integration is a different number: screen tagging for anything the automatic detector names badly, occlusion rules for every screen touching personal or payment data, custom events for business facts, and a QA pass across OS versions. Budget half a day for a simple app and a few days for a large one, and note that several verified reviewers say the real integration took longer than they expected, particularly on React Native. The November 2025 MCP integration is aimed at shortening this, with UXCam citing a 30 to 60 minute setup.
- Learning curve: Low for anyone consuming replays, heatmaps, and screen flows, which is most of the value and needs no training. Moderate for the analytics side, where funnels, retention, and segments follow familiar conventions but the dashboard is less polished than Mixpanel or Amplitude, and where several reviewers describe the interface as slow and dated. The genuinely hard skill is deciding what to record: recording rules and sampling determine both your bill and whether your retention numbers are trustworthy, and getting that wrong is expensive in one direction or misleading in the other.
- Onboarding: Self-serve for the free plan and the 14-day trial, neither of which requires a card. Everything beyond that requires a sales conversation, since no paid tier is published or purchasable online; the plans page asks for team size and promises a response within 24 hours. Chat support is available on every plan including free, with dedicated support on Enterprise, and the developer documentation is thorough and platform-specific.
- Migration: There is no meaningful historical import: session replay data cannot be backfilled, so UXCam starts recording from the day the SDK ships and any comparison against a previous tool has to be forward-looking. Going the other way, the REST API and formatted export cover sessions, users, and events on paid plans, though replay video is not portable. The migration detail most likely to catch a team out is data residency: the storage region is fixed when an app is created, non-enterprise accounts inherit their first app's region for every later app, and moving requires deleting the app, creating a new one, and shipping a new app key. Decide the region before the first release, not after.

## Platform, API & security

- Platforms: Android (native SDK), iOS (native SDK), React Native, Flutter and Flutter Web, Cordova, Kotlin Multiplatform, Xamarin and .NET MAUI, NativeScript, Web via HTML snippet, Google Tag Manager, Shopify, or WordPress, Web dashboard for analysis
- API: REST API with documented sessions, users, and events endpoints supporting filtering, pagination, and aggregation query parameters, plus formatted export of sessions, screens, events, and users for BI tools. API access and export are excluded from the free plan. An MCP integration shipped in November 2025 to speed SDK setup.
- Compliance: SOC 2 Type 1 and Type 2, GDPR, with a published data processing agreement and consent management guidance, CCPA, PCI, HIPAA alignment stated by the vendor, Cloud Security Alliance STAR registry listing
- Data residency: Data can be stored in the United States or the European Union, selected when an app is created, with the United Arab Emirates added in November 2025. Enterprise customers choose the region per app; other plans inherit the region of their first app. Existing apps cannot be migrated between regions and historical data cannot be moved.
- SSO: Single sign-on has been available since April 2021; multi-factor authentication is offered from the entry paid tier.
- Security notes: Infrastructure runs on Amazon Web Services with AES-256 encryption at rest and TLS in transit. Recording privacy is controlled through automatic text field occlusion, sensitive view marking on Jetpack Compose and SwiftUI, screen-level inclusion and exclusion rules, per-screen blur, and the option to disable gesture recording on hidden screens. Configuring occlusion correctly is the customer's responsibility, and it is the step most worth reviewing before a recording SDK ships to production. Access control is a documented weakness: reviewers report that some account-level actions, including stopping recording to avoid an overage, are restricted to the account owner.

## Support

- Channels: Chat support on every plan including the free tier, Email support, Dedicated support and named contacts on Enterprise contracts, Solution engineering assistance during the trial and paid onboarding
- Documentation: Thorough, platform-specific developer documentation at developer.uxcam.com covering every SDK, screen tagging, custom events, occlusion, WebView handling, crash and ANR reporting, integration logging, and the REST API, published in an LLM-readable form as well. A separate help centre covers plan mechanics, data retention, recording settings, and privacy, and a UXCam Academy provides structured product education.
- Community: No large independent user community. UXCam runs an extensive mobile analytics blog and academy that functions as category education, and peer discussion happens mainly on review sites and general mobile development forums rather than in a vendor-run space.

## Company

- Founded: 2013
- Founders: Kishan Gupta, Richard Groves
- Headquarters: San Francisco, California, United States
- Ownership: Independent, privately held and lightly venture-backed
- Employees: Approximately 79 (Tracxn, July 2026)
- Funding: Approximately $5.1M raised across four early rounds from seven investors including 500 Global and Headline; the most recent round was a seed round in November 2021 and individual round amounts are not disclosed. No Series A has been announced and the company has not been acquired.

Funding history:

- Accelerator and early seed (2013 to 2014): Not disclosed. Participated in 500 Startups Batch 10 in San Francisco, followed by two seed rounds in 2014.
- Seed (2021): Not disclosed. November 2021 round with four investors participating; the most recent funding event on record.

Timeline:

- 2013: Founded by Kishan Gupta and Richard Groves to record and analyse what happens inside native mobile apps, at a point when behaviour analytics was almost entirely a web category.
- 2014: Joins 500 Startups Batch 10 in San Francisco and raises two seed rounds, establishing a US headquarters alongside engineering presence in Germany and Nepal.
- 2020: The analytics half of the product arrives in earnest: event analytics in October, screen flow visualisation in December, and issue analytics for crashes and UI freezes the same month.
- 2021: Single sign-on ships, Slack crash notifications launch, user analytics gets a dedicated page, and the company raises its most recent seed round in November.
- 2023: A heavy year of qualitative product work: heatmap area selection and gesture filtering, redesigned session replay with rage quit filters and timeline markers, ordered and unordered funnels with custom conversion windows, screen blur rules and text field occlusion, and Microsoft Teams issue alerts.
- 2025: Web product analytics launches in March, heatmaps come to web in July, and multi-region data storage arrives in July with the EU and US followed by the United Arab Emirates in November; an MCP integration lands in November to shorten SDK setup.
- 2026: Tara AI, an AI product analyst that watches sessions, flags friction, and issues daily briefs, launches in January, with prompt suggestions following in February. UXCam reports more than 37,000 products using the platform and over 100 billion data points processed monthly.

## Integrations

Segment, Mixpanel, Amplitude, Firebase Analytics, Firebase Crashlytics, Google Analytics 360, Adobe Analytics, Intercom, Zendesk, Salesforce, Slack, Microsoft Teams, REST API and formatted data export for BI tools

## FAQ

### What is UXCam used for?

UXCam is used to understand how people actually behave inside a mobile app. Teams install its SDK to get session replays of real user visits, touch and gesture heatmaps for each screen, a screen flow diagram of the paths users take, funnels and retention reports, and automatic detection of friction such as rage taps, unresponsive gestures, UI freezes, application-not-responding events, and crashes. The most common jobs are diagnosing a drop in onboarding or checkout completion, reproducing a bug that support cannot describe, and validating a design change with evidence rather than opinion. A web version of the same feature set launched in March 2025.

### How much does UXCam cost?

UXCam does not publish a price for any paid plan. The free plan is $0 for 3,000 sessions a month, and the Starter, Growth, and Enterprise tiers are all quoted after a sales conversation. Billing is metered on sessions captured rather than seats or events, all invoices are in United States dollars, and usage above an allowance is charged in blocks of 1,000 sessions at a rate that is not published. The only public price anchor is Vendr's procurement data, which reports a median annual UXCam contract of $20,991 in a narrow observed range up to $21,949; that reflects larger buyers and should not be read as what a small team would pay. Some software directories list a starting price of $199 a month, but UXCam does not state that figure anywhere on its own site.

### Does UXCam have a free plan?

Yes, and it does not expire. The free plan covers 3,000 sessions a month that reset monthly, two app keys, one dashboard with a maximum of six reports, unlimited user licenses, chat support, and session replay, user analytics, and event analytics with basic filters for crashes, rage quits, and freezes. No credit card is required. The exclusions matter: heatmaps, funnels, app flow analytics, advanced filters, data export, rule-based recording, and third-party integrations are all paid features. Separately, there is a 14-day free trial that unlocks the full platform with 100,000 sessions and 100,000 videos, which is the better way to evaluate what you would actually be buying.

### What are UXCam's main weaknesses?

Three stand out. First, pricing opacity: no paid tier is published, so a small business cannot budget or self-serve an upgrade past 3,000 sessions. Second, the session meter has hard edges, with quotas that reset monthly without rollover, undisclosed overage rates, and reviewers reporting that only the account owner can stop recording to prevent a charge. Third, the product diagnoses but does not fix, with no in-app guides, surveys, feature flags, or experimentation, and a quantitative analytics layer noticeably thinner than Mixpanel or Amplitude. Verified G2 and Capterra reviewers also commonly cite a slow and dated dashboard interface, sessions that occasionally fail to record or arrive delayed, and integration taking longer than the advertised five minutes.

### Is UXCam only for mobile apps?

No, but mobile is what it is built around and what it does best. Native Android and iOS are the primary SDKs, with wrappers for React Native, Flutter, Cordova, Kotlin Multiplatform, Xamarin and MAUI, and NativeScript. A web product analytics offering launched in March 2025 with web heatmaps following in July 2025, installable through an HTML snippet, Google Tag Manager, Shopify, or WordPress. If your product is a website rather than an app, the web offering is comparatively new and you are usually better served by a tool with a longer web history.

### UXCam vs Smartlook: which should a small app team choose?

Both are unusual in this category for treating native mobile as a first-class recording surface rather than a port of a web tool, so the decision usually turns on how you want to buy. Smartlook publishes its pricing, starting free at roughly 3,000 monthly sessions and moving to paid plans from around $55 a month, which makes it easy to budget; it is also part of Cisco now, which brings backing and roadmap uncertainty in equal measure. UXCam is independent and quote-only above its free tier, and goes deeper on mobile-specific diagnostics such as ANR detection, unresponsive gestures, and screen flow analytics, plus the Tara AI analyst. Pick Smartlook for price transparency, pick UXCam for mobile depth.

### UXCam vs Mixpanel: do I need both?

They answer different questions and a lot of teams do run both. Mixpanel is the quantitative layer: funnels, retention, cohorts, and breakdowns across a whole population, built on a deliberate event schema, with a free tier of 1 million events a month and a published per-event rate above it. UXCam is the qualitative layer: replays, gesture heatmaps, screen flows, and automatic friction detection that show you the specific screen where things break. Mixpanel's mobile session replay exists but is a companion to its charts, and UXCam's dashboards and funnels are thinner than Mixpanel's. If you can only pick one and your questions are about conversion and retention at scale, choose Mixpanel; if they are about what is broken on a particular screen of your app, choose UXCam.

### How does UXCam count a session, and why does that matter?

A session covers the metadata collected during a user visit: device data, user data, screens visited, events triggered, and gestures made. It matters because sessions are the billing unit. Reviewers note that a session ends when the app is backgrounded, so one real user journey interrupted by a phone call or a switch to another app can be recorded as several sessions, which both inflates the metered count and fragments journey analysis. The practical response is to use recording rules and sampling deliberately, while remembering that UXCam's own documentation warns retention analytics becomes unreliable under sampling.

### Does the UXCam SDK slow down or bloat my app?

UXCam publishes an SDK size under 300 KB with memory use under 1 MB, main thread usage averaging around 19 milliseconds per frame drawn to bitmap, CPU bursts of roughly 3 to 6 percent on mid-range Samsung devices, and network calls limited to session start and app backgrounding. Video is encoded on device so uploaded files stay small. Those figures are the vendor's own, so treat them as a starting point and measure on your lowest-end target device during the trial. A minority of Capterra reviewers report performance strain when recording high-resolution screens, which is the case worth testing yourself.

### How does UXCam handle privacy and sensitive data in recordings?

Text fields are occluded automatically, individual views can be marked sensitive including in Jetpack Compose and SwiftUI, whole screens can be hidden by inclusion or exclusion rule, per-screen blur rules can be applied, and gesture recording can be disabled on hidden screens. UXCam states SOC 2 Type 1 and Type 2 certification, publishes a data processing agreement, provides GDPR and CCPA consent and deletion guidance, and describes PCI and HIPAA alignment; infrastructure runs on AWS with AES-256 encryption at rest and TLS in transit. Configuring the masking correctly is your responsibility, and it should be reviewed screen by screen before a recording SDK reaches production.

### Can UXCam store my data in the EU?

Yes. Multi-region data storage launched in July 2025 with a choice of United States or European Union hosting, and the United Arab Emirates was added in November 2025. The region is chosen when you create an app. The important caveat is that it cannot be changed afterwards: existing apps cannot be migrated and historical data cannot be moved between regions, so switching means deleting the app, creating a new one, and shipping a new app key. Enterprise customers can set the region per app, while other plans inherit the region of their first app for everything created later.

### How long does UXCam keep my data?

Session data and video are retained on separate clocks, with video always the shorter of the two, and both are counted from when a session uploads rather than when it happened. Growth is documented at 12 months of session data with the option to extend, and Enterprise reaches 60 months for both session data and video. Free plan retention is stated inconsistently across UXCam's own help articles, with the pricing FAQ describing 12 months of session data and 3 month video retention while the data retention article states 6 months for both, so get the figure that applies to your account confirmed in writing before relying on it.

### Is UXCam a stable vendor to build on?

It is small but long-running and independent. Founded in 2013 by Kishan Gupta and Richard Groves, headquartered in San Francisco with additional presence in Germany and Nepal, it has raised roughly $5.1M across four early rounds from seven investors including 500 Global and Headline, with the most recent round in November 2021. There has been no Series A and no acquisition, and third-party trackers put headcount around 79 in mid-2026. That profile cuts both ways: it has survived thirteen years and consolidation that absorbed Heap, Hotjar, and Smartlook into larger companies, but it is a fraction of the size of Amplitude or Contentsquare and its roadmap depends on a much smaller team.

## Editorial verdict

UXCam is the strongest answer in this category to a narrow but common question: what is actually going wrong inside my mobile app. Autocapture means you get screens, gestures, and sessions without a tagging plan, gesture heatmaps and screen flows are built for touch rather than adapted to it, and the automatic detection of rage taps, unresponsive gestures, freezes, and ANRs finds problems no funnel would have told you to look for. The free plan is real and permanent, the 14-day trial with 100,000 sessions is a fair way to evaluate the paid product, and the SDK is small enough to survive an engineer's objection. The reasons to hesitate are commercial and structural rather than technical. Nothing above the free tier has a published price, so an owner cannot budget or upgrade without a call; session metering has hard monthly edges and an undisclosed overage rate; the web product is young; and UXCam diagnoses problems without giving you any way to fix them in-app, so most teams will also pay for an analytics tool, an onboarding tool, or both. Install it if your product is an app and friction diagnosis is a regular part of your week. Start with Microsoft Clarity if your budget is zero, with Smartlook if you need to know the price before you commit, and with Mixpanel or Amplitude if the questions you actually have are about numbers rather than screens.

---

Source: SaaSTracker (https://saastracker.org), an independent editorial project. This profile is compiled from public information, carries no peer reviews or paid placement, and was last reviewed 2026-08-30. Awards are judged on published criteria: https://saastracker.org/methodology