Build the audience old

To improve the in-store pickup experience, Luma wants to reach customers whose order is about to arrive in store — while they're still in the "waiting to collect" window. You'll build the audience that feeds that journey.

Create the audience. Follow Coworker's guidance through field discovery, definition building, size estimation and creation — respond yes/validate when required, and ignore any data warnings.

Create an audience for customers whose next order is being delivered to a store for pickup, with a delivery date in the next 2 days. Name this audience "[{{LASTNAME}}] - Engage - Delivery in 2 Days".

User approval is required before Coworker can run specific actions. When prompted, grant Coworker permission to proceed.

Expected outcome: a new audience created and named as specified.

Before you can activate or use the audience, it needs to be published. You have two options:

Via the UI: open the audience from the link Coworker provides, review its structure in the interface to confirm the definition is what you expected, then publish it.

Via Coworker: ask Coworker to publish it for you directly.

Publish the audience.

Expected outcome: the audience is published and ready for activation.

Luma doesn't want to waste paid social budget retargeting customers who are about to walk into a store anyway. Let's ask Coworker to suppress them from paid social until they've collected their order.

Map this audience to a Meta Ads suppression list, so these customers are excluded from paid social remarketing until their order is picked up.

Expected outcome: there is no Meta Ads connection in this sandbox, so Coworker attempts to create one — but the setup requires an interactive login it cannot complete on its own. Instead of failing silently, Coworker explains the limitation and proposes opening a Jira ticket to ask the Social team to configure the connection. Because you installed the lab plugin, Coworker can create that ticket for you. Approve it when prompted.

This is a good example of Coworker's extensibility. When it hits a capability it can't complete itself — here, an authentication step only a human can do — it doesn't dead-end. It routes the request into the systems your organization already uses (Jira) so the right team can pick it up.

You've built the audience and handed off the destination setup through Jira. Next, you'll build the journey that uses this audience.