When to run this checklist
Run it once the campaign, ad groups and ads are built and still unpublished. Run it again whenever the pixel or the Events API connection changes, whenever the optimisation eventThe conversion event an ad set or campaign is told to optimise delivery towards, such as a purchase, lead or install. changes, and whenever new Spark Ads codes are added, because each of those can break delivery or measurement without an error message. Ad groups that optimise toward a conversion learn from what the pixel reports, so a measurement fault at launch teaches the algorithm the wrong lesson from the first impression. For an account's first campaign, the tutorial on launching a first TikTok Ads campaign walks through the build this list then checks, from the written goal to the first weekly read.
The builder runs it while building and a second person runs it before the campaign is switched on. If creators are involved, whoever manages the creator relationship should confirm the Spark Ads and disclosure lines, since they hold the authorisation codes and the contracts. The paid campaign launch SOP describes the approval route; this list is what the approvers check.
Before you start
- The campaign brief, with the objective, the optimisation event, the audience, the budget and the dates.
- The pixel's event setup and, if the Events API is in use, a note of how events are deduplicated.
- A test journey that can complete the optimisation event without corrupting real reporting.
- The creative files and their sound sources, with a record of where each sound came from.
- The Spark Ads codes and the creator agreements that cover them.
- A phone with the TikTok app, since the landing page opens in the in-app browser, not in a normal browser.
The checklist
The groups follow the build: how the campaign is structured, who it reaches, how results are recorded, what the videos show and say, and where the click lands. The landing and sign-off group comes last because it depends on everything above it.
Structure
Audience
Measurement
Creative
Landing and sign-off
Where each check is explained
The widget keeps each line short enough to tick; the reasoning lives in the guides. Each check links to the page that explains it.
| Check | Explained in |
|---|---|
| Objective and optimisation event match the brief | TikTok Ads campaign structure |
| Budget level, schedule and bid strategy | TikTok Ads campaign structure |
| Naming convention | UTM and naming conventions |
| Location, language and age settings | TikTok Ads for product sales |
| Automatic targeting or custom audiences | TikTok Ads for product sales |
| Recent purchasers excluded | Prospecting vs remarketing |
| Pixel fires the optimisation event | TikTok Pixel and Events API setup |
| Pixel and Events API deduplicated | TikTok conversions higher than orders |
| Event values and currency | TikTok Pixel and Events API setup |
| Campaign parameters on every link | UTM and naming conventions |
| Hook before logo | TikTok content formats and hooks |
| Text inside the safe zone | TikTok content formats and hooks |
| Sounds licensed for advertising | Posting cadence and trends on TikTok |
| Spark Ads codes authorised and valid | TikTok Spark Ads code not working |
| Paid creator content disclosed | Influencer contracts and disclosure |
| Destination works in the in-app browser | Speed and mobile for landing pages |
| Page repeats the video's offer | Message match |
| Approvals and first-day watcher | Paid campaign launch SOP |
If an item fails
The campaign stays unpublished until the line passes. Measurement failures matter most, because they shape what the algorithm optimises toward from the first hour. If the Tracking PixelAn ad platform's browser code that reports page views and events on a site back to the platform. does not fire the optimisation event on a test journey, do not launch on that event: fix the event first, or launch on an objective that does not depend on it and say so in the brief. If pixel and Events API events lack a shared identifier, the platform's conversion count will run ahead of real orders, the reported CPACost of each conversion. will flatter the campaign, and bidding will chase the inflated numbers; DeduplicationRemoving double counts when one conversion is reported by more than one source. is a launch requirement, not a later clean-up.
Creative failures split in two. A missing hook or text in the unsafe area is a creative fix that goes back to whoever made the video. An unlicensed sound or an undisclosed creator post is a legal and policy issue: the ad cannot run as it is, however good it looks, and the fix may need the creator or the rights holder. An expired or unauthorised Spark Ads code usually needs a fresh code from the creator, which can take days, so plan for it rather than swapping in an unapproved video; the Spark Ads guide explains how authorisation works. Paid UGCContent about a brand made by customers or creators rather than by the brand itself. without the disclosure the agreement requires is a problem for the brand and the creator alike.
If the landing page fails in the in-app browser, the campaign waits. Pages that work in a desktop browser can break inside TikTok's browser: logins, payment buttons and pop-ups are the usual casualties.
A skincare brand's launch that nearly double-counted
A skincare brand called Glossbrae sets up a conversion campaign optimising toward purchases, with the pixel on the site and the Events API sending the same purchases from its store platform. On the test journey, one purchase appears twice in Events Manager because the store sends an order number as its event identifier while the pixel sends nothing. The developer passes the order number from both sources and the second test shows one purchase. The reviewer also finds that two of the eight videos carry their price in the lower third, where the caption and buttons cover it, and that one Spark Ads code expired. The brand launches with six videos and replaces the other two the following week.
Common mistakes
- Launching on an event nobody tested. The ad group optimises toward a purchase event that fires on the basket page as well, and spends against the wrong action.
- Running the pixel and Events API without a shared identifier. Reported conversions run well ahead of orders, and the campaign looks better than it is.
- Reusing organic videos unchanged. Captions placed for an organic post sit under the ad's call-to-action button.
- Assuming a trending sound is free to use. Sounds available for posts are not automatically licensed for ads.
- Treating Spark Ads codes as permanent. Codes have an authorisation window, and creators can revoke them.
- Testing the landing page in a desktop browser only. The page that matters is the one inside the app.
The campaign launch QA checklist covers the checks every paid campaign shares, and the checklists library holds the rest.
