Watch the demo
QAiry 2.1: changes the way SFMC teams build audiences
QAiry 2.1 is designed for the real segmentation workflow: You can write a request in natural language, ask for audience suggestions that are realistic in your environment, refine the rules, and then activate with confidence.
Your data model
QAiry synchronizes your Data Extensions metadata (names, fields, and data types) so the AI can generate audiences that match your real environment. When QAiry creates a new Data Extension, it follows the same structure — including naming conventions and field typing (Email, Phone, Number, Text, Date, Boolean, etc.).
Metadata sync
- DE names, fields, and data types are synced
- Audience logic maps to available fields
- New DEs follow your structure and conventions
Keep it up to date
- Refresh/sync newly created Data Extensions
- Stay aligned as the org evolves
- Reduce “wrong table / wrong field” errors
Shared Data Extensions
- Sync shared DEs used across Business Units
- Leverage enterprise shared datasets
- Support consistent audience logic across teams
What this unlocks: when you ask for an audience, QAiry can propose rules that are feasible with the tables and fields you actually have.
Audience creation
QAiry 2.1 gives you two ways to build audiences. You can start from scratch, or ask QAiry to suggest segments that are realistic in your environment.
1) Build from scratch
Type your request in your own language (80+ languages supported). QAiry uses your data model and data view to map the right fields and logic.
Example requestGive me customers who:
- purchased in the last 30 days
- have a valid Email
- are opted-in
- exclude bounces and unsubscribes
2) Ask for suggestions (based on your Data Model and/or Data Views)
QAiry 2.1 proposes audience ideas that make sense for your environment, then you pick one and refine it.
Example requestSuggest 5 audience segments I can build
based on my current data model,
including loyalty and purchase behavior.
Field types preserved for reliable activation
QAiry keeps correct field types so downstream use cases (sending, personalization, SMS, validation) behave as expected. For example, Email Address and Phone fields behave differently than generic Text fields in Marketing Cloud Engagement.
Why this matters: if you build an audience that looks right but the field typing is off, the “activation” step (send relationships, personalization, SMS format checks) can become fragile. QAiry 2.1 is designed to keep the output consistent with your data model.
Want to know more?
See how QAiry helps SFMC teams build audiences faster — grounded in the data model you already have.
