Data Subject Request API Version 1 and 2
Data Subject Request API Version 3
Platform API Overview
Accounts
Apps
Audiences
Calculated Attributes
Data Points
Feeds
Field Transformations
Services
Users
Workspaces
Warehouse Sync API Overview
Warehouse Sync API Tutorial
Warehouse Sync API Reference
Data Mapping
Warehouse Sync SQL Reference
Warehouse Sync Troubleshooting Guide
ComposeID
Warehouse Sync API v2 Migration
Bulk Profile Deletion API Reference
Calculated Attributes Seeding API
Custom Access Roles API
Data Planning API
Group Identity API Reference
Pixel Service
Profile API
Events API
mParticle JSON Schema Reference
IDSync
AMP SDK
Initialization
Configuration
Network Security Configuration
Event Tracking
User Attributes
IDSync
Screen Events
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Push Notifications
WebView Integration
Logger
Preventing Blocked HTTP Traffic with CNAME
Linting Data Plans
Troubleshooting the Android SDK
API Reference
Upgrade to Version 5
Direct URL Routing FAQ
Web
Android
iOS
Cordova Plugin
Identity
Initialization
Configuration
Event Tracking
User Attributes
IDSync
Screen Tracking
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Push Notifications
Webview Integration
Upload Frequency
App Extensions
Preventing Blocked HTTP Traffic with CNAME
Linting Data Plans
Troubleshooting iOS SDK
Social Networks
iOS 14 Guide
iOS 15 FAQ
iOS 16 FAQ
iOS 17 FAQ
iOS 18 FAQ
API Reference
Upgrade to Version 7
Getting Started
Identity
Upload Frequency
Getting Started
Opt Out
Initialize the SDK
Event Tracking
Commerce Tracking
Error Tracking
Screen Tracking
Identity
Location Tracking
Session Management
Getting Started
Identity
Initialization
Configuration
Content Security Policy
Event Tracking
User Attributes
IDSync
Page View Tracking
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Custom Logger
Persistence
Native Web Views
Self-Hosting
Multiple Instances
Web SDK via Google Tag Manager
Preventing Blocked HTTP Traffic with CNAME
Facebook Instant Articles
Troubleshooting the Web SDK
Browser Compatibility
Linting Data Plans
API Reference
Upgrade to Version 2 of the SDK
Web
Alexa
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Step 9. Test your local app
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Step 1. Create an input
Step 2. Create an output
Step 3. Verify output
Node SDK
Go SDK
Python SDK
Ruby SDK
Java SDK
Introduction
Outbound Integrations
Firehose Java SDK
Inbound Integrations
Compose ID
Data Hosting Locations
Glossary
Migrate from Segment to mParticle
Migrate from Segment to Client-side mParticle
Migrate from Segment to Server-side mParticle
Segment-to-mParticle Migration Reference
Rules Developer Guide
API Credential Management
The Developer's Guided Journey to mParticle
Create an Input
Start capturing data
Connect an Event Output
Create an Audience
Connect an Audience Output
Transform and Enhance Your Data
The new mParticle Experience
The Overview Map
Introduction
Data Retention
Connections
Activity
Live Stream
Data Filter
Rules
Tiered Events
mParticle Users and Roles
Analytics Free Trial
Troubleshooting mParticle
Usage metering for value-based pricing (VBP)
Introduction
Sync and Activate Analytics User Segments in mParticle
User Segment Activation
Welcome Page Announcements
Project Settings
Roles and Teammates
Organization Settings
Global Project Filters
Portfolio Analytics
Analytics Data Manager Overview
Events
Event Properties
User Properties
Revenue Mapping
Export Data
UTM Guide
Data Dictionary
Query Builder Overview
Modify Filters With And/Or Clauses
Query-time Sampling
Query Notes
Filter Where Clauses
Event vs. User Properties
Group By Clauses
Annotations
Cross-tool Compatibility
Apply All for Filter Where Clauses
Date Range and Time Settings Overview
Understanding the Screen View Event
Analyses Introduction
Getting Started
Visualization Options
For Clauses
Date Range and Time Settings
Calculator
Numerical Settings
Assisted Analysis
Properties Explorer
Frequency in Segmentation
Trends in Segmentation
Did [not] Perform Clauses
Cumulative vs. Non-Cumulative Analysis in Segmentation
Total Count of vs. Users Who Performed
Save Your Segmentation Analysis
Export Results in Segmentation
Explore Users from Segmentation
Getting Started with Funnels
Group By Settings
Conversion Window
Tracking Properties
Date Range and Time Settings
Visualization Options
Interpreting a Funnel Analysis
Group By
Filters
Conversion over Time
Conversion Order
Trends
Funnel Direction
Multi-path Funnels
Analyze as Cohort from Funnel
Save a Funnel Analysis
Explore Users from a Funnel
Export Results from a Funnel
Saved Analyses
Manage Analyses in Dashboards
Dashboards––Getting Started
Manage Dashboards
Organize Dashboards
Dashboard Filters
Scheduled Reports
Favorites
Time and Interval Settings in Dashboards
Query Notes in Dashboards
User Aliasing
The Demo Environment
Keyboard Shortcuts
Analytics for Marketers
Analytics for Product Managers
Compare Conversion Across Acquisition Sources
Analyze Product Feature Usage
Identify Points of User Friction
Time-based Subscription Analysis
Dashboard Tips and Tricks
Understand Product Stickiness
Optimize User Flow with A/B Testing
User Segments
IDSync Overview
Use Cases for IDSync
Components of IDSync
Store and Organize User Data
Identify Users
Default IDSync Configuration
Profile Conversion Strategy
Profile Link Strategy
Profile Isolation Strategy
Best Match Strategy
Aliasing
Overview
Create and Manage Group Definitions
Introduction
Catalog
Live Stream
Data Plans
Blocked Data Backfill Guide
Predictive Audiences Overview
Using Predictive Audiences
Predictive Attributes Overview
Create Predictive Attributes
Assess and Troubleshoot Predictions
Use Predictive Attributes in Campaigns
Introduction
Profiles
Warehouse Sync
Data Privacy Controls
Data Subject Requests
Default Service Limits
Feeds
Cross-Account Audience Sharing
Approved Sub-Processors
Import Data with CSV Files
CSV File Reference
Glossary
Video Index
Single Sign-On (SSO)
Setup Examples
Introduction
Introduction
Introduction
Rudderstack
Google Tag Manager
Segment
Advanced Data Warehouse Settings
AWS Kinesis (Snowplow)
AWS Redshift (Define Your Own Schema)
AWS S3 Integration (Define Your Own Schema)
AWS S3 (Snowplow Schema)
BigQuery (Snowplow Schema)
BigQuery Firebase Schema
BigQuery (Define Your Own Schema)
GCP BigQuery Export
Snowplow Schema Overview
Snowflake (Snowplow Schema)
Snowflake (Define Your Own Schema)
Aliasing
The Cohort tool allows you to understand how often your customers return and engage with your website or product.
To begin a cohort query, determine an initiating event (called the Cohort event). The first event of a cohort is required; a user must complete the initiating event or Cohort event and then return to perform a second event which is explained in the section “Target Behavior”. Custom Events and Merged Events can be used. As with other tools, you may apply a Filter Where.
You may select a different time zone from your project time zone on a per query basis by locating the globe icon on the top right of the query screen.
You can chain multiple events in a sequence using an “and then performed” clause to define your cohort of users. In the following example, PetBox wants to measure users who download their app, and then start the app.
In addition to the first event, cohorts can be defined by a shared generation or a shared property. A generation is a unit of time, such as a month. A monthly cohort would include all users who entered the cohort during that month. A property is a characteristic or attribute, such as device type. Cohorts defined by device type would include all users with an iPhone, all users with an Android, etc. A user will only appear once in the results of a cohort analysis. For generation cohorts, users will be put into the property breakout in which they first appear during the time interval.
After selecting an initiating event, you must select a Target Behavior event. This second event of a cohort is also required; Custom Events and Merged Events can be used. As with the initiating event, you are also able to apply a Filter Where.
Revenue: Target behavior can also be represented as revenue. Using revenue as the target behavior will analyze the revenue generated over time by each cohort.
Every query requires you to select a date range. In Cohort analysis, the date range refers to the time period during which a user completes all steps of the cohort query, defined in Row A. All new queries default to Last 30 Days. To open the date range selector dropdown, click on Last 30 Days. The start date is the first day to be included in the search. The end date is the last day. As mentioned in Cohort Basics, you can set the time zone for your Cohort query.
Every cohort is defined by a first event, a breakout, and a second event. To appear in the results, a user must complete the first event and also have a defined value in the breakout. Breakouts may be an Event Property, a User Property, or a User Segment; or they may be a Generation; or they may be a combination. A generation is a time-based grouping that describes the cohort. It describes when the first event occurred. You may select Hour, Day, Week, or Month. For example, to create monthly cohorts of users using the date they signed for a newsletter, the first event would be Newsletter Signup and the generation would be Monthly. This will produce a list of all users who signed up for the newsletter, broken out by month: January signups, February signups, March signups, etc.
To select fixed start and end dates, use the date range selector on the left side of the dropdown, you may select a start date and end date from the calendar. You can also enter a specific date by selecting on the date at the top of the selector and entering a value. Use the left and right arrows to navigate the calendar. Tick the Today checkbox to create a dynamic end date.
The right side of the dropdown lists all of the dynamic date ranges that are available. You may choose a dynamic date range, for example Last 7 Days or Last Full Month. This will automatically update the date range of your query each time you view it, counting backwards from today. If you select Last Full Week, then Analytics will analyze the most recent complete week, defined as Monday to Sunday. If you select Last Full Month, then Analytics will analyze the most recent complete month. You can quickly navigate the calendar to select full months using the links in the lower left corner of the dropdown.
To save a custom date range, for example Last 45 Days, simply click Add Custom Date Range in the lower right corner of the dropdown. Your previously used custom date ranges will be saved for future use and are viewable alongside the default dynamic date ranges.
In Cohort, the interval describes the time period during which a user completes the Target Behavior, defined in Row C. You may choose hourly, daily, weekly, or monthly intervals. Interval options are dependent on the generation and date range selected.
For example, if the selected date range is Last 7 Days, then the available time intervals will be hourly and daily. Weekly will not be available because there is only one week in a seven day date range. If the date range is changed to Last 90 Days, then the intervals dropdown will update with the additional options of weekly and monthly, but will no longer allow hourly analysis due to the inability to visualize.
To calculate the total event count or user count across an entire date range, match the duration and interval of the report. Hourly intervals are only available if a cohort is defined by an hourly or daily generation.
In the results section, intervals are listed as columns. Interval 1 is the same interval during which the first event was completed. Interval 2 is the next interval after, and so on. If the interval is set to daily and a user completed the target behavior within the same day, then they will appear in Day 0.
Note: For Cohort queries with the time interval set to Daily, “Day 0” captures users who completed the target behavior in the subsequent 24 hours after entering the cohort (meeting the definition for inclusion).
For example, a user who performed Site Visit on Jan 1 at 1pm (and thus entered the cohort) would be included in Day 0 as long as they performed Subscribe (the target behavior) at any time before 1pm on Jan 2. Events are tracked down to the millisecond, and will be categorized in intervals by this level of precision.
You may adjust your cohort query to observe the frequency of recurring target behavior or to measure the first time that the target behavior occurred after completing the first event. If a query is set to Recurring, then a user will appear multiple times within a row if the user repeated the target Behavior multiple times. If a query is set to First-Time, then a user will appear only once in a row, describing when they completed the target behavior.
To exemplify the difference between recurring and first-time cohort queries, consider a box subscription company that wants to measure customer behavior among their newsletter subscribers. The first event could be “Newsletter Sign Up” and the target behavior could be “Purchase”. User A signed up for the newsletter in January, and then completed purchases in March, April, and May. In a recurring cohort query, the user will appear in the January cohort row, and they will appear in the Month 3, Month 4, and Month 5 columns. In a first-time cohort query, the user will appear only in the Month 3 column. Thus, exclusivity of cohorts as they appear in the interval counts only occurs in a first-time cohort. Recurring cohorts can have a user appear in multiple intervals, though the total number of users will be exclusive.
All new queries default to the Non-Cumulative setting. Non-cumulative cohort queries show the count or percentage of users in the cohort who performed the target behavior within the interval. Cumulative cohort queries show the count or percentage of users in the cohort who performed the target behavior as a running total over time. Cumulative counts are only available for queries measuring first-time behavior. For a full explanation of cumulative and non-cumulative, see Cumulative vs. Non-Cumulative Analysis in Cohort.
Cohort analyses have four different visualization options: Circle Heatmap, Heatmap, Line Chart and Area Chart. You can toggle between these options in the visualization dropdowns. You can also download a cohort analysis as a CSV file.
Cohort annotations act as general notes about the cohort analysis over the entire designated date range. To add an annotation to Cohort, click on the Annotation flag icon in the query builder window and click Add an Annotation. To access existing annotations, click the Annotation icon in the Data Panel. For more information about annotations, visit this article.
Was this page helpful?