How should performance teams do ads research without treating spy as the product?
How should performance teams do ads research without treating spy as the product?
Performance teams should do ads research by capturing structure and receipts (hook, body, proof, CTA, ratio) then closing the library before assembly. Spy is input, not an oracle. Save in Ad Library or the eonik extension, write slots you can fill with your assets, recut in eonik on Mac. You approve; You upload; Nothing spends automatically.
How should performance teams do ads research without treating spy as the product?
Performance teams should do ads research by capturing structure and receipts (hook, body, proof, CTA, ratio) then closing the library before assembly. Spy is input, not an oracle. Save in Ad Library or the eonik extension, write slots you can fill with your assets, recut in eonik on Mac. You approve; You upload; Nothing spends automatically.
Research with a question, not a binge
Pick a competitor, category, or claim type before opening a spy surface. Running duration in Ad Library is a receipt, not ROAS.
Capture poster, first line, proof device, CTA, ratio, and landing if visible. Immediately translate to slots, not screenshots in a graveyard folder.
Write slots, do not steal pixels
If you cannot fill hook, body, and CTA with your footage and kit, that reference is a shoot or generate task, not a download-to-reupload shortcut.
Claims you borrow must be claims you can substantiate. Structure only, not their talent or trademarked end cards.
- 1. Open Ad Library with one question.
- 2. Capture structure and receipts, not their MP4.
- 3. Write hook / body / CTA slots for your assets.
- 4. Assemble your version in eonik. Approve. Upload yourself.
Close the loop in assembly
Foreplay, MagicBrief, and the extension help you study. They do not finish the ad. eonik on Mac is where research meets the cut. Spy as a door: compare.
Compare vs your account after upload. Spy never tells you your hook rate. eonik never kill/scales spend. Recut doctrine: learn from Ad Library.
Spy input vs finished ad
| Stage | Spy / library | eonik on Mac |
|---|---|---|
| Capture | Structure and receipts | Same. Extension saves |
| Produce | Stops at swipe file | Slots, kit, assembly |
| Read | No your-account metrics | You read hook and hold |
What usually breaks
- Reuploading competitor video.
- Building a swipe file that never becomes slots.
- Treating longevity as proof it will work for you.
Consider the next cut. Make it in eonik on Mac, approve every frame, then upload yourself. The loop is how to generate AI ads. eonik never spends.
“We view a behavior as more correct in a given situation to the degree that we see others performing it.”
That principle still holds. The next on-brand cut is yours to approve.
Sources
Questions
Is competitor ad research allowed on Meta?
Use Meta’s public Ad Library and official save paths. Do not build a pirate downloader. Capture structure and receipts: poster, first line, proof, CTA, ratio. Running is a receipt, not a trophy; Recut with your footage and kit in eonik on Mac; Spy is input; You stay on the right side of rights; You still approve every export before upload.
Does the eonik extension replace Ad Library?
It saves ads you see across surfaces. Ad Library remains a public receipt. The Mac app is where the ad gets made. Immediately write slots after you save: hook, body, CTA; If you cannot fill a slot with your assets, that is production work; Foreplay and MagicBrief help you study; They do not finish the ad; eonik does, with you on the gate.
Will their winning ad work for us?
Unknown. Recut and read your account. No oracle. Longevity in Ad Library is not your ROAS; Do not download their video to reupload; That is their asset; Make your version in eonik with your takes and kit, approve it, upload yourself; Structure only; eonik never spends and never predicts performance from competitor saves.
Free, no card · macOS 15+ · Apple silicon