Save, Export, and AI Generation
After rules are validated and estimated, use the header and preview actions to save the audience, save a draft, duplicate the definition, export a sample, or generate editable rules with AI.
Audience name
Use a name that explains the audience purpose without opening the rule definition.
Recommended format:
[Lifecycle or intent] - [Behavior] - [Window] - [Use case]
Examples:
- Cart Recovery - Add to Cart No Purchase - 30D - Email.
- Retention - High Churn Risk Active Users - 30D - Lifecycle.
- Acquisition - Pricing View No Signup - 7D - Paid Retargeting.
Audience status
The status badge communicates whether the current definition is ready. Observed and supported states include examples such as Draft, Unsaved changes, Needs fixes, Invalid, Valid, Estimated, Saved, Estimate stale, and Save failed.
Use the status as a prompt for the next action:
| Status | Meaning | Next action |
|---|---|---|
| Draft | Audience is not finalized | Add rules and validate |
| Unsaved changes | The builder changed after the last save | Validate, estimate, and save again |
| Needs fixes or Invalid | Validation found a blocking issue | Fix conditions shown in Audience Summary |
| Valid | Rules passed validation | Estimate audience size |
| Estimated | Audience size is available | Preview and save |
| Estimate stale | Rules or dates changed after estimate | Run Estimate again |
| Saved | Audience has been saved | Use it for downstream review or activation |
| Save failed | Save request did not complete | Check validation, connection, and retry |
Save actions
Use Save Audience when the audience is ready for reuse.
Use Save as draft when the definition should be preserved but is not ready for activation or formal reporting.
Use Duplicate locally when you need a copy of the current definition for a variant. Rename the duplicate before saving so teams can distinguish it from the source audience.
More actions
The More actions menu includes utility actions.
| Action | Use it when | Check before using |
|---|---|---|
| View insights | You want to inspect audience performance or downstream analytics | Audience has been estimated or saved |
| Reset audience | You need to clear the current builder state | Current rules are no longer needed or have been copied elsewhere |
| Duplicate locally | You need a local copy for a new variant | The duplicate will be renamed and reviewed |
Export Sample (CSV)
Use Export Sample (CSV) after preview rows are loaded and attributes are selected. The export is useful for QA, stakeholder review, and operational handoff.
Before exporting:
- Confirm the audience is estimated.
- Confirm preview users match the intended criteria.
- Confirm selected attributes are approved for export.
- Remove unnecessary PII.
- Confirm the CSV sample is not used as a permanent activation list unless that is the approved workflow.
Generate with AI
Use Generate with AI to turn a natural-language audience description into editable builder rules.
The prompt should describe:
- Inclusion behavior.
- Exclusion behavior.
- Time window.
- Important source fields when known.
- Intended use case.
Good prompt:
Users who added to cart in the last 30 days but did not purchase in the last 30 days. Use this for cart recovery review.
After selecting Generate and apply, review every generated rule before saving.
AI review checklist
- The generated source entity is correct.
- The generated attribute is correct.
- Operators match the intended logic.
- Values match the source data spelling.
- Time windows match the prompt.
- Exclusions are represented as exclusion logic, not as additional inclusions.
- The audience is validated and estimated after applying AI-generated rules.
AI-generated audience rules are editable drafts. Do not save, export, or activate them until a user reviews the logic, validates the audience, estimates size, and checks preview users.
Final QA checklist before saving
- Audience name is clear and specific.
- Status is not Needs fixes, Invalid, Estimate stale, or Save failed.
- Validation has no blocking errors.
- Estimate is current.
- Preview users match the business question.
- Audience Summary metrics are reasonable.
- Preview attributes are appropriate and approved.
- Exclusions and suppressions are present when needed.
- The audience owner knows whether this is a draft, saved audience, export, or activation input.
Common issues
| Issue | Cause | Fix |
|---|---|---|
| Save Audience should not be used yet | Validation, estimate, or preview is incomplete | Save as draft or finish QA first |
| Duplicate audience is confusing | Duplicate kept the same name | Rename the copy immediately |
| Export is unavailable | Preview rows or attributes are missing | Select attributes and run Estimate |
| AI output uses the wrong field | Prompt did not name the source or field clearly | Edit the generated rule or regenerate with a more specific prompt |
| Reset removed work unexpectedly | Current definition was not saved or copied | Use duplicate or copy JSON before resetting important work |