@JMinor this is tagged for beta, but is already in ready for dev, ahead of other alpha tasks. Is that intentional?

@JMinor to be clear, do you intend for us to use Piwik for this initially, or go straight to Event Logging?

@JMinor got a few more questions.

1. For "impressions" - do you want to log an impression for each section or for each item in each section?
2. Piwik has "impression/conversion" tracking which can used instead of just a plain "event" do you want me to use that for tracking the impressions and taps on the home view?

1. Lets track each individual item
2. No lets use the event system for tracking user events in general. Its not too hard to calculate conversion rate and it just keeps user interactions all in the same reports.

@JMinor also - I didn't add "load section" tracking as that seemed to not be necessary (especially since we are going to lazy loading anyways) - impressions / taps for each appear to be enough data. Let me know if you think otherwise.

@Fjalapeno Agreed, thats fine for now given our current refreshing pattern and feed architecture. The long term intent is to see how many items are being generated but never viewed.

Checked with 5.0.0 (602) on iPad mini iOS 8.2 and iPhone 5 iOS 9.02.

• piwik records promptly & filters correctly the events mentioned in the above scenarios
• Save/un Save event is recorded as following

• not sequential numbering of events?