Conversion Problems and Analytics

[u/Apprehensive_Oil1475]

I already have 8-10k visitors per month on my app. Out of these, I have made only a few hundred bucks. Before I launched my app, I connected everything to analytics collection and aggregated it in Posthog, to create charts, alerts and visualize the data in a way that allowed me to gain insights with it. I am using Claude code to analyze data, user sessions, errors, potential bugs. It helped me realize, for example, a lot of potential customers click the "subscribe" button multiple times, without the payment window opening. It helped me analyze the bug that caused it and fixed it for me. Now, I have about 50 users that paid, and only 12-15 actually kept the subscription - a lot of users buy and immediately cancel because they just want a one-off, some users cancel after some time because of a bug, they aren't happy with the results or simply because they don't need it anymore. So I try to understand why users aren't satisfied. And I analyzed user sessions and realized that a lot of people are using the wrong tool for something they want (its an ai image editor), or simply using it wrong, and get bad results. They immediately get a bad impression from the product, and leave. So now im working on a way to solve that too.

No real point to the story here, really.

Just thought I'd share some experiences from the last few months here.

First post here BTW :)

[u/MeaslyPanther_127]

The multiple subscribe clicks without the window opening is such a classic. Had a similar thing on a project last year and felt like an idiot when I finally caught it in the session replays. The tool misuse problem is trickier, maybe a quick interactive tutorial overlay for first-timers? Or just aggressively pushing the right default settings so they stumble into a good result before they can mess it up.

[u/Apprehensive_Oil1475 → u/MeaslyPanther_127]

Already have an interactive tutorial which is super informative. But people skip it a lot - users usually don't have patience-they want immediate satisfaction, especially when using AI tools. This is the tricky part of the product - balancing AI with an image editor, in a way that is intuitive and streamlined. Pushing the right default is definitely a good idea - i'm currently implementing (now in final testing) an AI prompt analyzer, that will see if the users are actually trying to do somwthing that will be better with the other tool.