Use Composable Audiences when you need lifecycle-driven segmentation based on data in your warehouse, such as churn risk scores, customer lifetime value, or subscription status. Use Real-Time Audiences when you need to react immediately to live user actions, such as cart abandonment, logins, or content views.
\nNo. Composable Audiences run on a scheduled refresh cadence. They are not designed for real-time updates. You define the refresh schedule when creating the audience.
\nNo. The first time your audience runs, mParticle processes the full list of qualifying users and forwards them to downstream integrations. On subsequent runs, only users who have been added or removed are sent.
\nNot by default. Composable Audiences does not modify user profiles or interact with identity resolution (IDSync). If you enable a composable audience for hybrid use, then audience membership will be stored on user profiles in mParticle.
\nNo. Real-Time Audiences (audiences built using data stored in mParticle) and Composable Audiences are separate features and cannot be cloned across types.
\nIf you update a data model’s SQL, any audiences built on that model will reflect the new structure the next time they refresh. If your database administrator renames or drops a column that your model depends on, the model (and any audiences depending on it) may break. Coordinate schema changes with your data team, and verify that the model still returns the expected fields and structure.
\n\nBy default, for Composable Audiences, the audience size preview reflects actual user counts based on your current criteria. You can optionally use the sampling option to determine audience size which uses a sampling algorithm to determine the size. The sampling option will result in faster response times for larger data sets.
\nYou can use user data, timestamped event data (such as purchases or logins), and contextual data (such as device types or subscription plans). Each is configured using a SQL query.
\nIt depends on your account’s configured IDSync identity scope. With the default workspace-level scope, identity matching — and therefore enrichment — is limited to profiles within the workspace where the composable audience was created. If your account is configured with account-level or organization-level identity scope, mParticle can match users to profiles across workspaces within that scope, and enrichment may pull data from those additional profiles. See IDSync identity scope for more information.
\nHybrid audiences always match against production environment profiles only. User data ingested under the development environment is not eligible for identity matching and will not appear in the profile view for these audiences.
\nIf user data in the originating workspace was ingested under the development environment, those profiles will not be matched, and the originating workspace will not appear in the profile view. To have profiles from a workspace appear for hybrid audience membership, ensure that data is being sent to that workspace as production data rather than development data.
","frontmatter":{"title":"Frequently Asked Questions","order":3,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/audiences/composable-audiences/faq/"}},"staticQueryHashes":["2950460867"]}