search

MinnPost / minnpost-membership

WordPress plugin for membership stuff
GNU General Public License v2.0
1 stars 1 forks source link

Address the current requirements for Ecommerce tracking for #38 #39

Closed jonathanstegall closed 5 years ago

jonathanstegall commented 5 years ago

I'd like us to review this one carefully, but I think it does at least meet the criteria of tracking what we currently track in the Ecommerce section of Analytics for #38.

I think it might also make it easier to track some of the other things Analytics has built into it, like product details (maybe we could add that as another event that happens when a user switches levels?) and product list (maybe that is the event for when users go to the levels page?)

jonathanstegall commented 5 years ago

@krbullock we're still discussing that part about the benefits description page. Here's where my thought process was (and I'll go ahead and merge this part so we could discuss in Asana if that works better for you):

I was looking through the Analytics documentation for the Ecommerce tracking features. There are two features (at least) that we don’t use because they’re built for shopping carts:

  1. The product detail view
  2. The product list view

I was wondering if we could use those features like this:

  1. Product detail could be something we do when users switch the level, if they are looking at the thank you gifts. So whenever their amount or frequency or whatever they click has changed the level they'd be getting, it would trigger a product detail view.
  2. Product list could be if users go to the benefit list page.

Again, neither of those things have to happen for us to launch. But I thought if people understand this data model, using the built in features might be helpful?

krbullock commented 5 years ago

@jonathanstegall Thanks for the explanation! I think that approach makes sense, let's continue talking about it w/the rest of the team.