The problem: the same lead campaign in every account, separately
An agency running 5–20 client Business Managers usually rebuilds the same lead-campaign structure by hand in every single account: the same instant form or the same site with a lead form, the same targeting, but a different Page and account ID each time. That's not just slow — it's a source of errors, like forgetting to swap the form on one of twenty accounts.
How this works in AdFleet
The Leads objective (OUTCOME_LEADS) supports both kinds of lead campaigns. Instant forms — the LEAD_GENERATION or QUALITY_LEAD optimization goals — resolve not by a hardcoded ID but by the name of an existing form on that specific account's Page, at launch time, so one preset expands correctly even when every client has their own Page with their own form. Website leads go through OFFSITE_CONVERSIONS with the pixel's LEAD event — the choice between a form and a site is made once, in the preset itself. As with any other launch, a daily budget summary per account currency shows before anything actually reaches Facebook, and crash-safe restart without duplicates works the same way described in article #6.
Special ad categories Meta supports: housing, jobs, financial
If your lead gen is real estate, hiring, or financial products and services (credit, insurance, banking), AdFleet genuinely supports these three Meta categories rather than working around them. In the preset, under "Campaign and optimization," there's a "Special ad categories (Meta)" block with three checkboxes — "Housing," "Employment," "Financial products and services (credit, insurance, banking)" — and a "Category countries" field (comma-separated codes). Leave it empty when the preset's targeting is a plain country list and AdFleet fills it in from there; for worldwide, a country group, or a region/city without its country named, you type the list yourself.
For any of the three categories, in every country, Meta limits targeting the same way: age fixed to 18–65+ with no narrowing, gender locked to "all" (no choosing men or women separately), no ZIP codes or other small areas, a radius of at least 15 miles / 25 km around a city or pin, no location exclusions, no behaviours or demographics in detailed targeting (interests only), no lookalike audiences — regular custom audiences, both included and excluded, are fine. AdFleet checks all of this itself when the preset is saved and again before the launch, before anything is created in Facebook. Which exact interests Meta approves inside a category is Meta's own list and can't be checked ahead of time: if Meta still refuses an ad over an interest, the launch card explains that refusal in your own language.
AdFleet doesn't offer the "Social Issues, Elections or Politics" category at all: Meta requires a separate advertiser authorization and a "Paid for by" disclaimer for it, which AdFleet doesn't manage. A preset or a hand-edited campaign JSON carrying that category never reaches Facebook — AdFleet refuses the launch itself, explaining which category and why it isn't supported.
What's still missing in leads
Leads submitted through a form or pixel don't sync into your CRM automatically — you keep pulling them exactly as you do today, from Meta's Leads Center or your own integration; AdFleet doesn't touch or replace that step.
Who this is for
Lead-gen agencies and buyer teams running the same lead campaign across many client accounts who want to launch it in bulk instead of rebuilding it by hand in every Ads Manager — including real estate, hiring and financial services, as long as the campaign fits Meta's limits for those categories (above). The one real exception is ads about social issues, elections or politics: AdFleet never runs those, under any circumstances.
Team starts at $149/mo for 5 seats, Solo at $29/mo for one buyer. Try it free for 3 days, no card — on one client account with a minimal budget.
On roles for a team launching these campaigns across different client accounts — article #19; on partner access to the accounts themselves — article #16. Guides — /help/first-launch, /help/presets.