Learn
How should assembly connect to Meta performance data?
How should assembly connect to Meta performance data?
Assembly should connect to Meta performance data with a human readout, not an API that spends. Export video columns. Paste hook rate and hold rate into the test log. Decide the next file; Produce it in eonik; There is no sanctioned “assembly engine ↔ Ads Manager autopilot.” eonik does not ingest your ad account to pause ads; Performance informs what to consider; It must not trigger spend.
The steps
01
Standardize Naming Conventions
You cannot track data programmatically if your ad names are messy. Enforce a strict naming convention: [Date]_[Hook-ID]_[Body-ID]_[CTA-ID].
02
Map the Winning Thresholds
Define the mathematical triggers. For example: "If [Hook-ID] achieves >35% Thumb-Stop over 5,000 impressions, it is flagged as a Winner."
03
Connect the Assembly Tool
Use an assembly platform that allows webhook or API integration. Configure it to listen for the "Winner" flag from your data dashboard.
04
Automate the Iteration
Set a rule that when a [Hook-ID] wins, the engine automatically generates 5 new variations combining that winning Hook with different Body-IDs, ready for the buyer to upload.
How should assembly connect to Meta performance data?
Assembly should connect to Meta performance data with a human readout, not an API that spends. Export video columns. Paste hook rate and hold rate into the test log. Decide the next file; Produce it in eonik; There is no sanctioned “assembly engine ↔ Ads Manager autopilot.” eonik does not ingest your ad account to pause ads; Performance informs what to consider; It must not trigger spend.
Read-only on purpose
Performance data informs what to consider. It must not trigger spend. If a connector can pause campaigns, you have a budget product. eonik is not that.
File-name discipline is how rows map to cuts. Without it, the pipe is theater.
Do this in order
Keep the pipe boring and auditable.
- 1. Customize Ads Manager columns: 3-second plays, ThruPlay or your hold proxy, impressions, frequency.
- 2. Weekly export or screenshot into the test log beside file names.
- 3. Write the next hypothesis in one line.
- 4. Make that cut in eonik. Upload yourself.
What not to automate
Webhooks that pause ads when hook rate moves. Warehouse perfection before shipping variants. Any write path into the ad account.
Boring paste-into-log is the sanctioned connection. Anything that spends is out of scope.
What usually breaks
- Webhooks that pause ads when hook rate moves.
- No file-name discipline so data cannot map to a cut.
- Waiting on a perfect warehouse before shipping variants.
When the readout is fatigue, hook rate, or velocity, the next move is consider what to make. Then make the cut in eonik and approve it. The loop is how to generate AI ads. It never touches spend.
“Almost any question can be answered, cheaply, quickly, and finally, by a test campaign. And that’s the way to answer them, not by arguments around a table.”
That principle still holds. The next on-brand cut is yours to approve.
Sources
Questions
How should assembly connect to Meta performance data?
With a human readout, not an API that spends. Customize Ads Manager columns for 3-second plays, ThruPlay or your hold proxy, impressions, and frequency. Weekly, paste those into the test log beside file names. Write the next hypothesis; Make that cut in eonik; Upload yourself; There is no sanctioned assembly-engine autopilot; Performance informs consideration; It must not trigger spend.
Should I API-connect eonik to Meta?
Not for spend. eonik is production. Bring numbers over in a log. You remain the operator; If a connector can pause campaigns, you have a budget product; eonik is not that; Read-only paste is boring on purpose; File names must match the log or the pipe cannot map a ratio to a cut; Do not wait on a perfect warehouse before shipping variants.
Where do 3-second plays come from?
Meta Ads Manager video columns. See Meta Help for the definition: plays of at least three seconds, or nearly full length if shorter, counted per impression, replay time excluded. ThruPlay is completion or at least 15 seconds. Hook rate and hold rate are operator divisions you compute after export; eonik does not pull those columns; You paste them; You still own the next file decision.
Free, no card · macOS 15+ · Apple silicon