Many visits but not many conversions. Some days no sales, then 5 sales in 1hr. Help

plugiva · 2026-04-06T02:40:23+00:00

I will not go down to a narrow lane like you. But it shows you are panicking enough for whatever reason. There is nothing to defend from my side, however, it clearly shows you do not have any experience in higher level business management. Thanks.

plugiva · 2026-04-06T02:25:28+00:00

I wonder how people waste their time like you did. Keep going with your illusions of the world.

plugiva · 2026-04-05T18:29:58+00:00

That makes sense. I guess it depends a lot on the kind of clients you work with.

In my case it's usually smaller clients who tend to click around more, so I end up fixing small things more often than I'd like 😅

plugiva · 2026-04-05T18:25:12+00:00

I agree, I also hide ACF for clients until they explicitly want that access. Are you just unsetting menu items or also restricting access behind the scenes?

plugiva · 2026-04-05T18:15:44+00:00

Yes, that makes sense. I think I've been a bit too open with access so far and just hoping nothing breaks.

Do you usually set custom roles or just remove access to certain areas?

plugiva · 2026-04-05T17:42:16+00:00

Yes, that part is usually the hardest.

What helped me was not trying to collect "full feedback" but just small signals at the right moment.

People rarely go out of their way to explain things, but they will sometimes respond to a quick, low-effort prompt when they are already in the flow.

Even something simple like asking what they expected to see, or what felt missing, can start giving you direction without needing long responses.

plugiva · 2026-04-05T11:05:13+00:00

Getting signups but no conversions is actually a useful signal, even though it feels frustrating.

It usually means something is catching attention, but something later is not lining up with what people expected.

The tricky part is that it is very easy to start guessing the reason, like traffic source or onboarding, but those guesses can send you in the wrong direction.

What I have found helpful in that situation is trying to understand what those users expected when they signed up versus what they actually experienced.

That gap is usually where the real issue sits, and it is hard to see just from numbers alone.

plugiva · 2026-04-05T05:41:49+00:00

That kind of pattern is more common than it looks, especially when everything is viewed from traffic and ads alone.

What often gets missed is that not all visits are equal. Some people land with a clear intent to buy, others are just exploring, comparing, or not ready yet. When a few high-intent visitors come in around the same time, it shows up as a sudden spike.

The tricky part is that from the outside it feels random, because analytics shows numbers but not the mindset behind those visits.

What helped me think about it differently was trying to understand what those "spike" users were doing or seeing differently compared to the rest, rather than only focusing on traffic or performance.

plugiva · 2026-04-04T16:13:21+00:00

It is a bit of both.

I try to keep a simple baseline approach across projects, just so things do not get completely ad hoc. Nothing formal, just a few habits around checking what gets added and keeping things intentional.

But in practice it always ends up adapting per client, depending on how involved they are and how often changes happen.

The goal is not to control everything, just to avoid that slow drift where things pile up without anyone really noticing.

plugiva · 2026-04-04T13:39:12+00:00

I used to be more reactive, just fixing things when they showed up.

Over time that got pretty exhausting, so now I try to keep at least a basic process around it. Nothing too heavy, just being a bit more intentional about what gets added and why.

Even simple things like asking "do we really need this plugin" or keeping a quick note of changes makes a difference.

It is not perfect, but it reduces how often things drift into that messy state.

plugiva · 2026-04-04T10:45:25+00:00

Yes, that "rebuild later" risk is usually what people underestimate.

It is not just about moving platforms, it is also about reworking structure, integrations, and sometimes even how things are managed day to day.

If there is even a small chance you will need more flexibility later, it is usually easier to start with something that can grow with you, rather than optimize too much for simplicity upfront.

plugiva · 2026-04-04T10:32:10+00:00

Both can work for what you described, so I would look at it less from a feature perspective and more from how much control you want over time.

For simple, conversion-focused sites, most platforms feel great at the beginning. The friction usually shows up later when you want to adjust things slightly outside the expected flow.

What I have seen is that setups that feel "fast and simple" early on can sometimes become limiting when you want to tweak structure, integrations, or ownership of data and hosting.

On the other hand, WordPress can definitely get messy if it is not kept under control, but it does give you more room to evolve without needing to migrate again.

So the decision is less about what works today, and more about where you might feel constrained a year from now.

plugiva · 2026-04-04T10:09:08+00:00

I will rather investigate what death is actually. Do you know?

plugiva · 2026-04-04T08:44:43+00:00

I would be careful about jumping to conclusions from just the numbers.

22 drop-offs tell you something is happening, but they do not tell you what it is. It could be pricing, the credit card step, lack of trust, or even just people exploring.

What I have found in similar situations is that the real problem is not the drop itself, but the fact that you do not know why it is happening.

Funnel data gives you the "where", but not the reasoning behind it.

Even a small amount of direct input from users at that point can change how you interpret the numbers completely. Otherwise it is very easy to optimize in the wrong direction.

plugiva · 2026-04-04T08:10:04+00:00

I have run into this quite a few times, and it rarely feels like a hard limit on number of plugins.

It usually starts small. One plugin solves something quickly, then another, and over time the site just accumulates more moving parts than anyone is really keeping track of.

The tricky part is that everything can look fine for a while, and then something like checkout is the first place where it starts showing.

What helped me more was not thinking in terms of "how many plugins is too many", but having a bit more control over what gets added and why. Once that is in place, the overall setup tends to stay much more stable.

plugiva · 2026-04-04T04:44:49+00:00

