Creating Playbooks

Set Up the Playbook

The first page controls who can use the playbook, how it launches, and which choices workspaces can make during opt-in. Use Expand all to review every section, or open one section at a time.

Basic Information

• Playbook Name is what workspace users see and search for. Name the campaign outcome or season, not your internal project code.
• Description should tell a workspace what the campaign is for and when to use it. One or two sentences is enough.
• Primary Language guides AI copy generation and Meta language targeting. A workspace's language settings in Paid Social Ads > Configuration take priority when that workspace has its own override.

Collections

Add the playbook to one or more Playbook Collections so workspaces can browse the Shop by campaign type, season, product, or another useful theme. Collections organize the Shop. They do not grant access by themselves.

Who Has Access?

Choose the audience model that matches how your network changes:

• All Workspaces lets every workspace in the Hub use the playbook.
• Specific Workspaces saves a fixed list. Use it for one-off exceptions or a campaign meant for a few named locations. The list does not update on its own.
• Workspace Groups keeps access tied to group membership. A workspace added to a selected group automatically gains access. A workspace removed from every selected group loses access to future opt-ins, while campaigns already running finish normally.

With Workspace Groups, the current resolved audience appears below the group list. Use Also include these workspaces for individual exceptions that should retain access regardless of group membership.

How Will You Launch The Playbook?

• Workspace Opt-Ins lets each workspace review the playbook and provide any permitted budget, schedule, media, or question responses before deployment.
• Deploy Immediately starts deployment to eligible workspaces when the playbook is activated. Use it only when the Hub has fully configured every required input.

Deploy Immediately is unavailable when the playbook requires workspace-provided media, a workspace-selected schedule, or another opt-in-only choice.

Playbook Budget

• Lifetime Budget is one total amount for the full scheduled run. A start and end date are required.
• Daily Budget is the average amount to spend per day.
• Total Playbook Budget is the budget for the whole playbook. If the playbook has multiple campaigns, you allocate that total after creating the campaigns.
• Allow workspaces to set their own budget lets workspace users replace the default during opt-in. Turn it off when every location should launch with the Hub-defined amount.

When workspace budget control is enabled, set a minimum that still gives every campaign and ad set enough budget to deploy.

What Kind Of Playbook?

• One Time creates a single campaign run with the schedule you define. Use it for launches, holidays, and other fixed events.
• Recurring Evergreen Process lets a workspace opt in again after a run finishes. Use it for repeatable campaigns such as trial offers, hiring, testimonials, or monthly promotions.

Evergreen playbooks let workspaces choose the schedule and budget for each run. Define a duration that is long enough for the campaign to learn and deliver.

Schedule Configuration

A lifetime budget requires both Start Date and End Date because the total budget must have a defined delivery window. A daily budget can use an optional start date and can continue without an end date.

For workspace opt-in playbooks, you can let each workspace choose its own dates. When you do, set duration constraints so local schedules stay within the campaign design.

Offer Variants

Add variants when workspaces should choose between a small set of approved options, such as price point, audience, or offer length. Flamel generates the valid combinations from the options you add.

Skip variants when every workspace should run the same offer. Fewer, clearer choices make opt-in faster and reduce review work.

Creative / Media Configuration

Choose where each workspace's ad media comes from:

• Hub Provides Media uses the images and videos you add to the playbook.
• Workspaces Upload Media asks each workspace to provide local creative during opt-in.
• Use Existing Posts lets each workspace choose one of its organic posts to boost.

Then choose the approval flow. This gate is independent of creative source: it works with Hub Provides Media, Workspaces Upload Media, and Use Existing Posts. No, Workspace Directly Deploys sends completed opt-ins straight to deployment. Yes, Hub Approval Process holds each opt-in for Hub review so you can approve it or request changes. See Playbook Review Required for the reviewer and workspace workflow.

Opt-In Questions

Add questions only when the answer is needed to tailor or approve the campaign. Questions support rich text and must be answered during opt-in.

Good questions ask for a concrete deployment input, such as the promoted service, local offer details, or a landing page. Avoid asking for information already stored in Workspace Variables or Ad Configuration.

Notification Preferences

Opt-in emails are off by default. Turn on Email hub admins when a workspace opts in when someone needs to review launches or monitor adoption. You can notify every Hub admin or choose specific admins. See Review Email Reminders for recipient rules and the approval reminder cadence.

Advanced options includes a setting to silence all playbook emails. Use that only for testing or a deliberately quiet workflow.

Set The Campaign Structure

Choose the objective, campaign naming pattern, any special ad categories, and whether Meta should optimize budget at the campaign or ad set level.

Build Ad Sets and Ads

Set:

• the audience type
• where leads or traffic should go
• which page and account the ads should use
• the creative type
• the ads themselves

Review Before Publishing

Check the budget, schedule, audience choice, and ad copy one more time, then click Create.