Decipher the product analytics & logging for Product Managers

Rohit Verma
2 min readAug 23, 2022

It’s a best practice for PMs to ensure that their product has rich product analytics & logging across all touch points of the users.

What are events?

For instance, when a user clicks on your CTA of “Proceed”, it translates into an event. These events aren’t automatically triggered for consumption. Mostly the front-end engineer will add a code for the action recommended by the PMs. This is also referred to as “adding instrumentation”.

What type of information can be passed in the events?

It can go as granular as required. This information is often referred to as metadata passed while logging an event. For instance, it can include below metadata :

  • Name of the event
  • Time of the event
  • Unique ID of the user
  • Platform used by the user
  • OS version of the user
  • Device type
  • Communication/Error message displayed to the user

What happened once the event information is triggered?

PMs often consume this data with the help of the product analytics team. The product analytics team process these data points & try to present them in the consumable format in terms of a tableau dashboard to the PMs & other relevant stakeholders.

A quick example

PFB the snapshot of the signup screen.

Based on the respective nomenclature followed by the product analytics, most of the information is documented below format :

  • screen_name: enteryourmobileno
  • event_type : click
  • event_sub_type : button
  • event_name : next
  • event_id :
  • event_metadata: {“Mobile no”:”9999999999", “Full name”:”,” Referral code”:” WINNER76”, message:” name is empty”}

Thanks for reading! If you’ve got ideas to contribute to this conversation please comment. If you like what you read and want to see more, clap me some love! Follow here, or connect with me on LinkedIn or Twitter.

Do check out exclusive Product Management resources 👇



Rohit Verma

Group Product Manager @AngelOne, ex-@Flipkart, @Cleartrip @IIM Bangalore.