Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

TikTok Marketing › Troubleshooting

TikTok Spark Ads Code Not Working

Why a TikTok Spark Ads authorisation code fails or a Spark Ad stops and how to fix it: expiry, private posts, wrong posts, uncleared sounds and account links.
Troubleshootingintermediate7 min readUpdated

First, read the error and the post's status in the creator account

Write down exactly what Ads Manager says when the code is entered, or what the ad's status shows if it stopped mid-flight, because the wording separates a code problem from a post problem from a review problem. Then ask the creator, or open the brand's own account, and check the post itself: is it still published, still public, and is it the same video you agreed to promote, not a re-upload with a new caption? Finally, find the code's details in your own records: when it was generated, for which post, and the authorisation period the creator chose.

If the ad was never accepted, the cause sits in the code or the post at the time it was entered: expiry, revocation, the wrong post, authorisation not switched on, or a post that was not public. If the ad ran and then stopped while budget and schedule remain, the cause happened later: the period ended, the creator revoked it, or the post changed status. If the ad was accepted and then rejected, review found a problem, and the sound is the usual suspect. If the post belongs to your own brand and you are using codes at all, the link is the first thing to check. The Spark Ads guide holds the authorisation flow and what carries over from a post; this page does not repeat them.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
Code refused, or a running ad stops at a dateGeneration date and period in your records; whether the creator revoked itCode expired or revoked by the creatorAsk for a new code with a period covering the flight
Code refused, or an ad stops without warningPost status in the creator's account: public, private, deleted, re-postedPost made private, deleted or replaced after the codeRestore the post to public, or authorise the replacement
Code refused from the first attemptAd authorisation setting in the creator tools; which post generated the codeAuthorisation off, or the code made for a different postSwitch authorisation on and generate the code from the agreed post
Code accepted, ad rejected in reviewRejection reason; the post's sound and its commercial eligibilitySound not cleared for commercial useRe-post with an eligible sound or original audio and authorise that
Own brand posts missing, team asks for codesWhether the brand account is linked to Ads ManagerOwn-account post expected through a code instead of a linked accountLink the account; select its posts directly

Fix, verify and prevent each cause

A period that ran out, or permission withdrawn

A creator chooses an authorisation period when generating a code, and can revoke it before the end. Delivery stops at expiry or revocation whatever the budget or schedule says, as the Spark Ads guide documents. A code generated weeks before launch may already be close to its end when the campaign starts.

Fix: ask the creator for a new code from the same post, with a period that covers the remaining flight, and replace the ad's creative with it; if they revoked deliberately, resolve the reason with them before asking again.

Verify: the new code is accepted and delivery resumes the same day.

Prevent: record each code's generation date and period beside the campaign plan, and request renewals before expiry, not after delivery stops.

A post that is no longer what it was

The authorisation attaches to one post, and the post must stay public for the whole period. A creator who sets it to private, deletes it, or deletes and re-posts it with a fixed caption ends delivery or invalidates the code, because the re-post is a different post.

Fix: ask the creator to restore the original post to public if possible; if they replaced it, request a code from the new post and rebuild the ad around it, as the Spark Ads guide notes that each new video needs its own code.

Verify: the post is visible to a logged-out viewer and the ad shows as delivering again.

Prevent: put "post stays public and unchanged for the period" into the creator agreement, and ask for edits before the code is generated.

A code that was never valid for this post

Two set-up slips account for most first-attempt refusals. The creator has not switched on ad authorisation in their creator tools, so no valid code exists; or the code was generated from a different post than the one agreed, often a near-identical take.

Fix: ask the creator to confirm the setting and to generate the code from the agreed post, sending the post's link alongside it so you can check the match, following the flow in the Spark Ads guide.

Verify: Ads Manager accepts the code and previews the expected video, caption and handle.

Prevent: send creators a short checklist with every request: authorisation on, the agreed post, the period, the link with the code.

A sound that review will not accept

A Spark Ad carries the post's sound, and ad review checks whether that sound may be used commercially. A post built on a popular track that is not cleared can be accepted as a code and then rejected as an ad. The Spark Ads guide records this as a carry-over consequence.

Fix: ask the creator to publish a version with original audio or a sound from the commercial library, then authorise that post.

Verify: the new ad passes review and starts delivering.

Prevent: brief creators on sound eligibility before they film, so the posts you plan to promote can be promoted; the campaign structure guide covers the ad group around the post once it is cleared.

Own posts routed the hard way

For a brand's own account, the documented route is to link the account to Ads Manager, after which its public posts can be selected directly. Teams that skipped the link end up asking colleagues for codes post by post, and every code brings its own expiry.

Fix: link the brand account through Business Center or the identity settings, with the account owner granting the link in the app, as the Spark Ads guide describes.

Verify: the brand's public posts appear in the Spark post selection without a code.

Prevent: link every brand account when it is created, and keep codes for posts the business does not own.

Prevention: code expiry in the campaign plan

Spark Ad failures are scheduling failures more often than technical ones. Treat each code as a dated asset: record the post link, the creator, the generation date, the authorisation period and the planned flight in the campaign plan, and set a reminder before expiry. Ask creators to keep posts public and unchanged for the period, to use eligible sounds, and to send the post link with every code. Link every brand account so own posts never need codes. When a Spark Ad starts, note its reach (Reach), tap rate (CTR) and cost per thousand impressions (CPM) for the first days, so that a later stop is noticed as a stop rather than a decline. The TikTok Ads hub lists Spark problems among the common ad problems, and the TikTok Ads troubleshooting hub covers ad groups that are approved but still do not spend.

Illustrative example — not a real result

A coffee brand's creator campaign that stopped in week three

A coffee brand runs a four-week campaign promoting 6 creator posts as Spark Ads. On day 17, delivery on 4 of the 6 ads stops and the budget of £250 a day concentrates on the one ad still running. The campaign plan shows that those 4 creators generated their codes 13 days before launch with 30-day periods, so all 4 expired mid-flight. A fifth creator had re-posted their video on day 9 with a corrected caption, which had already ended that ad's delivery, but the team had not noticed because the remaining ads absorbed the budget. The brand requests new codes from the 4 original posts with periods covering the rest of the flight, and a code from the re-posted video. Delivery resumes on day 19, and the plan now has a column for code expiry with a reminder set a week before each date.

Common mistakes

Requesting codes long before launch. Letting a creator re-post to fix a caption without asking for a new code. Promoting posts built on uncleared sounds. Using codes for the brand's own posts. Reading a stopped Spark Ad as creative fatigue.

Frequently asked questions

The creator sent a fresh code but Ads Manager still refuses it. What next?

Ask the creator to confirm three things from their app: that ad authorisation is switched on in their creator tools, that the code was generated from the exact post you agreed, and that the post is public. A code made from a different post, or from a post later set to private, fails however new it is. Then paste the code again without extra spaces or characters.

Why did a Spark Ad stop delivering when the budget and schedule still run?

Delivery of a creator post ends when the authorisation period runs out or the creator revokes it, and also when the post is made private or deleted. None of these appear as a budget or schedule problem, so check the post's status in the creator's account and the code's expiry date in your records first.

Do we need codes for posts from our own brand account?

Not usually. A brand account linked to Ads Manager makes its public posts available to select directly, without a code. Codes are the route for posts that someone else owns. If your own posts are missing from the selection, check the account link rather than generating codes post by post.

Terms used on this page

Also related

Sources

  1. About Spark Ads — TikTok for Business

Related