Skip to main content

Hi 

We are capturing events from mobile app, we are thinking of 2 approaches for submitting the events, can you suggest recommended  approach by Amplitude.

 

Approach 1

 

  1. Submit page load events for each page when user navigates to each page like

Event Name

Properties

Home Screen - Loaded

From Page, Current Page, From Section, User ID

Explore Page - Loaded

From Page, Current Page, From Section, User ID

 

  1. For common functionalities in the app will capture common events but use event properties to have details like

Event Name

Properties

Section Loaded  

Section: Carousel/Featured/App Section Name , Current Page

App Featured Clicked

Feature: Feature Name, Current Page, From section, From Page, User ID

User Activity

Feature, Activity, From section, From page, Current Page, Action Performed: Back button clicked/Save button Clicked/Card clicked, Argument1, Argument2: , User ID, Action Response: Success/Failed/Passed/Error

 

 

Approach 2

 

Capture all event on page with unique names and different properties as follows:

 

Event Name

Properties

Home Screen - Loaded

From Page, Current Page, From Section, User ID

Explore Screen - Loaded

From Page, Current Page, From Section, User ID

Home Screen - Module Clicked

From Page, Current Page, From Section, User ID

Explore Screen - Module Clicked

From Page, Current Page, From Section, User ID

Home Screen – Activity Bar Clicked

From Page, Current Page, From Section, User ID

Home Screen – Carousel Slide Clicked

From Page, Current Page, From Section, User ID

Home Screen – Gratitude Clicked

From Page, Current Page, From Section, User ID

 

In this we will have lot of similar events but with different name.

 

 Thank you

Hi @Puneet Gandhi . There was a similar question a while ago, take a look here and you’ll see the responses which should hopefully guide you: 

As mentioned in there, a key consideration is whether the subsequent user journeys are fundamentally different. In our setup I use a single event names for thinks like “clicked navigation bar link”, coupled with event properties to split the page, etc…but for things like “view park page” I split these into “view park page <type>” as we have user journeys that are very different dependent on whether it’s someone looking for a holiday, looking to buy a caravan, etc.

 


Reply