help.mixpanel.com Open in urlscan Pro
104.16.53.111  Public Scan

Form analysis
4 forms found in the DOM

GET /hc/en-us/search

<form role="search" class="search" data-search="" data-instant="true" autocomplete="off" action="/hc/en-us/search" accept-charset="UTF-8" method="get" __bizdiag="-256754706" __biza="WJ__"><input name="utf8" type="hidden" value="✓"
    autocomplete="off"><input type="search" name="query" id="query" placeholder="Search our articles" autocomplete="off" aria-label="Search" class="aa-input" spellcheck="false" role="combobox" aria-autocomplete="list" aria-expanded="false"
    aria-labelledby="query" aria-owns="algolia-autocomplete-listbox-0" dir="auto" style="">
  <pre aria-hidden="true"
    style="position: absolute; visibility: hidden; white-space: pre; font-family: &quot;Apercu Pro&quot;, sans-serif; font-size: 16px; font-style: normal; font-variant: normal; font-weight: 500; word-spacing: 0px; letter-spacing: 0.1px; text-indent: 0px; text-rendering: auto; text-transform: none;"></pre>
  <input type="submit" name="commit" value="Search">
</form>

GET /hc/en-us/search

<form role="search" class="search-box search-box--mobile" data-search="" data-instant="true" autocomplete="off" action="/hc/en-us/search" accept-charset="UTF-8" method="get" __bizdiag="-256754706" __biza="WJ__"><input name="utf8" type="hidden"
    value="✓" autocomplete="off"><input type="search" name="query" id="query" placeholder="Search our articles" autocomplete="off" aria-label="Search" class="aa-input" spellcheck="false" role="combobox" aria-autocomplete="list" aria-expanded="false"
    aria-labelledby="query" aria-owns="algolia-autocomplete-listbox-1" dir="auto" style="">
  <pre aria-hidden="true"
    style="position: absolute; visibility: hidden; white-space: pre; font-family: &quot;Apercu Pro&quot;, sans-serif; font-size: 16px; font-style: normal; font-variant: normal; font-weight: 500; word-spacing: 0px; letter-spacing: 0.1px; text-indent: 0px; text-rendering: auto; text-transform: none;"></pre>
  <input type="submit" name="commit" value="Search"><button class="btn btn--default btn--search-topbar-close" data-toggle-search="true"><span class="fa fa-close"></span></button>
</form>

<form class="feedback_forms" __bizdiag="103858620" __biza="WJ__">
  <div id="hidden_fields">
    <input type="hidden" name="article_id" value="115005708186">
    <input type="hidden" name="article_name" value="Cohorts Overview ">
    <input type="hidden" name="helpful?" value="Yes">
    <input type="hidden" name="choice" value="N/A">
  </div>
  <textarea id="feedback_up" maxlength="600" rows="4" name="feedback_text" placeholder="Please let us know if you had any thoughts or suggestions." style="display: inline-block; margin: 0px; width: 100%; height: 120px;" spellcheck="true"></textarea>
  <div style="padding-top:10px">
    <input type="submit" value="Submit Feedback" id="neg-form-submit">
  </div>
</form>

<form class="feedback_forms" __bizdiag="-1851408545" __biza="WJ__">
  <div style="padding-bottom:10px">
    <div style="margin-right:10px;text-align:left;padding-bottom:2px">
      <input type="radio" name="choice" id="feedback_option_1" value="helpfulness">
      <label for="feedback_option_1">This article did not answer the question I thought it would.</label>
    </div>
    <div style="margin-right:10px;text-align:left;padding-bottom:2px">
      <input type="radio" name="choice" id="feedback_option_2" value="clarity">
      <label for="feedback_option_2">The information was confusing or difficult to read.</label>
    </div>
    <div style="margin-right:10px;text-align:left;padding-bottom:2px">
      <input type="radio" name="choice" id="feedback_option_3" value="product">
      <label for="feedback_option_3">I don't like how this feature works.</label>
    </div>
    <div style="margin-right:10px;text-align:left;padding-bottom:2px">
      <input type="radio" name="choice" id="feedback_option_4" value="other">
      <label for="feedback_option_4">Other.</label>
    </div>
    <div id="hidden_fields">
      <input type="hidden" name="article_id" value="115005708186">
      <input type="hidden" name="article_name" value="Cohorts Overview ">
      <input type="hidden" name="helpful?" value="No">
    </div>
  </div>
  <textarea id="feedback_down" maxlength="600" rows="4" name="feedback_text" placeholder="Please let us know more about your question and any thoughts on what we could do to improve."
    style="display: inline-block; margin: 0px; width: 100%; height: 120px;" spellcheck="true"></textarea>
  <div style="padding-top:10px">
    <input type="submit" value="Submit Feedback" id="neg-form-submit">
  </div>
</form>

Text Content

toggle menu





Help Center Contact Support
 1. Mixpanel Help Center
 2. Analysis
 3. Advanced


COHORTS OVERVIEW

Marissa Kuhrau
December 09, 2017 20:45


Cohorts are groups of users defined by a chosen set of criteria, like a shared
property or sequence of events. When you define a cohort, you can use it to
group and filter data in the Analysis reports. You can also use cohorts to
target groups of users via messaging integrations. 


USE COHORTS IN REPORTS

Cohorts can be created almost anywhere within Mixpanel.  

You can create a new cohort from the Insights, Flows, Funnels, Retention, and
Impact Reports. To do so, click "Create Custom" > "Cohort" from within any
Filter or Breakdown menu.



You can also create cohorts directly from the charts in Retention reports or
Funnels reports.

You can create and save cohorts in the Users page as well.

Finally, cohorts can be created via the Create Cohort button at the top right of
the Cohorts management page, found in the Data Management menu.

After you create a cohort, you can use it to analyze your user data in the
Analysis Reports.


VISUALIZE COHORTS OVER TIME

Select a cohort from the Insights drop down menu to see how the number of users
in the cohort has changed over time.



When you visualize a cohort over time, you can breakdown by another cohort,
compare to an event, or compare to another cohort.


NOTE ON COHORTS WHOSE FILTERS CONTAIN USER PROFILE PROPERTIES:

Because user profile properties only store the most recent value, cohorts
involving user profile properties will use the current value for those
properties (even if the value changed over time).

For example, suppose the cohort's filter criteria is: users where user[“City”]
== “SF” and “Did Event: Order Ride 3 times in Last 7 days”.

Mixpanel computes the above over the last 30 days and then groups the set of
users who have property user[“City”] == “SF” as of right now and intersect that
with the daily cohort of users who did Order Ride 3 times in the last 7 days.


COHORTS CHARACTERISTICS

Cohorts have several characteristics that affect results in Mixpanel reports.
While Cohorts are intuitive, the following traits are important to realize when
interpreting results.


COHORTS ARE DYNAMIC

Users qualify for a cohort based on the specified conditions. This doesn’t
ensure that that user will always be in the cohort.

For example, assume the condition of the cohort is performing a “Song Play”
event in the last 30 days. If a user plays a song once in thirty days, they will
enter the cohort. If that user doesn’t listen to another song at the 30 day
mark, however, then they will exit the cohort as they no longer meet the
qualifying condition of having performed a “Song Play” event in the last 30
days.


COHORTS ARE ALWAYS CURRENT AT THE TIME YOU RUN A REPORT

When you run a report that involves a cohort, Mixpanel returns the group of
users that meet the criteria for that cohort at the moment.

This is important to consider when running a report with a “From Date” and “To
Date” selected. The analyzed cohort will not be the cohort during the “From
Date” and “To Date” time period. The analyzed cohort will be users currently in
the cohort.


EXPORT COHORTS

From Data Management -> Cohorts, click Export in the inline action menu to
export a cohort list to a webhook or an integration 



To download a csv, click View Users and then click Export CSV. The CSV file will
automatically download. 

NOTE:

 * The export will only show the user profile properties of users in the cohort
   that are viewable in the currently displayed table at the time of export. You
   don't get ALL of a user's profile properties.
 * Users who exist in the cohort that don't have a user profile will appear in
   the CSV as a distinct_id only.


DELETE COHORTS

Click on the trash icon or click Delete in the inline action menu to delete a
cohort.



If you create cohorts based off of other cohorts, you will not be able to delete
the original cohort the new cohort is dependent on.

For example, you can create a new cohort A which combines cohorts B and C, but
you will not be able to delete cohorts B or C, until you delete cohort A.


Did this answer your question?
60 out of 115 found this helpful

This article did not answer the question I thought it would.
The information was confusing or difficult to read.
I don't like how this feature works.
Other.




COMMENTS

0 comments

Article is closed for comments.


ARTICLES IN THIS SECTION

 * Lookup Tables Overview
 * Query Builder Features
 * Cohorts Overview
 * Create Cohorts
 * Impact Report
 * Experiments Report
 * Signal Report
 * Slack / Mixpanel Integration
 * Custom Events
 * Custom Properties

See more

   
 * Use Cohorts in Reports
 * Cohorts Characteristics
 * Export Cohorts
 * Delete Cohorts

Product
 * Team Dashboards & Alerts
 * Interactive Reports
 * Limitless Segmentation
 * Group Analytics
 * Data Integrations
 * Scalable Infrastructure
 * Security & Privacy
 * Integration Directory

Resources
 * Product Updates
 * Customer Stories
 * Blog
 * Content Library
 * Webinars
 * User Community
 * Partners
 * Topics
 * Sitemap

Support
 * Contact Us
 * Developer Docs
 * Help Center

Company
 * About Us
 * Press
 * Careers
 * Legal
 * Your Privacy Rights

--------------------------------------------------------------------------------

All Systems Operational © 2020 Mixpanel. All rights reserved Terms Privacy
Policy