Using Amplitude

Frequently Asked Questions:  How do we avoid sending “Viewed /-” or “Loaded a Page” events to Amplitude? What settings should we enable in the Amplitude Destination for Page/Screen calls? What is the difference between Segment’s Cloud Mode vs. Device Mode?  What are the pros + cons of using Amplitude’s client-side bundled Segment integration?  How do we set session in Amplitude while using Segment in Cloud Mode? I set up the Amplitude Destination in Segment - why am I not seeing any data in Amplitude? What is Amplitude’s definition of a Session?  Handy Resources: Note: for Segment Support: please contact your designated Segment Rep or Segment support (friends@segment.com)  Getting Started with Segment   Segment Tracking Plan (for all Segment customers) Introduction to Segment Guide  Segment/ Amplitude Developer Docs Segment Product Docs Segment Developer Docs Segment + Amplitude Recipes Maximize the ROI of your Data Management Platform | January 2021About the

Do you...Hate using spreadsheet to create taxonomy? Can’t map between event name with the web/mobile page? Recently we released Amplitude Event Planner in Figma to VISUALIZE the whole taxonomy planning process! We would love to hear feedback from you! 

I want to make a Funnel where step 2 can be event a or b. Does anyone have any tips for making this?

Looking for questions, comments, and suggestions!Unreal is the one of the most popular engines for building games on consoles, PC, mobile, and VR. We’re making an effort to create an SDK plugin for it in the coming months so that game developers can add analytics in Unreal.For a beta release, we plan to support iOS with APIs in C++ and Blueprint, with support for Android during general release and other platforms further in the future.

The data points you see in the Retention chart are the deduplicated “weighted averages” of all Day N retention values and should match the percentages located in the top row of the breakdown table. It is often easier to digest retention data in Amplitude by looking at the expanded breakdown table below the chart. In the breakdown table, the asterisk means that the day is incomplete for that cohort and the percentage may change as more data comes in. Percentages with asterisks are not calculated in the average unless it is the only data point for that day.For each retention percentage in the data table, the numerator is the number of unique users who performed the return event on their Day/Week/Month N. The denominator for all rows - except the top "All Users" row - is the user count you see in the "Users" column,​ which represents the number of users in that cohort who performed the Starting event that day. Since users can perform the Starting event multiple times in the chart date ran

It is not uncommon to see retention going up, especially if your selected timeframe includes incomplete data points. The main reason why the retention is going up is that we are dealing with uneven sample sizes for each "day" of retention when the date range is very recent. For example, User A became a new user on September 30th. This user would be counted in the denominator of the Day 1 retention rate because this user has had the opportunity to be Day 1 retained. However, this user would not be counted in the Day 10 metric because today is October 2nd and the user hasn't had the opportunity to be Day 10 retained yet. User A is completely excluded in the calculation of Day 10 retention.The line graph will show you the weighted average of all the retention numbers from the user cohorts within the selected time frame. You can see the data for each individual cohort in the table below the chart. Your retention chart is going up because the user cohorts who joined later are given less tim

Have you ever wanted to know the following:Total count of device IDs used per day Number of devices that a user is using / count of devices grouped by User IDIf so, Amplitude does support a metric called PROPCOUNT in which returns the number of distinct property values for the property the event is grouped by: https://help.amplitude.com/hc/en-us/articles/115001163231#h_46d7c586-591a-4454-989e-74deab6a732fYou can use this custom formula on an Event Segmentation chart to get the total count of device IDs per day: https://analytics.amplitude.com/demo/chart/gqyzg77 And then add a second event group by UserID to get a total count of device IDs per user per day: https://analytics.amplitude.com/demo/chart/848sph6 Please note that the Event Segmentation chart is subject to the dates in the date picker. So you will only be able to see the count of devices each User ID used during the time period selected.