A campaign export can be the starting point for two different jobs: updating existing objects or preparing new ones from a reference. Confusing those jobs can leave a tidy-looking spreadsheet without the identifiers its intended operation needs. Before changing names, budgets or copy, decide whether each row must find an existing object or describe a new one.

TikTok's upgraded Smart+ creation guide, updated in October, points advertisers to Excel and CSV bulk creation and editing. This is a current workflow reference, not evidence that bulk import first launched this month. The platform's editing guidance says to preserve Campaign, Ad Group and Ad IDs; its reference-file creation guidance instructs advertisers to remove those identifiers when creating new ads.

Names help the operator; IDs locate the object

An international team may rename a campaign to reflect a new product, market or reporting convention. The readable name helps people find their work, but it is not a safe replacement for the system identifier. An old name left in a file does not repair a missing or altered ID.

That is why a spreadsheet prepared for analysis should not automatically become an import file. Analysts may rename headers, collapse repeated values or remove columns to make a report easier to read. An import format has a different purpose: it must preserve the structure the receiving system expects. TikTok's guidance also warns against changing headers and removing required fields.

Keep an untouched export, then make a working copy for the specific edit. Preserve the identifiers and template structure while changing only supported fields needed for the task. The untouched file helps explain what was exported; it should not be treated as a promise that re-importing it will reverse every possible change.

Repeated campaign or ad-group names across rows are not automatically duplicate records. A hierarchy can require the same parent object to appear beside several child ads. Before deduplicating anything, establish what each row represents and at which level the intended setting belongs. A spreadsheet that looks repetitive to a person may still encode necessary relationships.

For a regional marketer working with a China-based supplier team, an instruction such as “update the German campaign” is too loose if several campaigns match that description. Agree on the object set from the export or account interface. Resolve an uncertain identity before importing, rather than using name similarity to guess where the change belongs.

Separate the creation file from the editing file

When the task is to create new ads from an existing configuration, use the documented creation workflow. When the task is to update existing ads, retain their identifiers. Label the files by purpose so that a reference with IDs removed cannot accidentally become the next revision upload.

The distinction is especially important when one colleague prepares the file and another imports it in a different time zone. A filename such as “final” says little about whether the file creates or edits objects. A short handover should state the action, account and intended object range, without including credentials or unnecessary buyer information.

Start with a small set that can be checked directly in Ads Manager. The point is to test object matching and field interpretation, not to infer campaign performance from a tiny sample. After the import, inspect the original objects and look for unintended new ones. A file-processing message cannot establish that every business change landed exactly where intended.

If a setting is not supported for bulk editing, changing column names or deleting mandatory fields is not a workaround. Use the supported route for that setting or narrow the operation. Bulk handling is valuable when the intended changes are repeatable and clear, not when every row still needs a new strategic decision.

Our article on settings changed by Smart+ duplication examines configuration conversion. Object identity comes first here. Before comparing old and new settings, know whether the spreadsheet was supposed to modify the old campaign or create another one.

For a handful of changes, the interface may be simpler than preparing a bulk file. Use the spreadsheet when it reduces repetitive input without obscuring the target objects. The useful result is a known change to a known object, not merely a successful upload.

Sources