Create audiences for programs
In Adobe Marketo Optimizer, people lists define the audience for person journeys — either as dynamic filter-based lists that update automatically, or static lists with fixed membership. From the chat interface, the Audience Creation skill builds, adapts, and edits people lists through a guided conversation.
- Skills -
audience-creationandpeople-list-comparison - Invocation - Describe audience criteria directly, upload a Marketo Engage Smart List, or name an existing list to edit
- Reads from / writes to - Marketo Optimizer; reads Marketo Engage when adapting Smart Lists
Supported workflows workflows
Coworker supports three audience creation workflows and determines which one applies from your request. If your intent is ambiguous, it asks before proceeding.
Create a people list from scratch create-from-scratch
Before generating anything, Coworker confirms all four of the following. It asks for any that are missing — in a single message.
- Rules / criteria — A plain-language description of who belongs in the list.
- Name — What to call the list.
- Location — Which program the list should live in. Provide a program name and Coworker finds it; if there are multiple matches it asks you to pick.
- Type — Dynamic (filter-based, auto-updating) or static (fixed membership). This is required — Coworker will not guess; if you don’t specify, it asks.
Dynamic lists dynamic-lists
For dynamic lists, Coworker proactively suggests including personalization attributes to make targeting richer. These attributes are included by default — you opt out, not in:
Tell Coworker if you want to remove any of these before it proceeds.
Static lists static-lists
- Static, no criteria — The list is created empty, ready for you to add members manually.
- Static from criteria (a snapshot) — Coworker builds the matching set and copies those people in. Population is asynchronous — Coworker confirms the list was created but notes that it may take a few minutes for people to appear. It will not claim the list is ready immediately.
Review card review-card
Nothing is created until you approve it. After you describe your criteria, Coworker presents an interactive People List Creation Review card (for adaptations from Marketo Engage lists, the card is titled People List Conversion Review).
Each row in the card represents one condition:
Confidence levels:
- High confidence rows are matched cleanly and checked by default.
- Low confidence rows (approximate mappings or anything flagged) are shown with a notice indicator and are unchecked by default.
- Rows the system could not map show “No equivalent found” — these have no rule and remain unchecked.
A Conversion Summary tallies N High Confidence and N Low Confidence, with a hint: low-confidence rules are unchecked by default; check them to include, or describe the change you want in chat.
Card actions:
- Proceed — Creates the list using only the checked rules.
- Describe the changes you want in chat — Pre-fills the input with "I want to change: " so you can refine; Coworker regenerates and shows a fresh card, keeping rules you had already approved.
You can also type a follow-up at any point (for example, “also restrict to companies over 500 employees”) and Coworker regenerates the card.
Attribute mapping attribute-mapping
When you describe criteria, Coworker translates each condition into a real, known person-level attribute. Three outcomes can appear on the Review card:
- Matched (high confidence) — Your condition maps directly to an attribute (for example, “email is acme.com” maps to the
emailattribute). Checked by default. - Approximate (low confidence) — The closest available attribute differs in name or data model (for example, a Marketo Amount filter approximated as Lead Score). Shown with a note explaining the difference; unchecked by default.
- Not found — The condition couldn’t be mapped to any known attribute. Shown as “No equivalent found”; no rule is generated.
This is why a list you describe might come back with fewer rules than conditions you specified — unmatched conditions are surfaced explicitly rather than silently dropped. If important criteria land as “not found,” rephrase them using the attribute’s real name and Coworker re-tries.
Edit rules for an existing list edit-rules
When you ask to change rules on a list you already have, Coworker establishes which list and which edit mode:
- Add / append (default for “add rules”, “add more rules”) — new rules are merged with the existing ones.
- Replace (default for “replace rules”, “change rules to”) — new rules replace all existing rules on the list.
Coworker summarizes what will be applied and clearly states whether it’s adding or replacing, then asks you to confirm before it commits. After applying, it reports the total rule count and how many were added or replaced.
Audience overlap overlap
Ask Coworker to compare two people lists (for example, “Show me the overlap between ‘Q3 Webinar’ and ‘Enterprise Accounts’”) and it renders a People List Overlap card:
- A header badge showing the count: “{N} in common.”
- A stats row with each list’s total member count and the overlap as “X% of A · Y% of B.”
- A member table of the people in both lists, with a Name column and a second column you can steer — Email (default), Company, or Job Title depending on what you asked.
- Click any name to open that person in the workspace.
- If there is no overlap, the card says so clearly: “No members in common between these two lists.”
Limitations:
QA validation qa-validation
After creating or updating a list, Coworker offers: “Would you like me to verify the list is correctly configured?” If you accept, it re-fetches the list and reports the following checks: