A lot of page calls

[ianstormtaylor]

From one of the beta testers:

Regarding "Viewed", I think by far the biggest thing that makes this discussion tricky is the exact implementation in the current Magento Segment beta library, which is to essentially call analytics.page(CURRENT_PAGE_TITLE). This results in a bunch of events like "Viewed Eye Cream" and "Viewed Lip Balm", with nothing unifying the two events as product pages. Most event analytics suites I've used (in particular Mixpanel, KISSMetrics, and GA) put the event name at some a pivotal high level with no option to consolidate events into classes.

As a result, this fine-grainedness of the beta library's implementation would leave us unable to answer a question "What percentage of homepage visitors see a product page" without a bunch of manual work to aggregate events. If this changed in the library to do something like analytics.page(CURRENT_PAGE_TYPE), it would help somewhat.

@astorm he didn't install, he was looking at the code. But can you give me a sense for which pages in Magento will generate the page(name) calls versus the page(category, name) calls?

Does every product result in:

analytics.page('Name of Product');

On those specific pages? Curious.

I think I probably recommended that if so, but if so I'll do a bit of thinking about how to solve his problem here.

[astorm]

Take a look at the top navigation on this demo store site

http://commercebugdemo.pulsestorm.net/

We're using the category form of .page on the category landing pages. Furniture, Electronics, and Apparel are all links to category landing pages. Their sublinks are also links to category landing pages.

Also, re: the user's comment above, we were (until yesterday) missing a "View Product" event. We now have this.

[astorm]

Take a look at the top level navigation on this demo page

http://commercebugdemo.pulsestorm.net/

We're using the category form on category landing pages. Furniture, Electronics, and Apparel are all category landing pages. So are their sub-links.

Also, Re: the specific comment above, up until yesterday we were missing a specific Viewed Product event.

[astorm]

Read reading this, realized my explanation may not have been clear.

Every page generates a .page call.

The category pages mentioned above generate a .page call in the category form.

Product pages generate a .page call with the product's name, as well as a Viewed Product .track event.

Let me know if the .page call is redundant on the product pages or if this behavior needs to change.

[ianstormtaylor]

Ah gotcha! Let's change the product page call to be .page('Product') instead of .page('PRODUCTNAMEHERE'), that way we don't end up with an unbounded number of page names.

[astorm]

Done.