Data Subject Request API Version 1 and 2
Data Subject Request API Version 3
Key Management
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
Audit Logs API
Calculated Attributes Seeding API
Bulk Profile Deletion API Reference
Custom Access Roles API
Household Reach API Reference
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
Workspace Switching
Linting Data Plans
Troubleshooting the Android SDK
API Reference
Upgrade to Version 5
Upgrade to Version 6
Cordova Plugin
Identity
Direct URL Routing FAQ
Web
Android
iOS
Workspace Switching
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
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
Upgrade to Version 9
Getting Started
Identity
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 3 of the SDK
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
Composable Audiences Overview
User Guide Overview
Warehouse Setup Overview
Audience Setup
Frequently Asked Questions
Overview
Overview
User Profiles
Household Reach
Calculated Attributes Overview
Using Calculated Attributes
Create with AI Assistance
Calculated Attributes Reference
Predictions Overview
What's Changed in the New Predictions UI
View and Manage Predictions
Future Behavior Predictions Overview
Create Future Behavior Prediction
Manage Future Behavior Predictions
Create an Audience with Future Behavior Predictions
Identity Dashboard
Identity Logs
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
The new mParticle Experience
The Overview Map
Observability Overview
Observability User Guide
Observability Troubleshooting Examples
Observability Span Glossary
Key Management
Audit Logs
Platform Configuration
Event Forwarding
Event Match Quality Dashboard
Notifications
System Alerts
Trends
Introduction
Data Retention
Data Catalog
Connections
Activity
Data Plans
Live Stream
Filters
Consent Filters
Rules
Blocked Data Backfill Guide
Tiered Events
mParticle Users and Roles
Analytics Free Trial
Troubleshooting mParticle
Usage metering for value-based pricing (VBP)
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
Audiences Overview
Create an Audience
Connect an Audience
Manage Audiences
Audience Insights
Audience Sharing
Match Boost
Inclusive & Exclusive Audiences Overview
Using Logic Blocks in Audiences
Combining Inclusive and Exclusive Audiences
Inclusive & Exclusive Audiences FAQ
Audience Expansion
Predictive Audiences Overview
Using Predictive Audiences
Overview
Explore Your Data
Build Audiences
Create Predictions
Data and Privacy
mParticle Agent FAQ
Introduction
Core Analytics (Beta)
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
Dashboard Filters
Organize Dashboards
Scheduled Reports
Favorites
Time and Interval Settings in Dashboards
Query Notes in Dashboards
The Demo Environment
Keyboard Shortcuts
User Segments
Data Privacy Controls
Data Subject Requests
Default Service Limits
Feeds
Import Data with CSV Files
CSV File Reference
SFTP Credentials
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
Snowflake (Snowplow Schema)
Snowplow Schema Overview
Snowflake (Define Your Own Schema)
Aliasing
Event
Audience
Audience
Event
Feed
Cookie Sync
Platform SDK Events
Server-to-Server Events
Audience
Audience
Audience
Event
Feed
Event
Audience
Event
Event
Data Warehouse
Event
Event
Audience
Feed
Event
Event
Event
Event
Event
Event
Audience
Feed
Event
Event
Audience
Feed
Event
Event
Event
Custom Feed
Event
Data Warehouse
Event
Audience
Audience
Audience
Event
Audience
Event
Event
Event
Event
Event
Audience
Event
Audience
Event
Event
Audience
Data Warehouse
Event
Audience
Cookie Sync
Event
Event
Event
Event
Event
Feed
Feed
Event
Event
Kit
Event
Audience
Event
Event
Audience
Event
Event
Event
Feed
Audience
Event
Audience
Event
Audience
Event
Audience
Audience
Audience
Microsoft Ads Audience Integration
Event
Audience
Event
Event
Event
Event
Feed
Event
Event
Event
Event
Event
Feed
Audience
Event
Event
Event
Event
Event
Event
Event
Event
Event
Event
Feed
Event
Event
Audience
Custom Pixel
Feed
Event
Event
Event
Event
Audience
Event
Event
Audience
Data Warehouse
Event
Event
Audience
Audience
Event
Feed
Loyalty Feed
Audience
Event
Audience
Audience
Audience
Audience
Cookie Sync
Event
Feed
Audience
Event
Audience
Event
Audience
Event
Event
Event
Event
Audience
Audience
Cookie Sync
Feed
Audience
Audience
Cookie Sync
This guide explains how to use the mParticle Agent to prepare, review, refine, and save a real-time audience.
For example, you can ask the agent to identify customers who lapsed after an initial purchase, customers showing recent purchase intent, or high-value customers who are actively browsing.
You can open the mParticle Agent directly from the left-hand navigation by clicking mParticle Agent.
You can also open the mParticle Agent from Segmentation by clicking + New Audience and selecting Build with mP Agent. The agent panel will open with a message box and starter prompts for common ways to begin, such as I have a campaign goal, help me define the right audience and Show me what data I have to work with.
In the message box, ask a question or describe what you’re trying to achieve using plain language. Your query can be a specific question about your data, a specific audience such as users who purchased in the last 7 days, or a broad business goal such as re-engage customers who lapsed after one purchase. You don’t need to know the exact event or attribute names in your workspace.
If you ask about your data, the agent replies with summaries, tables, and sometimes graphs about the data available in your workspace instead of an audience definition. For example, it can describe:
To learn how best to explore available data using the agent, see Explore Your Data with the mParticle Agent.
Use what you learn to decide exactly what audience to create; when you describe an audience or goal, the agent works toward a definition:
You can also ask the agent to review pre-existing audiences. Available information can include metadata, a summary of the audience’s criteria, a complete saved definition, and whether the audience is eligible for use as an Audience Membership criterion. When a complete definition isn’t available, the agent discusses only the available summary and doesn’t infer missing criteria from the audience name. The agent doesn’t edit the saved original or expose its members.
For example, ask:
Ask the mParticle Agent to use an eligible saved audience as an Audience Membership criterion in a new real-time audience. It can use an eligible existing Composable Audience for this purpose. When you combine that membership with live behavioral criteria, the result is a hybrid real-time audience.
If a Composable Audience cannot be used, the mParticle Agent explains the limitation so you can choose another supported source or workflow. For details about Composable Audience membership and identity matching, see Hybrid Audiences.
The agent works in 2 stages. First, it prepares 1 or more audience definitions for you to review and refine. When you’re satisfied with a definition, you turn it into an audience proposal that you can save.
Each definition appears as a card labeled Definition A, Definition B, and so on. Above the card, the agent summarizes the suggested name, membership criteria, the pattern it used, and a possible refinement. Read the summary and definition details carefully to confirm that the agent interpreted your intent correctly before you continue.
The card header shows the suggested audience name and an estimated size. While the agent calculates the estimate, the size shows a loading indicator. If the population is too small to estimate reliably, a warning icon appears instead of a number. Hover over the warning icon to see the reason.
Each row states a criterion in plain language, such as performed page view WHERE url contains “checkout” more than 1 time in the last 180 days. Event and attribute names appear in color when the agent resolves them to entities in your workspace.
Each criterion shows the number of platforms or feeds it uses, such as From 3 platforms. Hover over the count to open the data sources popover, which lists the included platforms and feeds. Click Update platform(s) or feed selection in the popover to adjust them.
If you work in multiple workspaces, hover over the workspace count and click Update workspace(s) selection to change the workspace the definition uses.
Reply with the change you want if the definition is too broad, too narrow, or doesn’t capture the customers you want to reach. For example, ask the agent to use the last 14 days or include only customers who purchased more than 3 times.
The agent adds each revised definition to the audience definition bar at the top of the panel. Each entry shows the definition label and its own size estimate. Select a definition to return to it in the conversation, review its criteria, and compare it with other versions before deciding which one to turn into a proposal.
The proposal card identifies the definition it was built from and shows its estimated size and the agent’s confidence when available. It displays the proposed audience’s:
If you want to change the definition, click Continue Refining. You can adjust the definition and create another proposal. Each proposal is numbered and remains available in the proposals bar alongside the audience definition bar. Select a proposal to return to it in the conversation and compare it with other proposals before deciding which one to save.
Before saving the proposal, confirm:
Click Proceed to Save. Nothing is saved until you confirm the final proposal.
The agent doesn’t activate the saved audience or connect it to an output. You must manually activate the audience and manually connect it to an output using the mParticle UI.
Saving an audience preserves the proposal you selected, but it doesn’t preserve the other definitions, proposals, or rationale generated throughout the conversation. Use Copy chat before closing the panel if you want to retain that material.
Use the controls in the agent panel to manage the conversation:
If you close the panel without saving an audience, the exit dialog confirms that your conversation progress won’t be saved and offers an option to download a copy. After you save an audience, closing the panel doesn’t prompt you to save the conversation.
The information available for a saved audience can vary. When a complete saved definition is available, the agent can explain it. Otherwise, it can discuss only the available summary and won’t infer missing criteria from the audience name.
Open the saved audience in the Audience Builder to review or edit information that isn’t available to the agent.
Review the Agent’s explanation for why the selected Composable Audience cannot be used. Choose another eligible audience or see Hybrid Audiences for details about how Composable Audience membership becomes available in real-time audiences.
The mParticle Agent prepares one new individual real-time audience per creation flow. It can’t edit an existing audience, create or restructure an Audience Group, create a Composable Audience, activate an audience, or connect an audience to an output.
If the goal requires an Audience Group or changes to a saved audience, continue in the Audience Builder.
Hover over the warning icon to see why the agent couldn’t provide an estimate. If the population is too small to estimate reliably, broaden the definition and wait for the size to recalculate.
Was this page helpful?