Editing → Publishing: the rules, and what's outstanding

We've built something that takes the ⭐ Final Edited Link off a Fibery ticket, pulls the video out of Shade, and loads it straight into the Meta ads library — no manual downloading and re-uploading. It runs the moment a ticket is marked Edit Complete.

The catch: the robot publishes exactly what the link points to. If the link is missing, points to the wrong video, or points to a folder with several videos, it can't know which one you meant. So the link being right is now the single most important thing.

1. One ticket = one video.The ⭐ Final Edited Link should open to a single final video. If a creative has several hooks, give each hook its own ticket with its own link — don't put them all behind one link.
2. Link the full ad, not just the hook.Asel flagged this before — a link came through as only the hook. The link must be the complete, ready-to-run ad.
3. Always update the link on the ticket.The recurring miss. When you re-export or make a change, paste the new Shade link onto the Fibery ticket. If the link isn't updated, we publish the old version — or nothing.
4. The linked folder holds only the final.If your link opens a folder, that folder should contain only the publishable final — no drafts, alternate cuts, or captions-off copies sitting next to it.
5. Follow the original script/video.When the script and what the speaker says differ, follow the original video. (Per Asel, 10 Mar.)

Out of 45 "Edit Complete" ad tickets. The 36 clean ones we can start auto-publishing right away — the 9 below need a quick fix first.

Three tickets, all about the link on the ticket. For each: open the creative's folder in Shade → find the final video → right-click → Share → "Downloading" link → copy → paste into the ticket's ⭐ Final Edited Link field.

What these are

Each of these tickets bundles one ad in 3 hook versions (A / B / C) behind a single link — they were never split into separate creatives. Nothing in Fibery records which hook is which; only the Shade filename does (e.g. …ITR_UGC HOOK4B…). That's why the robot can't pick — and why each hook needs to become its own ticket going forward.

How to clean them up

1. Asel decides which hooks runFor each batch, which of A / B / C go live? (Often all three — they're a hook test.) For 564 / 565, also confirm whether to test square, portrait, or both.
2. One creative + one ticket per chosen hook — RaedenMake a separate Fibery creative and editing ticket for each chosen hook, named with the hook so it's traceable, e.g. …NoDegreeSuccess_HOOK4B. Point its ⭐ Final Edited Link at that single video. Then it flows like any other ad.
3. Link the two orphans (564, 565)These two aren't connected to a creative record at all — link them as part of the split above so they don't fall through the cracks.

Tiny note, no action: 525's file is labelled W14 vs the ticket's W15, and 485's filename is slightly cut short — same correct videos, cosmetic only.

Keep posting deliveries in this exact shape — it's what works:

Every time you finish an ad, before you flip a ticket to Edit Complete, run this quick check:

1. Open your own Shade link.Click it like the team would. Does it open the right ad — the full ad, not just the hook?
2. One link, one final video.The link should land on a single finished video. Not a folder of drafts, not several hooks behind one link. One hook each? One ticket each.
3. Paste it onto the Fibery ticket.Put that exact link in the ⭐ Final Edited Link field. If you re-export later, re-paste the new link. This is the step that's been missed most — it's the one that matters most.

You don't touch Meta at all. Once a link is clean and the ticket is Edit Complete, we auto-publish it to the Meta ads library and make sure nothing goes up twice. The 36 clean tickets are ready to go now.

The whole job: Raeden's 3 quick fixes (~12 min), then a short call with Asel to split the 6 hook batches — after that, keep the 20-second check before every Edit Complete. That's it.