Trying to evaluate the usage interval of a product, i want to be able to segment users that did a critical action twice in two separate sessions - Any idea how that could be done on Amplitude?
Hi, My first guess would be to play with some of Amplitude’s own properties and events (User ID, Session ID, Historical Count, Start Session...) and use a segmentation chart. Here’s an AmpliTunes example of how to compute the amount of unique users who performed a critical action (Play song or video) and launched two or more session in a month (users “who performed Start Session >=2 times”) : https://analytics.amplitude.com/demo/chart/new/fsfup4d?source=copy+urlHowever, I do not know how to solve the issue of segmenting by taking into account the fact that the “critical action” took place in separate sessions.Best of luck
Hi The Product Manager ,
I like the solution from Matrak above! Another way is you could possibly use the sessions chart and only include sessions that did a particular event. You can then see different sessions where this event was triggered. You could then group it by user ID for example. Another option is to use the funnel chart and if you are tracking session IDs, you could make a funnel and hold the session ID constant and look at event totals and then group by the Device or User ID to see the user’s with a high amount of events within the same session.
I hope this helps!
Kind Regards,Denis
Thanks Matrak, Denis Holmes,
You guys are Pro’s! Although my main challenge is still being able to ensure that a specific event happened within a two separate sessions.
Your’e suggestions get me close yet unfortunately the challenge remains, Denis Holmes i might be able to do it by exporting and manually segmenting the users by Id’s and later using a funnel to check the time to convert…. Though i won’t be able to ensure that the time it took to convert the second time would be for that event in a separate session, it would include users that do that action twice in the same session.
It would have been way easier with a paid plan using the “Usage Interval View” - The company I’m consulting isn’t yet ready to upgrade so i’m trying to help with a work-around.
If you have any other thoughts, please share! Thanks Guys!
Hi The Product Manager,
Usage Interval View would be a good way to go. Unfortunate that they do not want to upgrade. You could use the funnel chart and use event totals but it can be hard to see exactly the users who did this event across two sessions. You could try make a cohort of users from the chart such as here for users who did the event once in a session and then seem, out of those users, if there is any who did the session across two events. However, I do not think there is a very applicable workaround at this time.
Regards,Denis
Hello! In React-Native mobile project we have error: Amplitude Logger [Error]: Failed to set cookie for key: AMP_TEST. Error: Cannot set property 'cookie' of undefined Error Component Stack: ``` The package version is "@amplitude/analytics-react-native": "1.5.1", Steps to Reproduce: * Initialize Amplitude with our API key…
We implemented first party tracking using the basic JS SDK on the browser and pointing the payload to our servers like this: amplitude.init(AMPLITUDE_API_KEY, { serverUrl: serverUrl, autocapture: { attribution: { excludeReferrers: [/domain1\.com$/, /domain2\.com$/], }, formInteractions: false, fileDownloads: false, }, });…
My Android app is primarily a background app. Does Amplitude track events for such an app? Please let me know.
here is the referance graph: https://app.amplitude.com/analytics/demo/chart/new/363tk5og In this graph, retention is currently being calculated based on the next day, but I want to analyze it based on the previous day instead. Example: For July 27, we should compare retention against July 26, not July 28. * So for 1-day…
Hi everybody! I need your help with a client request: my client is used to analyze landing pages performance with the standard report from GA4 and I need to create something similar in Amplitude. What I already have: * session entries grouped by page URL * purchase event calculated as session totals grouped by page URL and…
