Pulse Analytics

[burt]

I have created a self contained Analytics system so that you can view your Phoenix's health. It's called Pulse (ie like a heartbeat monitoring of your shop). Pulse tracks "events", such as ;

product_viewed
add_to_cart
cart_viewed
specials_viewed
checkout_start
checkout_end

and any number of other things only limited by your imagination and the ability of you (or a coder) to write a few lines of code to integrate a new tracked event.

There is NOTHING to see on the Shop Side.

But on the Admin Side, you have this;

Main Admin Page showing quick cards and main events table.

pulse_1.png

And a Products page where you can select a Product (or ALL) and a Date Range to show the Pulse of Views vs Sales.

pulse_2.png

[burt]

NO core code changes, that's my style Sir.
NO ongoing subscription fees, nickel & diming you.
NO 3rd party involvement.
NO data loss to any other companies.
YOU own YOUR data.

--

You want to add a new Pulse, easy as 123..no core code change.
You want to add a new Admin View (like the Product Views/Sales), easy as 123, no core code change.
You want to add a new Card at the Top (like the 3 cards that are in the image), easy as 123, no core code change.

Just to show an extra Days Views/Sales of Oranges;

[burt]

We now have a Login Pulse;

login.png

My next mini-project is to introduce a filterable report, so that shopowner can see all events of (eg);

event_type; ALL, login, product_view, etc
customer_id; of this particular customer only
product_id; of this particular product only

[burt]

A create_account Pulse might be interesting. Then shopowner could exactly know `new` customers vs `returning` customers.

[burt]

Now we can Filter Customer Pulse, per customer.

cust.png

And similar filtering for Product Pulse, per Product.
Or even per Customer, per Product.

[Omar_one]

will be an new database table for product_viewed including date ?
as I think we have it now as count of views and there is not data of when the products viewed.

[burt]

will be an new database table for product_viewed including date ?
as I think we have it now as count of views and there is not data of when the products viewed

Exactly so. Some of Phoenix is still using stuff from osc of 20 yrs ago, I'm trying to move it forward
All data is stored in new table.

[burt]

This is the next in the August Code Drops.

Note that the Drop will be in TWO parts;

1. The base system including the product_view Pulse Event.
- simply to ensure a really easy install, and to easily see the system in action.
and then
2. The rest of the Pulse Events
add_to_cart, checkout_started, checkout_end and more.

Sign up for August Code Drops here:
To get this, the previous August Drops, the future August Drops
and the knowledge your Beer is helping me work on Phoenix Core Code.
I'm doing Core Code alone at the moment, so any help is extra valuable.

viewtopic.php?f=28&t=2924

[burt]

If any of the August Code Drop members have feedback on the first part (which is the foundation + the product_view Pulse), I'd appreciate knowing of any problems or suggestions.

I can get the second part (which adds in *loads* more Pulse Events) updated to fix any problems or update with suggestions etc, and then distribute to you guys.

Thanks in Advance.

[burt]

No extra feedback so can only assume all is OK - get next lot of Pulse Events out to all.

Surprised at lack of interest in this overall, as Pulse really uprates some of Phoenix's historical code, and provides actionable insights in not only how your shop is doing, but what your customers are doing.