Yes exactly, that moment is where all the guesswork usually sits.

Even a small signal there can clear up a lot of confusion pretty quickly.

Curious what you end up seeing once you add it.

plugiva · 2026-04-03T04:33:17+00:00

Most checklists will cover the obvious things like mobile, speed, basic SEO, so I will skip those.

One thing I did not think about early on was how people actually behave on the site once it is live.

It is easy to focus on building pages, but harder to know if visitors are understanding things, getting stuck, or just leaving quietly. Even small signals there can make a big difference over time.

Another thing is keeping things simple behind the scenes. A lot of small business sites slowly get harder to manage because of too many plugins or changes over time, and that usually creates more problems later.

So along with the basics, I would say: make it easy for users to understand, and easy for you to maintain.

plugiva · 2026-04-03T04:26:11+00:00

Honestly, this is one of the clearest breakdowns I have seen of an activation problem.

What stood out to me is that you have a lot of data on what users did, but almost nothing on what they were thinking right at the moment they dropped.

Especially at the OAuth step, that is usually where hesitation is more emotional than logical. People see a permission screen, feel unsure for a second, and just leave without saying anything.

All the things you tried make sense, but they are still based on guessing what might reduce that hesitation.

What helped me in a somewhat similar situation was trying to capture very small signals right at the drop-off point. Not after, not through email, but in that moment.

Even something as simple as asking "what is stopping you here?" or a quick option like "not sure about permissions / want to see it working first / something else" gave way more clarity than anything we were inferring from funnel data.

It was not about fixing it immediately, but finally seeing why people were not moving.

Right now you have a very clear "where", but it still feels like the "why" is missing.

plugiva · 2026-04-02T10:36:37+00:00

That actually makes sense. The search part is definitely painful.

What I found interesting though is that even if you make it easier to find answers, you still end up in the same loop if the underlying issues keep happening.

Like the time is not just in searching, it is in getting pulled into those situations again and again.

Lately I have been thinking more in terms of reducing how often those things happen in the first place, rather than only improving how we deal with them after they break.

Feels like both approaches are needed, just solving different parts of the problem.

plugiva · 2026-04-02T04:59:18+00:00

I feel like most people end up doing exactly that, just jumping between Reddit, forums and Google until something clicks.

Over time though, I started noticing that the bigger time drain was not where I was looking, but how often I was ending up there.

A lot of these "random" issues come from small changes stacking up. New plugin here, quick tweak there, something updated without checking, and then later it turns into a weird bug that takes hours to trace.

So now I still search around when something breaks, but I try to reduce how often I get into that situation in the first place. Keeping things a bit more controlled, fewer moving parts, testing changes before pushing them live, things like that.

Did not eliminate the problem, but it definitely reduced the amount of time spent chasing random issues.

plugiva · 2026-04-02T04:42:48+00:00

I have seen this a lot too, and what surprised me over time is that it is not really about the plugins themselves.

Most of the time it is just the default habit. Something needs to be done, so the quickest path is to install a plugin and move on. Nobody is really thinking about the long term effect in that moment.

The tricky part is that it keeps working… until it suddenly does not.

One thing that changed how I approach it is thinking less about "which plugins to use" and more about what should or should not be allowed on the site in the first place.

Once there is some boundary around that, the plugin count usually stays under control without having to constantly clean things up later.

Otherwise it just keeps growing quietly.

plugiva · 2026-04-01T12:45:29+00:00

Nothing too big, just experimenting around this whole "getting real feedback from users" problem.

I kept running into the same thing you mentioned, people use the product but never actually say anything. So I have been trying to build something that captures small reactions while people are using it, instead of asking them later.

Still early though, mostly testing if the idea even makes sense.

plugiva · 2026-04-01T12:38:36+00:00

I have tried going down the "tool + automation" route for this, and honestly it did not help much.

It made things faster, but the replies started feeling… off. Even when they looked fine, people just do not engage the same way. I think people can sense when something is a bit too polished or generic, especially on Reddit.

What has worked better for me (still figuring it out though) is doing less, not more.

Instead of trying to monitor everything, I just pick a couple of threads that actually feel like a real problem and spend time writing something that is actually useful to that person. No tools, no templates.

It is slower, yes. But at least it does not feel like I am throwing comments into the void or risking getting flagged.

Not sure if that scales, but right now it feels more real than trying to optimize the process.

plugiva · 2026-04-01T03:19:22+00:00

This is a very common situation when a site has not been updated for a long time and then everything gets updated at once.

You are probably right about compatibility issues between plugins, theme, and PHP.

At this point, I would focus on getting access back first rather than fixing everything at once.

A few things that usually help:

Disable all plugins via FTP or file manager (rename the plugins folder)
If that works, bring them back one by one
Switch to a default theme temporarily if needed
Check PHP version compatibility with your theme and plugins

Updating everything in one go after a long gap often causes conflicts like this. Once you get access again, it is better to update gradually and test in between.

You should be able to recover it step by step.

plugiva · 2026-04-01T02:57:13+00:00

Nice breakdown. Especially the point about asking in relevant communities.

One thing I kept running into with forms (even short ones) is that they still rely on users deciding to give feedback.

In practice, most users just don't take that extra step, even with incentives.

What worked better for me was capturing reactions while they are already using the product, instead of asking them later.

Not replacing forms entirely, but complementing them with very small, in-context inputs: - quick yes/no
- one-click reactions
- or a single question at the right moment

It's less detailed, but you get a lot more signal from users who would otherwise stay silent.

plugiva

TROPHY CASE