An agency can use AdManage to move approved creative through a repeatable process: research, brief, asset approval, structured launch, verification and review. Marketing agency automation is useful when that process stays understandable in everyday production.
We looked at a defined 30-day sample of our own launch records. It contained 115,833 successful Meta and TikTok batches, recording 788,666 completed ad entries. About four in five batches contained fewer than ten completions.
That last finding is the most useful one. A workflow built only for the occasional giant upload misses the small, repeated launches that make up much of the work.
The operational case study
Our sample covers database calendar dates from 12 September through 11 October 2026. We selected successful Meta and TikTok batches and excluded known internal test company labels.
| Channel | Successful batches | Recorded ad completions | Batches with 100+ completions |
|---|---|---|---|
| Meta | 112,652 | 767,577 | 269 |
| TikTok | 3,181 | 21,089 | 8 |
| Combined | 115,833 | 788,666 | 277 |
This is a platform operations study relevant to agencies. The sample also includes other kinds of advertisers; it is not an agency-only cohort. We have not invented an unnamed agency, a before-and-after result or a customer testimonial.
The counts describe completed entries recorded within successful batches. They are not deduplicated unique ads or proof of incremental ad creation; a completion can include an already-existing ad. Failed and partial batches are excluded from this table, so it is not a platform success-rate calculation.
Most successful batches were small
| Recorded completions in a batch | Meta batches | TikTok batches |
|---|---|---|
| 1 | 23,102 | 793 |
| 2–9 | 68,491 | 1,809 |
| 10–49 | 19,711 | 546 |
| 50–99 | 1,079 | 25 |
| 100+ | 269 | 8 |
Taken together, 81.3% of successful batches contained fewer than ten recorded completions. Large batches are demonstrably possible, but they are a small share of jobs in this sample.
Our interpretation: an agency should evaluate automation against its recurring weekly work. A useful system makes a six-ad refresh consistent, then supports the larger launch when it arrives. For the wider brief-to-approval process, see our ad agency project management guide.
Batch size alone does not tell us why the user launched that group, how much work happened before it or whether automation saved time. Those questions need additional measurement.
A creative brief starts with an observable idea
In this public Emily Jackman and Fussy example, the video shows the creator holding the product with an on-screen offer. The captured headline frames it as a packing-list essential. That gives a team three separable elements to brief: a real-life use occasion, a creator demonstration and an offer. View the captured ad.
The useful action is to write a hypothesis for your own product. For example: will a travel use case make the benefit more concrete than a generic feature introduction? Keep the offer stable while comparing those openings, then review your own campaign results.
This example was captured from Meta. The creative belongs to its original advertiser and creator. Inclusion does not imply that either uses AdManage. The captured ad gives us no verified conversion or ROAS result.
How does marketing agency automation work for ad launches?
1. Save the observation and write the hypothesis
Use AdScan research to identify the visible hook, format, use occasion and offer. Record the source so someone else can understand the reference. Write one sentence explaining what your own test should teach you.
“Make five more ads like this” is difficult to evaluate. “Test a travel-use opening against a product-feature opening” produces a clearer brief.
2. Approve assets and permissions together
Before launch, keep the approved file, caption, landing page, creator identity and permitted usage together. With creator-led ads, the permission check belongs in the handoff to the buyer.
For comparison, this public Huel creator example uses a meal-prep situation and a busy-day message:
View the captured Huel example. A team borrowing the general use-case structure should make its own assets and obtain the permissions appropriate to its own launch.
3. Give every intended deployment a readable name
Use a consistent naming structure that lets the team identify the concept and execution. An illustrative name is TRAVEL_DEMO_CREATOR-A_HOOK-B_V02. Keep destination and tracking explicit in the launch table.
AdManage's Google Sheets workflow provides platform templates and field mapping. The goal is a handoff another buyer can inspect without decoding a folder of loosely named files.
4. Launch a batch, then verify the outputs
Import approved assets, select the intended destinations, review the expected outputs and submit. Reconcile completions with the plan, inspect warnings and identify any failed rows before retrying.
Our TikTok guide includes a real example where a regular TikTok ad used one caption despite the row containing five. That is why reading the result matters even when the batch succeeds.
5. Review performance at the concept level
Carry concept labels into your reporting. Compare results using a consistent objective, measurement window and attribution approach. Record what you learned and use it to choose the next brief.
Ad creation automation can make the execution more repeatable. Whether that improves commercial results is something your campaign data must demonstrate.
Measure the change you want to claim
If your agency wants a defensible case study, collect the baseline before changing its workflow.
| Question | Measure |
|---|---|
| Did the workflow reduce setup effort? | Active buyer minutes from approved handoff to submission |
| Did it reduce rework? | Rows requiring correction or retry, with reasons |
| Did it speed up usable delivery? | Time from handoff to the intended ads being approved and eligible |
| Did tests become easier to review? | Share of deployments with consistent concept labels and tracking |
| Did campaign performance improve? | A defined conversion or business metric, with comparable conditions |
Keep buyer effort separate from unattended processing. A job can run for thirty minutes while the buyer spends much less time actively managing it. Our current operational sample does not measure those active minutes, so we do not convert batch counts into “hours saved.”
Frequently asked questions
How do agencies automate ad creation with AdManage?
They can prepare approved media and copy in a structured launch workflow, map intended destinations, then submit and verify batches. Spreadsheet templates help make the handoff repeatable. Research, approvals and interpretation still need clear ownership.
Does this analysis prove an improvement in campaign performance?
No. It establishes recorded operating volume and batch-size distribution. It does not contain a controlled before-and-after comparison of conversions, CPA or ROAS.
Are the AdScan examples high-performing ads?
We do not have verified performance outcomes for them. They are real public creative examples used to explain visible choices and generate test hypotheses.
Should an agency aim for 100+ ads in every batch?
No. In this sample, small successful batches were much more common. Choose volume around the question you are testing, available delivery and your ability to review the results.
Put the process to work
Try the workflow with one approved creative refresh. Use the bulk launcher, keep the hypothesis attached to the assets and check the resulting ads. For choosing software, read the AdManage and AdEspresso comparison.
Data and source notes
Original read-only AdManage database analysis on 12 October 2026. Window: database dateAdded calendar boundaries from 12 September inclusive to 12 October exclusive. Channels: Meta and TikTok. Status: Success. Excluded known internal test company labels. All selected records had a populated final completion count. The 81.3% figure is 94,195 batches with one to nine completions divided by 115,833 selected batches, rounded to one decimal place.
Counts are batch-level operational observations and may include reuse or already-existing ads. They do not establish unique new ads, success rates across all attempts, customer account counts, agency-only behaviour, time savings or performance uplift. No customer identities or private account identifiers are disclosed.
AdScan examples were retrieved on 12 October 2026. Commentary is based on the visible media and captured copy. Research examples are separate from the anonymised launch dataset.
