Defining 24-Hour Gaps in Retention Reports with Kapa.ai

Moritz H. · 2025-08-08 20:50:18.322278+00

For retention reports, can I define that between each action there must be at least 24 hours of time, otherwise it is not counted? And then it should also show me if there were for example four actions: Action 1 > 24 hours+ > Action 2 > 24 hours+ > Action 3 > 24 hours+ > Action 4

Mixpanel is headed to Money20/20 October 26 - 29 in Las Vegas, Nevada!

Defining 24-Hour Gaps in Retention Reports with Kapa.ai | Mixpanel Community

5 comments

· Sorted by Oldest

kapa.ai
APP
·
·
Please stand by Moritz H. as I search the knowledge base. I normally take about 15 seconds or so. 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
I'm sorry, but the knowledge sources do not indicate that Mixpanel's retention reports natively support enforcing a minimum time interval (such as 24 hours) between each action in a retention sequence. The retention report allows you to define the time window for when a user must return (e.g., on Day 1, Day 2, etc.), and you can use custom retention brackets to group days into intervals (e.g., Days 1–3, Days 4–7), but there is no explicit feature to require that each subsequent action must occur at least 24 hours after the previous one to be counted as retained.Mixpanel's retention logic is based on users returning within or on specific time units after the initial event, not on enforcing a minimum gap between each action in a sequence. The closest available options are: - Custom retention brackets, which let you group retention buckets into custom intervals, but these do not enforce a minimum gap between actions—just that the action occurs within a certain window after the initial event Custom Retention Brackets. - Retention criteria such as "On," "On or After," and "Streak mode," which define when a user must return, but not the minimum time between each action Retention Criteria.If you need to analyze sequences where each action must be separated by at least 24 hours, you may need to preprocess your data outside of Mixpanel or use a different type of analysis, as this specific functionality is not described in the available documentation.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Moritz H.
·
·
kapa.ai My main problem is that I am comparing in my retention report two times action A. Quite a few people are doing the second action A in the same session, just a few minutes later after the first action A. But for me it's much more important information if action A was repeated at least after 24 hours after the first action A. What would you recommend to me?
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
Mixpanel’s standard retention reports do not provide a built-in way to enforce a minimum time gap (such as 24 hours) between repeated actions of the same event (e.g., “Action A” followed by “Action A” at least 24 hours later). The retention logic is based on users returning within or on specific time units after the initial event, but it does not filter out repeated actions that occur within the same session or less than 24 hours apart Retention: Measure engagement over time.What you can do:Summary: Mixpanel does not natively support filtering retention by a minimum time gap between repeated actions. For your use case, preprocessing your data to identify and count only those “Action A” events that occur at least 24 hours apart is the most reliable approach, as the platform’s built-in retention and session features do not offer this level of control.If you need more granular control, consider exporting your raw event data, applying your 24-hour filter logic, and then using the results for further analysis in Mixpanel or another tool.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

kapa.ai
APP
·
·
Please stand by Moritz H. as I search the knowledge base. I normally take about 15 seconds or so. 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
I'm sorry, but the knowledge sources do not indicate that Mixpanel's retention reports natively support enforcing a minimum time interval (such as 24 hours) between each action in a retention sequence. The retention report allows you to define the time window for when a user must return (e.g., on Day 1, Day 2, etc.), and you can use custom retention brackets to group days into intervals (e.g., Days 1–3, Days 4–7), but there is no explicit feature to require that each subsequent action must occur at least 24 hours after the previous one to be counted as retained.Mixpanel's retention logic is based on users returning within or on specific time units after the initial event, not on enforcing a minimum gap between each action in a sequence. The closest available options are: - Custom retention brackets, which let you group retention buckets into custom intervals, but these do not enforce a minimum gap between actions—just that the action occurs within a certain window after the initial event Custom Retention Brackets. - Retention criteria such as "On," "On or After," and "Streak mode," which define when a user must return, but not the minimum time between each action Retention Criteria.If you need to analyze sequences where each action must be separated by at least 24 hours, you may need to preprocess your data outside of Mixpanel or use a different type of analysis, as this specific functionality is not described in the available documentation.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Moritz H.
·
·
kapa.ai My main problem is that I am comparing in my retention report two times action A. Quite a few people are doing the second action A in the same session, just a few minutes later after the first action A. But for me it's much more important information if action A was repeated at least after 24 hours after the first action A. What would you recommend to me?
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
Mixpanel’s standard retention reports do not provide a built-in way to enforce a minimum time gap (such as 24 hours) between repeated actions of the same event (e.g., “Action A” followed by “Action A” at least 24 hours later). The retention logic is based on users returning within or on specific time units after the initial event, but it does not filter out repeated actions that occur within the same session or less than 24 hours apart Retention: Measure engagement over time.What you can do:Summary: Mixpanel does not natively support filtering retention by a minimum time gap between repeated actions. For your use case, preprocessing your data to identify and count only those “Action A” events that occur at least 24 hours apart is the most reliable approach, as the platform’s built-in retention and session features do not offer this level of control.If you need more granular control, consider exporting your raw event data, applying your 24-hour filter logic, and then using the results for further analysis in Mixpanel or another tool.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.