Partnership ad code or account-level permission: which to ask for
Meta partnership ads come in two permission types. How content-level codes and account-level access differ, and what to log when the clips are AI-made.
Ask for a partnership ad code when you want to promote one specific post, story or reel. Ask for account-level permission when you plan to run many ads from the creator's handle, including ads that start without an existing post. Meta's own page names these two types as content-level and account-level (read 2026-10-03).
For AI-made clips the choice changes how much per-clip bookkeeping you need, because a code ties permission to one piece of content while account-level access does not.
How do the two permission types differ?
Meta's help page says branded content ads are now called partnership ads, and that advertisers need permission from the partner whose handle the ad will include. Partners can revoke permission at any time. Two accounts owned by the same business, with an employee who has ads access to both, need no permission at all.
| Question | Content-level | Account-level |
|---|---|---|
| Scope | One post, story or reel | The partner's handle across ads |
| How it is granted | Allow brand partner to boost toggle with the advertiser tagged in the paid partnership label, or the partnership ad code | Accepted in Partnership Ads Hub, the Instagram app or the Facebook app |
| Needs existing content | Yes | No: partnership ads, other ad types and marketing messages can start without it |
| Content tagged with | Paid partnership label or a code shared by the partner | Paid partnership label, an @mention, a people tag, a product tag or a Collab |
| Audience option | Not listed | Include or exclude the partner's custom audience |
Which one fits a batch of AI clips?
If you produce one hero clip per creator, a code is the lighter ask: the creator shares a code for that reel and nothing else. If you generate many variants and want to test them from the creator's handle, account-level access is the realistic fit, because each new variant would otherwise need its own code.
That convenience has a cost. Account-level access lets you create ads from the partner's handle, so the creator is trusting you with their face and name across everything you run. Agree in writing which clips they have seen. Meta's page also notes the content-level route lets you hide comments, and that edits for the ad leave the original post unchanged, so a variant never rewrites what the creator published.
Where does Sume fit?
Sume produces and edits the files. It does not call Meta's ad tools, create partnership ad codes or set the paid partnership label. Those steps happen in Meta's products or in your own code. Sume's job records give you the production trail, and the asset library keeps the source files that edits run on.
One practical detail: Sume's edit endpoints such as video trim and inspect take only workspace media URLs on media.sume.com. If the creator sends footage as an Instagram or TikTok public URL, import it first with the media-imports route, then run your edit on the imported copy.
What should you log per permission type?
Keep a short sheet per creator and per ad. The columns differ a little.
- Content-level: the post or reel URL, the date the code was shared or the toggle turned on, and the date it was last confirmed active.
- Account-level: the date the creator accepted, the surface they accepted in, and the list of clips they approved.
- Both: the Sume job id and artifact URL of the final file, plus any earlier step such as a trim.
- Both: whether the clip was filmed by the creator or generated, since that feeds the involvement question.
What happens if the creator revokes?
Meta says partners can revoke permission at any time. Plan for it: do not assume an ad that was running yesterday can be duplicated today. Keep your own copy of the approved file, the approval record and the permission date, so you know what you may no longer run.
Sume cannot tell you the current state of a Meta permission, so the check belongs in your ad workflow. A weekly review of active partnership ads against your sheet is enough for most small programs.
For label fields on your own publishing code, see the Instagram API fields for paid partnership. That post covers sponsor ids; this one is only about which permission to request.
What should the ask to the creator say?
Creators are more likely to agree when the request is specific. For a code, name the post and the dates you plan to run. For account-level access, say which surface you will ask them to accept in, whether Partnership Ads Hub, the Instagram app or the Facebook app, and which kinds of ads you expect to run from their handle.
Be explicit about AI. If any clip in the program is generated rather than filmed, tell the creator before they grant anything, and show them a draft. A permission given without knowing a face or voice was synthetic is the kind that gets revoked, and Meta lets partners do that whenever they like.
Keep the thread. A short written exchange that names the permission type, the date and the clips shown is enough for most programs, and it costs nothing to save next to the Sume job records.
Sources
Related posts
More in Use cases
- Personalized gift video with a name: Ideogram edit, cues and cost
Put a customer's name on a gift card still with an Ideogram 4.5 edit, animate it, and burn exact caption cues for the name. The per-recipient cost on Sume.
- Vet clinic Halloween clip: chocolate, xylitol and costume checks
The ASPCA lists chocolate, xylitol candy and ill-fitting costumes as Halloween pet risks. Turn them into caption cards for a clinic reel from $0.22.
- Pet Halloween costume portraits: 30 photos, 4 takes each, cost on Sume
Thirty pet photos with four costume takes each, one n=4 call per pet, cost $3.90 on Seedream 4.0 via Sume, which keeps the photo's shape with aspect_ratio auto.
- Pick the hook frame of an ad with video inspect stills
Sume video inspect returns 8 mid-bin stills by default, or 1-24 at timestamps you choose, plus optional transcription. Find the best opening frame fast.
Written by Sume