Create campaigns around the way you manage your ads. You choose how to group products, organize campaigns and ad groups, name them, and set up targeting. The Merch Jar Copilot can build that structure through the API after you review and approve the plan. You can also use the creation endpoints directly in your own integration.
Campaign creation supports Sponsored Products. API access and the Copilot are included with every Merch Jar subscription, including legacy plans.
Describe what you want to create
Follow the Copilot setup guide to connect your AI client to Merch Jar. Use an API key with permission for the creation operations you need. The API scopes are listed below.
Describe the setup you want, whether that’s a single campaign or a structure spanning many products. You can follow your existing naming and grouping conventions, separate campaigns by targeting approach, or build a different setup for a particular launch.
Share the products and any targeting or settings you already have. An ASIN list can be pasted into the conversation or supplied in a spreadsheet. A column named asin is one convenient format for a product list. Use products eligible for advertising in the selected marketplace.
For example:
Create campaigns for these products using the structure I’ve described.
If you want help deciding on a structure, ask for a proposal. The Copilot can ask for missing details and work through the plan with you.
Choose the parts you need
The API lets you create campaigns, ad groups, product ads and targeting. You decide how to combine them. That can mean creating a complete structure or adding ad groups, ads or targets to parents that already exist.
Campaign count, products per campaign, ad-group organization, naming, budgets and targeting choices come from your plan. You can use automatic targeting, supported keyword match types or product targeting where appropriate. The API reference lists the supported entity combinations and required fields.
Review the plan and total budget
Before approving creation, check:
- The account, marketplace and product list.
- Campaign and ad-group organization, names and product assignments.
- The campaign count and daily budget for each campaign, plus the combined daily budget.
- Bidding strategies, ad-group default bids and any explicit keyword or target bids.
- The proposed start date and which campaigns, ads and targets will remain paused.
Be explicit about whether a budget applies to each campaign or to the whole setup. Review the combined daily budget for the campaigns you’re creating. A daily budget is not a promise of actual spend.
The proposed amounts must also meet Amazon’s limits for the selected marketplace and currency. If an allocation is too small, decide whether to change the total or the campaign count before creation.
Create and verify the structure
Approve the reviewed plan, then check the returned results in Merch Jar. Start paused while you verify the structure and enable only the campaigns and targeting you intend to run.
Confirm that the campaigns, ad groups, product ads and targeting match your plan, including which products belong where. Check names, budgets and states. A campaign appearing in the table alone does not prove all its children were created.
Amazon generates the automatic targeting groups for automatic campaigns: close match, loose match, substitutes and complements. If they aren’t visible yet, reconcile the result in Amazon Ads before creating anything again. An empty table immediately after a request is not proof that creation failed.
If a batch partly succeeds, review the individual results and identify what remains. Don’t resend the whole product list without checking for campaigns and other entities that already exist.
Example from the campaign creation video
In the video, Cameron supplies ten ASINs and chooses an Auto, broad-match Research and Exact campaign for each product, creating thirty campaigns. That is one example of a structure you can request. Your setup can use a different number of campaigns, group products differently and use different targeting.
The manual campaigns in that demonstration use placeholder keywords and remain paused while the structure is being built. Use your own reviewed targeting when you’re ready to run ads. The demonstration covers structure creation; keyword research and Smart Campaign connections are separate work.
Creation operations available through the API
You can also build your own integration using the same endpoints. Create parent entities first and use their returned IDs when creating children.
- Create campaigns:
POST /api/v5/campaigns, usingcampaigns:write. - Create ad groups within campaigns:
POST /api/v5/ad-groups, usingad_groups:write. - Add product ads to ad groups:
POST /api/v5/product-ads, usingads:write. - Create supported keywords and product targets:
POST /api/v5/targets, usingtargets:write.
The API also supports negative creation. Negative keywords use the supported keyword branch of /targets; ad-group negative product targets use /negative-targets with negative-targets:write. Check the API reference for the supported combinations and exact request bodies.
Use the profileid header for the selected advertising profile. Keep campaign, ad-group and target IDs as decimal strings. An automatic campaign uses autoCreationSettings.autoCreateTargets: true; Amazon generates its automatic targets, so do not send separate creates for those four groups.
Create responses contain success, partialSuccess and error arrays. Inspect each item; an HTTP 200 does not mean the entire batch succeeded. Creation does not have the same idempotent retry contract as campaign-setting updates. If the outcome is uncertain, reconcile the entities before retrying.
The public API reference contains the current schemas, including campaign budgets, marketplace and start-date fields, and ad-group bid requirements.
Change settings after creation
Once the structure exists, you can change campaign names, daily budgets, bidding strategies and placement adjustments. Follow Change campaign settings through the API for those operations.