What you need to know
- This is a planning handoff, not a Meta Ads Manager import format or a PlugMind API payload.
- Use one row per intended ad and preserve real account and asset identifiers.
- Uploading an image, creating an ad and activating delivery require separate decisions.
Download the planning template
A useful bulk-ad template removes ambiguity before you create anything. It tells the reviewer which image, copy, destination and existing ad set belong to each intended ad. That is different from a platform-native import file, whose columns and accepted formats must come from the platform itself.
Open the file in a text editor or give it to your assistant as a planning document. Replace every bracketed placeholder and delete the example rows you do not need. PlugMind does not provide a general-purpose importer that automatically executes this file.
What each row needs to establish
| Field | Purpose |
|---|---|
| row_id and ad_name | Distinguish each intended ad, including variants using the same image. |
| image_filename and uploaded_image_hash | Track the original file and the successful Meta upload. |
| existing_ad_set_id | Target the exact existing ad set in the authorized account. |
| page_id and instagram_account_id | Record the chosen, available advertising identity. |
| primary_text, headline and destination_url | Preserve the complete approved message and destination. |
| requested_status | PAUSED for the creation review. |
Account and workspace context belongs at the top of the plan. For a separate client or account, create a separate document rather than hiding a change of account among otherwise similar rows. Optional identity fields should remain explicitly empty when they are not being used; never invent values.
Image hashes are filled from successful upload results, not derived from filenames. If the same file is used for two approved variants, you can keep its returned hash associated with both planned rows instead of uploading it again solely to make another row.
Review the handoff before asking for execution
Compare the planned ad count with your intended test. Two images with two different messages each can mean four ads, while two images in a single format may represent a different configuration. Do not let the assistant decide that relationship from the number of files.
Check each landing page and its approved copy together. Tracking parameters should preserve the intended destination. A different offer, price or unsupported claim is an editorial problem to resolve before a tool validates the technical payload.
Move from a reviewed template to a saved batch
Upload the actual files with the image-upload preview and approval flow. Fill in the successful hashes, then have the assistant prepare the exact supported Meta batch proposal. The saved plan, not this editable planning file, becomes the execution reference after approval.
Keep the final planning document alongside the returned IDs and batch status. If execution is partial, record which rows succeeded. Inspect uncertain writes and reuse successful results instead of regenerating the whole batch.
This template does not establish support for videos, carousels, placement-specific asset combinations or direct Meta spreadsheet import. Use it for the documented image-ad workflow and confirm any additional configuration separately. For a full upload-to-results walkthrough, follow the bulk-image-ad article linked below.
Frequently asked questions
Can I import this file directly into Meta Ads Manager?
No. It is a PlugMind-oriented planning document. Use Meta’s own current import specification for native bulk imports.
Does downloading or submitting the template create ads?
No. The document does not execute anything. Account access, upload approval, batch validation and creation approval remain separate steps.
Why use JSON instead of pretending this is an upload-ready spreadsheet?
The document makes nested account context, rows and review notes explicit without implying a platform-native importer exists.
Sources and verification
Platform references are listed below. PlugMind tool descriptions were checked against its implementation. Example prompts are suggested workflows, not claims of results from a live advertising account.