- From
- Media library
- To
- New ad set
- Editor
- Lena
- Copy
- From brief
Uploads in. Ad sets live. Nothing live touched.
Every uploaded concept becomes a native copy of the ad set that already performs, with ads built from the brief and every setting checked against the source. About 35 seconds each, one after another.
- Snapshot 470
- First creative
- Native copy
- 13/13 match
- 3 ads paused
- Ads on
- Ad set on
- 470 → 470
Twenty concepts uploaded. One buyer to launch them.
Every concept is the same ritual in Ads Manager: duplicate the ad set that works, rename it, attach videos one by one, paste the brief, re-check what Meta quietly reset. The queue waits for the buyer, and the afternoon is gone.
- Duplicate the working ad setplacements, Explore, lifecycle1:00auto
- Rename by the team's patterndate · product · pod · funnel · batch1:00auto
- Attach V01, V02, V03found in the media library by name4:00auto
- Paste texts from the brieftext, headline, description, link3:00auto
- Check, schedule, switch on13 settings against the source2:00auto
By hand: rough minutes per concept for a buyer who knows the account. Adrayo: 20 × 37 s, the median of the last 149 real launches.
Nothing to retype. The uploads are the queue.
Every file named “concept - V01, V02, V03” becomes one task: one ad set, one ad per version. Funnel, holiday, product and editor are read from the name.
Upload to the ad account as you always do. Adrayo reads the media library and groups versions by name. Meta's own auto-crops and unnamed files are ignored.
One real ad account on 18.11. Names changed.
- From
- Media library
- To
- New ad set
- Editor
- Anton
- Holiday
- BF · 27/11
The screens your team works in every day.
Six screens of a live ad account: the launcher, activity, reports, a read-only Ads Manager, settings and angles. Pick one, or let them run.
Real screens of a live account. Names changed, creatives blurred.
Everything a launch needs on one screen.


Every task finds its campaign by its name.
A real Launch map of one ad account, names changed: products first, then rules in the order you set. The first rule that matches wins; the last one is the default. Type a task name below and watch which rule takes it.
One launch, second by second. Straight from the log.
Before anything is written, every active ad in the account is counted. The number is checked again at the end.
Sent before the copy: if Meta refuses it, the launch stops here and nothing is created.
POST adcreatives · okTexts from the brief, link and button from the source ad set, read fresh at this launch.
Meta's own duplicate, in the campaign the Launch map chose. Paused from the first millisecond.
POST /copies · PAUSEDThe creatives are built in the time Meta needs anyway.
About twenty seconds on Meta's side, the same for everyone. Then the copy is compared with the source.
12 / 12 settings identicalAn ad can only go into an ad set the platform created itself. There is no other path in the code.
All three, and only now.
The name goes in the same edit, so there is no extra wait.
The second count equals the first. A missing ad would turn the task red and name it.
lost: none
The only action on this screen is Duplicate → Launch.
It cannot touch a live ad. Not “won't”. Cannot.
Your Ads Manager is mirrored for context. Switches, budgets and edits of live items do not exist in this tool.
- One write patha single function sends writes; it creates copies, creatives and adsLOCKED
- Only what it maderename, switch on, add ads: only to its own objectsLOCKED
- Paused until checkedcopy and ads are born paused; then ads, then the ad setLOCKED
- Counted before and afteractive ads before and after every launchLOCKED
- Launched once, never twicea lost answer from Meta is looked up, not retriedLOCKED
- Writing to Metaoff for every ad account until an owner switches it onOWNER
Rules in code, checked by tests on every release.
Every change in the account, with a name on it.
Who changed what and when: the platform, the uploads, the team in Ads Manager, Meta's own automation. And what the platform launched, per ad account.
Counted from the platform's own records, 06–19.11. Account names changed.

Where a bulk launcher spends your attention.
As published on their sites, 11.2026.
Built for teams that launch every day.
Adrayo was built inside Goverlo Media, a performance agency, and launches on its own Meta ad accounts every day. Every rule on this page exists because a real launch needed it.
BoardingAdrayo is for you if
Not boardingIt is not for you if
What teams ask before the first launch.
Anything else goes into the walkthrough: fifteen minutes, on your own ad account.
What is a bulk launcher for Meta ads?
Can Adrayo change or pause my running ads?
Where do the tasks come from if we don't use Slack?
What access does Adrayo need?
What if Meta refuses a launch?
How much does it cost?
Where is our data, and can we delete it?
Your queue, launched by the time the coffee is done.
Fifteen minutes: your ad account in read mode, your real queue, one launch if you say so. Then you decide.