Spark Ads and Partnership Ads authorisation across a roster

An ad authorisation is a dated permission and it expires while your flight is still running. The repair we are called in for most often is a ninety-day flight built on a TikTok ad authorisation the creator issued for thirty days: on day thirty-one the best-performing asset in the account stops delivering, and nobody on the media team can fix it, because the fix lives in an app on the creator's phone. This work builds the permission layer so it outlasts the media plan. How the permission is actually granted: Spark Ads run on a code the creator generates in their own account against a duration they choose. We specify that duration against the flight plus a buffer for extensions, collect the codes before the first euro is committed, and register them in Ads Manager as creative assets rather than leaving them in an email thread. On Instagram and Facebook there are two routes and they are not interchangeable. Account-level partnership ads permission persists until the creator revokes it, and is right for a retained creator. Per-post codes carry their own lifetime, and are right for a single collaboration. Brands that take the account-level route for a one-off end up holding rights the creator never meant to give, which is the version of this problem that ends in a takedown request rather than a dark ad. On YouTube we link the channel in Google Ads at the permission level the campaign needs: the right to run ads against their video, not access to their channel revenue, which creators refuse for good reason and which nobody needs. The register: You receive one sheet, per creator, per post: platform, asset code, grant date, expiry date, what the permission covers, who renews it and the date they are prompted. It is dull and it is the deliverable. A roster without an expiry calendar is a set of ads that will go dark on dates nobody has written down. Disclosure has to survive the paid version: An organic post carrying a partnership label becomes a different object when it runs as an advertisement, and the label has to come with it. Turkey's Advertising Board addressed placement directly in its 2021 influencer guide: the label belongs in the opening lines of the caption, visible before the text truncates, not appended below a wall of hashtags. We check the paid variant the way a buyer sees it, in feed, on a phone, not in the ads manager preview. Contract language we insist on: A usage window with an end date rather than in perpetuity. A named revocation route and how long the brand has to pull the ad. Whether the brand may edit the asset for the paid version, and if so what it may not touch: caption, audio, the creator's own voice-over. Whether dark posts are permitted at all. Who answers at nine in the evening when a post has to come down. What is not included: We do not buy the media. We do not produce or edit creative. We do not source creators or negotiate their fees. If your legal team wants an opinion on Turkish advertising law they should get one from a lawyer; we tell you what the guide says and where your setup does not match it. Who this is not for: Brands that want a creator post to run as an ad without the partnership label. Brands running one creator, once, where the register is not worth building. Teams who want a template to run themselves, because the value here sits in the calls about which permission route fits which relationship, and a template does not make those calls.