Ad Configuration
Per-workspace targeting profile: audience types, default targeting, lead forms, and CTAs.
Who does what
Hub admins create audience types and the network defaults. Workspaces customize within those limits. Playbooks pull from this configuration at deploy time.
How it works
Every workspace has two layers of targeting:
- Default tab is the baseline targeting (demographics, locations, call to action) that applies unless something overrides it.
- Audience type tabs are named presets (
Database,Mass,Lookalike) that override the default for specific use cases.
When a playbook ad set targets Database, Flamel pulls that workspace's Database configuration at deploy.
Set up your side
You create the audience types and own the network-wide strategy. Workspaces customize within the boundaries you set.
Create your audience types and Hub defaults
Build the named presets every workspace will share (Database, Mass, Lookalike) and set the baseline targeting that applies network-wide. See Hub setup for the full walkthrough.
Build the per-workspace Ad Configuration row
For each workspace, create its row in the Ad Configuration table so the playbook engine has a profile to pull from at deploy.
Add or remove studio locations as the network changes
When a franchisee joins, add their location row. When one closes, remove it so campaigns stop deploying for that workspace.
Check the field reference when you need detail
The Walkthrough covers every field in the Ad Configuration UI.
You customize within the audience types your Hub created. You cannot create or delete audience types, but you control your local targeting, audiences, and lead capture.
Set your local targeting radius
Open the Workspace guide and set how far around your location your ads should reach.
Add your custom audiences
Go to Ad Configuration, open Custom Audiences, then click Sync to pull your CRM-backed audiences in from Meta.
Set your local website URL and lead form
On the Default tab, fill in your Call to Action URL and your Lead Capture form so leads route to your location.
Check the field reference when you need detail
The Walkthrough covers every field in the Ad Configuration UI.
Who can change what
This is the permission split between Hub admins and workspace owners.
| Action | Hub | Workspace |
|---|---|---|
| Create or delete audience types | Yes | No |
| Edit Hub-locked targeting | Yes | No |
| Adjust targeting radius | Yes | Yes |
| Add custom audiences | Yes | Yes |
| Set CTA URL and lead form | Yes | Yes |
| Sync audiences and forms from Meta | Yes | Yes |
Granting a workspace more control
To give a workspace owner editing rights, go to Organization, then Permissions, and enable paid_ads_management on their role. Super Admins get it automatically.
Common audience types
These are the presets most brands set up. Two or three covers most strategies. More than five usually means the strategy is over-engineered.
| Name | Strategy |
|---|---|
Database | Custom audience from a customer list (CRM upload) |
Mass | Broad demographics, no audience filter |
Lookalike | 1 to 3 percent lookalike from a customer list |
Retargeting | Custom audience from pixel data |
VIP | Top spenders from your CRM |
Deleting an audience type is network-wide
An audience type is Hub-owned. Deleting it removes it from every workspace and breaks any playbook that references it. Before you delete one, update the referencing playbooks to use a different type.
Where it plugs in
Once configured, the Ad Configuration feeds three surfaces.
| Surface | What it consumes |
|---|---|
| Playbooks | Each ad set picks an audience type; deploy pulls that workspace's matching config |
| Command Center | Filter performance by audience type |
| Analytics | Performance is attributed per audience type |
Common questions
Audience types
An audience type is a named preset in Flamel (like Database or Mass) that bundles a targeting strategy. A custom audience is the actual list of people in Meta (website visitors, CRM uploads, lookalikes) that an audience type might use.
Workspaces cannot create their own audience types. They are Hub-only, which keeps targeting consistent across the network.
Targeting and permissions
With the paid_ads_management permission, a workspace can customize its targeting radius, custom audiences, local interests, website URL, and lead form. It cannot change audience types or Hub-locked detailed targeting.
The location status dot
A green dot means location targeting is configured. A red dot means it is missing, and campaigns will not deploy for that workspace until it is fixed.
Syncing audiences and lead forms
To sync audiences, open an audience type tab, go to Custom Audiences, then click Sync Audiences. This pulls the latest from the workspace's connected Meta ad account.
To sync lead forms, go to Lead Capture and click Sync Forms. Forms must be published (not draft) in Meta and copied to the workspace's Page.
When Meta audiences do not appear
If an audience does not show up, check three things: the custom audience may still be processing in Meta, the workspace may not be on the right ad account (check Connected Accounts), or the audience may be archived in Meta.
CTA and lead forms
CTA values fall back in order: the audience-type CTA, then the Default tab CTA, then the Hub default. Set the CTA once on the Default tab and audience types inherit it unless you override them.
For lead forms to appear in a playbook, the playbook objective must be Leads and the audience type's Lead Capture must have a form selected. If a workspace lacks a form, the playbook cannot deploy for that workspace.
You cannot reuse the same form across workspaces, because leads route to the Page the form lives on. Copy the form to each workspace's Page in Meta, then sync it into Flamel.
Adding and removing locations
When a new franchisee joins, run Onboard a new workspace. The Ad Configuration step covers adding the table row.
When a location closes, remove its studio location row from the Ad Configuration table and then run Close a workspace for the full cleanup.
Advantage+
For conversion campaigns where Meta has room to optimize, enabling Meta's Advantage+ audience is usually worth it. Skip it for compliance-restricted categories (housing, credit, employment) and for small or tightly defined audiences you do not want diluted.