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
Calculated Attributes Seeding API
Bulk Profile Deletion API Reference
Group Identity API Reference
Custom Access Roles API
Data Planning API
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
Cordova Plugin
Identity
Direct URL Routing FAQ
Web
Android
iOS
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
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
Getting Started
Identity
Web
Alexa
Node SDK
Go SDK
Python SDK
Ruby SDK
Java SDK
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
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
Overview
Overview
User Profiles
Overview
Create and Manage Group Definitions
Calculated Attributes Overview
Using Calculated Attributes
Create with AI Assistance
Calculated Attributes Reference
What are predictive attributes?
Create an Input
Start capturing data
Connect an Event Output
Create an Audience
Connect an Audience Output
Transform and Enhance Your Data
Usage and Billing Report
Observability Overview
Observability User Guide
Observability Troubleshooting Examples
Observability Span Glossary
The new mParticle Experience
The Overview Map
Event Forwarding
System Alerts
Trends
Introduction
Data Retention
Data Catalog
Connections
Activity
Data Plans
Live Stream
Filters
Rules
Blocked Data Backfill Guide
Tiered Events
mParticle Users and Roles
Analytics Free Trial
Troubleshooting mParticle
Usage metering for value-based pricing (VBP)
Audiences Overview
Create an Audience
Connect an Audience
Manage Audiences
Real-time Audiences (Legacy)
Standard Audiences (Legacy)
Predictive Audiences Overview
Using Predictive Audiences
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
Introduction
Core Analytics
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
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
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
User Attributes at Event Time
Understanding the Screen View Event
User Aliasing
Dashboards––Getting Started
Manage Dashboards
Organize Dashboards
Dashboard Filters
Scheduled Reports
Favorites
Time and Interval Settings in Dashboards
Query Notes in Dashboards
The Demo Environment
Keyboard Shortcuts
User Segments
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 (Snowplow Schema)
AWS S3 Integration (Define Your Own Schema)
BigQuery (Snowplow Schema)
BigQuery Firebase Schema
BigQuery (Define Your Own Schema)
GCP BigQuery Export
Snowflake (Snowplow Schema)
Snowplow Schema Overview
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 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.
Once you have defined your cohort, you can continue to add precision to your analysis with the following settings:
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.
Fixed start and end dates Use the date range selector on the left side of the dropdown to 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.
Dynamic date ranges 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.
Custom ranges 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.
The generation setting in cohort analyses determines how users are grouped based on when they first performed a specified event. It defines the cohort’s starting point and can be set to an hourly, daily, weekly, or monthly interval. For example, if you create monthly cohorts based on newsletter signups, users will be grouped by their signup month (e.g., January signups, February signups, etc.).
Hourly
Daily
Weekly
Monthly
Cohort queries can track either recurring target behavior or the first occurrence of a behavior after the initial event.
Example:
A box subscription company tracks purchases after a “Newsletter Sign Up” event.
First-time queries enforce exclusivity per interval, while recurring queries allow users to appear in multiple intervals.
By default, cohort queries use the Non-Cumulative setting.
For more details, see Cumulative vs. Non-Cumulative Analysis in Cohort.
Available Metrics:
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?