A privacy-first alternative to the analytics you use today
Respectlytics shows where users convert and where they give up, with no user IDs, no device IDs and nothing stored on the phone. Here is how it compares with the tools most apps use today, fact by fact.
Free for one app and 20,000 events a month, no card needed. The demo runs on sample data, no signup.
The comparisons
Each page shows what the other tool stores about your users, what Respectlytics stores instead, and how to switch.
Why teams switch to Respectlytics
What they get from the first day, whichever tool they come from.
The analysis runs by itself. Name your conversion events, and Respectlytics works out the paths that lead there, the steps where sessions end and the events that go with converting.
You hear about changes the same day. Alerts by email, Slack or webhook when an app goes quiet, an event stops arriving, the day's events jump or drop, or conversion falls. On paid plans.
What changed, every Monday. A short email with what moved in each of your apps last week, and a link to the view that shows it. On every plan.
A/B tests without profiles. Declare a property such as a paywall version, and see how the sessions with each variant convert. On paid plans.
Every feature on every paid plan. Unlimited apps, team members and two years of history on all of them. You choose only how many events a month.
Free to start, with no card. One app and 20,000 events a month on the free plan, with no time limit, and an upgrade whenever you need more.
Carrying an attribution SDK just to count?
Respectlytics can take over what happens inside the app, with no IDs.
Attribution tools such as AppsFlyer, Adjust, Branch, Kochava and Singular say which campaign brought an install, and data platforms such as Segment and mParticle route events to other tools. Both are built on identifying users or devices.
Many apps carry one of them only to count what happens after the install. Respectlytics counts that, finds the paths that lead to a purchase, and leaves you free to decide whether you need attribution at all.
Coming from another analytics SDK
Flurry, Countly, Matomo, GameAnalytics or one of your own: the switch looks the same.
Install the SDK, configure it at launch, replace your tracking calls with one line each, and run both side by side until you trust the numbers.
If you self-host Countly or Matomo to keep data on your own servers, the Respectlytics Community Edition does that too. It needs Docker and PostgreSQL. See the open source edition.
Questions buyers ask
Straight answers to what teams ask before they choose.
Can I run Respectlytics next to my current analytics?
Yes. The SDKs do not depend on any other analytics library, so you can ship both, compare the numbers for a few weeks and then remove the old one.
Can I import my history from another tool?
No. Respectlytics starts counting the day you install it, which is why most teams run both side by side for a few weeks. History exported from other tools carries user and device identifiers, which the API is built to refuse.
How much work is a switch?
Small. The install is a few lines per platform and each tracking call becomes one line. Most of the work is choosing the 10 to 20 events that answer your questions, and the event plans and the SDK page's AI prompt help with that.
Keep exploring
Comparisons, design choices, event plans and industries.
Try it on your own app
Free for one app and 20,000 events a month, no card needed. Unlimited apps on every paid plan.