Phoca Forum

I agree, but it's not the only way. Maybe he should be making much more from it?

Here the problem is somewhere else. Even if I had the time or even if it was paid for, GA is not something I work on regularly. That's why there are events and plugins in Phoca Cart to extend this. Moreover, such a plugin simply already exists and there is no point in writing something new. Besides, this is an area where things change often. On the one hand, on the part of the provider (Google), but mainly on the part of marketers, who change their requirements from day to day.

I focus on the core and try to make the system extensible. And at this point (GA) I am ready to extend the core system according to any needs. The problem is that the people working with GA never deliver the right requirements, they keep changing everything and they don't know how websites work at all.

Trust me, if you get the right requirements and clear instructions, then programming the plugin is a simple matter, but in this regard (GA) I get only confusion and information that changes even in a few hours.

I hear you great points well made. I am sorry. GA is a mess for everyone.

As I understand it to track a button press requires js to be fired. So if a button can get a custom ID then you can add custom js to target this. But buttons don't tend to have this feature.

If you want to capture the event of pressing button, the this cannot be done per events on the server, this needs to be done in Javascript directly (despite the fact that tracking this event does not make sense, because just pressing a button does not say anything, moreover, such statistics are strongly influenced by bots, and in addition, I would personally be interested in what important output is for the customer from marketers in the sense that someone pressed the button). Instead of pressing button, you can e.g. per backend methods get information about which products e.g. were added to cart and which products in cart were not "transformed" to successfull order, etc. etc. Lets say you have GA, which completely slow down the website, you track nonsense events but instead you can get great data from backend (without slowing down the site) whcih nobody uses.

But this is not our goal. My goal has always been to give users what they need. So we have to look at it objectively. Catching the button press event should be completely up to GA, and now the question is what exactly is the identifier for the button GA needs. As I wrote, if I get clear and specific data, what and where should be added so that GA can create its activity, there is no problem to put this in one of the following Beta versions.

Mostly there is following scenario:

- the core gets event on some place where specific GA pugin can be run
- then the plugin can be extended through this event (mostly some javascript call or some ID for the javascript)
- the the GA javascritpt should care about the statistics.

Jan