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
Bulk Profile Deletion API Reference
Audit Logs API
Calculated Attributes Seeding API
Custom Access Roles API
Data Planning API
Household Reach 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
Workspace Switching
Linting Data Plans
Troubleshooting the Android SDK
API Reference
Upgrade to Version 5
Direct URL Routing FAQ
Web
Android
iOS
Cordova Plugin
Identity
Getting Started
Identity
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
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
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
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 Sharing
Audience Expansion
Match Boost
FAQ
Inclusive & Exclusive Audiences Overview
Using Logic Blocks in Audiences
Combining Inclusive and Exclusive Audiences
Inclusive & Exclusive Audiences FAQ
Audience Agent Overview
Building Audiences with the Agent
Data and Privacy
Standard Audiences (Legacy)
Predictive Audiences Overview
Using Predictive Audiences
New vs. Classic Experience Comparison
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
Cross-Account Audience Sharing
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 (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
Event
Audience
Feed
Audience
Event
Audience
Audience
Cookie Sync
Platform SDK Events
Server-to-Server Events
Event
Audience
Audience
Feed
Event
Event
Event
Data Warehouse
Event
Event
Audience
Event
Feed
Event
Event
Event
Event
Audience
Event
Event
Event
Feed
Event
Event
Audience
Feed
Event
Event
Event
Custom Feed
Data Warehouse
Event
Event
Audience
Audience
Audience
Event
Audience
Event
Event
Event
Event
Event
Audience
Event
Audience
Event
Audience
Data Warehouse
Event
Event
Audience
Cookie Sync
Event
Event
Event
Event
Event
Feed
Event
Feed
Event
Kit
Event
Audience
Event
Event
Audience
Event
Event
Event
Feed
Audience
Event
Audience
Event
Audience
Event
Audience
Audience
Microsoft Ads Audience Integration
Audience
Event
Audience
Event
Event
Event
Event
Event
Feed
Event
Event
Event
Event
Feed
Audience
Event
Event
Event
Event
Event
Event
Event
Feed
Event
Event
Audience
Custom Pixel
Feed
Event
Event
Event
Event
Event
Audience
Event
Audience
Data Warehouse
Event
Event
Audience
Audience
Event
Feed
Loyalty Feed
Audience
Audience
Event
Audience
Audience
Cookie Sync
Event
Feed
Audience
Audience
Event
Event
Audience
Audience
Event
Event
Event
Audience
Cookie Sync
Event
Audience
Cookie Sync
Feed
Audience
Event
This guide explains how to build an audience with the Audience Agent, from describing the audience you want or your business goal, to reviewing and iterating on the audience definitions the agent suggests, to saving a final audience proposal.
The agent panel opens with a message box and a set of 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 take the form of a specific question about your data, a specific audience (“users who purchased in the last 7 days”) you want to build, or a broad business goal you’re trying to reach (“re-engage customers who lapsed after one purchase”). You don’t need to know your exact event or attribute names.
If you ask about your data, the agent replies with summaries, tables, and sometimes graphs about the data in your workspace instead of an audience definition, such as:
Use what you learn to decide what to build. When you describe an audience or goal, the agent works toward a definition:
The agent works in two stages: first it prepares one or more audience definitions (up to three in a single message) for you to review and refine. When you’re happy with one of the audience definitions, you turn it into a single audience proposal that you can save as an audience.
Each definition appears as a card labeled Definition A, Definition B, and so on. Above the card, the agent summarizes the suggested name, the membership criteria, the pattern it drew on, and the refinement it thinks would help most.
Read the summary and the following details carefully to confirm the agent interpreted your intent correctly before moving on.
A definition card includes:
The header shows the suggested audience name and an estimated size. While the agent calculates, the size shows a loading indicator. If the population is too small to estimate reliably, a warning icon appears instead of a number. Hover your cursor over the warning icon to see the reason, for example: “Population is too small to accurately estimate.”
Each row states a rule 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 to show they were resolved against real entities in your workspace.
Each row shows how many platforms it draws from, such as “From 3 platforms.” You can hover your cursor over this to open the data sources popover, which lists the platforms and feeds included. Click Update platform(s) or feed selection in that popover to adjust them.
If you work in more than one workspace, you can change the workspace a definition draws from by hovering over “From … workspace” and clicking Update workspace(s) selection.
When you’re happy with an audience definition, click Create Audience Proposal to turn the definition into an audience proposal (see Step 5).
If a definition is too broad, too narrow, or doesn’t capture the exact user segment you want to target, reply conversationally with a follow-up like “make it the last 14 days” or “only users who purchased more than 3 times.” The agent revises the definition and adds a new one.
Each definition is tracked in the audience definition bar at the top of the panel, where every definition (Definition A, Definition B, and so on) shows its own size estimate. Click a definition to jump back to it in the conversation, so you can compare definitions before deciding which one to turn into a proposal.
When you’re satisfied with a definition, click Create Audience Proposal on its card to move to the proposal stage.
After you click Create Audience Proposal, the agent presents the audience proposal card with a label like Audience Proposal #1 and a note on the definition it’s built from, such as “uses Definition B.” Above the card, the agent states the estimated size and its confidence, and reminds you that you can save the proposal as-is or keep refining.
The proposal card summarizes the finalized audience:
Nothing is saved until you click Proceed to Save. To return to drafting, click Continue Refining.
When you click Continue Refining, you can keep adjusting the definition and create additional proposals. When a conversation has more than one, each proposal is numbered and tracked in the proposals bar at the top of the panel, alongside the audience definition bar. Click a proposal to jump back to it in the conversation, the same way you move between definitions, so you can compare proposals before deciding which one to save. Remember that you can save only one proposal per conversation.
After saving, the audience appears in your Audiences list and behaves like any other audience. To connect and activate it, follow Connect an Audience. The agent does not connect audiences to destinations.
Several controls are available in the agent panel itself to help you manage your conversation:
Hover the warning for the reason. “Population is too small to accurately estimate” means too few users currently match. Change the definition (for example, broaden it using a longer time window), and the size will recalculate.
The agent only uses signals that exist in your workspace and won’t substitute a weak proxy. If your request needs a metric that isn’t instrumented, it explains the dependency.
Multi-node structures, editing existing audiences, scheduled audiences, and audience activation are out of scope for this release. The agent explains the limitation and offers the closest useful next step. For manual control, use the Audience Builder.
Was this page helpful?