Load approved creative variants into ad drafts
Use a structured asset folder and control sheet to prepare a correctly named ad set without repetitive downloads and uploads.
How this works
Use a structured asset folder and control sheet to prepare a correctly named ad set without repetitive downloads and uploads. Asset upload work becomes error-prone when filenames, copy, destinations, and settings live in different places. A structured control sheet should identify exactly which files belong together and make the created draft easy to verify before launch.
Treat the folder and control sheet as a release manifest for ad drafts. Validate assets and settings before using any available platform connector. Create paused drafts or a manual import package, then reconcile the resulting identifiers with the source rows.
Before you start
Asset convention
Define folders, filenames, versions, and which variants form one creative family.
Control sheet
Provide the exact campaign, copy, destination, and budget fields.
Platform access
Confirm a configured draft-creation path or use a file-based handoff.
Prepare the inputs
- asset_manifest
- Required
File records
Include file path, version, dimensions, and checksum where available.
- control_rows
- Required
One row per intended draft
Require stable row IDs and complete settings.
- copy_variants
- Required
Approved text
Map text to the correct creative family.
- destination_settings
- Required
Account and campaign IDs
Use current configured identifiers.
- creation_log
- Required
Prior receipts
Prevent duplicate drafts after retries.
Implementation, step by step
Validate the manifest
- Check every selected row resolves to the intended files.
- Reject missing, duplicated, or ambiguous versions before uploading.
Checkpoint: A complete draft manifest.
Inspect asset suitability
- Verify dimensions, duration, format, and required text for the placement.
- Review product fidelity and approved claims separately from technical file validity.
Checkpoint: Assets marked ready or held.
Resolve settings
- Map copy, destination URL, tracking fields, campaign, and budget to each row.
- Keep daily and lifetime budgets distinct and require an explicit paused or draft state.
Checkpoint: An exact settings preview.
Create drafts through available tools
- Use the authorized connector or prepare the supported import format.
- Record each creation result immediately so partial completion can be reconciled.
Checkpoint: Draft IDs or a ready import package.
Compare source and destination
- Inspect uploaded media, copy, URL, names, and settings in the resulting draft.
- Treat successful upload as separate from correct ad assembly.
Checkpoint: A row-by-row verification record.
Hand off for launch review
- Present verified drafts and unresolved exceptions to the media buyer.
- Leave launch state unchanged unless the user has separately authorized it.
Checkpoint: A controlled draft handoff.
Decisions along the way
A row points to several plausible files
Hold it and request the intended version.
Only some drafts are created
Resume from missing row IDs after checking receipts.
A destination setting is invalid
Correct that row without recreating successful drafts.
What you will produce
ad-draft-manifest.csv
CSVLinks prepared assets to platform drafts.
Include: row_id · asset_version · copy_id · destination · draft_id · status
draft-verification.md
MarkdownSupports a precise launch review.
Include: row_id · checked_fields · exceptions · review_owner
Check the result
- Open the actual uploaded creative rather than trusting its filename.
- Compare budgets and URLs with the control sheet.
- Check every created draft remains in the intended non-live state.
- Reconcile one manifest row to one intended draft.
When something goes wrong
Upload times out
Inspect the creation log and platform state before retrying.
Wrong asset version is attached
Replace it in the draft and reverify the complete package.
A connector cannot create drafts safely
Deliver a manual import package and state the limitation.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Prepare two paused ads from approved asset families.
Inputs
Synthetic example. Synthetic row R1 references video-v2 and copy-A; R2 references image-v1 but the file is missing.
Expected result
Synthetic expected result. Create or prepare R1 only, keep R2 held for the missing file, and return actual draft IDs. Neither row is described as launched.
Run a small pilot
Start small
A small asset batch with deliberately missing and duplicate references.
Record the baseline
Record preparation time and manual correction rates.
Agree success criteria
Agree exact field fidelity and idempotent retry behavior before larger batches.
Stop or revise
Stop creation if draft state or account identity cannot be confirmed.
Keep the scope clear
- Asset preparation does not authorize campaign launch.
- Do not infer missing budget, copy, or destination settings from previous campaigns.
Check before using
Check account, placements, variants, budget, links, and naming. Creating a draft must not imply approval to spend.
Business activities
- Run advertising and acquisition tests
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Approved creative files by size · Naming convention · Destination campaign and draft settings
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow