Skip to main content
Studio → Uploads takes supplied creative files through an actual Meta ad launch. You need the intended connected account, the destination campaign and ad sets, Page and ad defaults, and permission to create ads. Launch can create active ads, so inspect the delivery choice as well as the files.

​
Prepare the destination and assets

  1. Select the correct account and open Studio → Uploads. Check Upload Creatives shows that account.
  2. Choose the campaign and assign the intended ad sets. The assignments determine where each ad is created; merely selecting a campaign is not enough.
  3. Upload your files, or use the Google Drive option if it is connected and shown. Wait for uploads to finish and inspect unsupported or failed files separately.
  4. Choose Single for individual ads or Carousel for a card sequence. Assign the assets to the intended ad sets; for a carousel, review card order and each card’s content.
  5. Review copy, destination URL, and the Page or other required account defaults. Check the actual preview rather than assuming a filename identifies the right creative.

​
Review and launch

Open Launch readiness and resolve every Needed requirement. Provider validation still applies even when the local checks say Ready. Check whether the ads are being launched active or paused. Active ads may enter delivery subject to Meta review, their parents’ status, schedule, and budget. Paused ads still create real provider entities and need a separate delivery review to resume. Choose the launch action only after verifying the account, destinations, asset count or card order, copy, URL, and delivery choice. The button identifies Launch Ads or Launch carousel, with the quantity where applicable.

​
Verify individual outcomes

Inspect successes and errors after the attempt. A batch can partially succeed: do not relaunch the entire batch simply because one item failed. Check created ads in the intended account and ad sets, including their identities, content, and configured status. For an unclear outcome, preserve the original launch result and verify Meta before submitting another attempt. For failed items, fix the displayed requirement and retry only the unresolved work. Upload completion, local readiness, provider creation, and actual delivery are separate states. Next: read ad performance or contact support.