Structuring an Amazon Ads Account: Hierarchy, Naming, and Portfolios

CH.01Map the five-tier hierarchy Amazon actually uses

Before you create a single campaign, draw the real tree. Reading top to bottom, an Amazon Ads account nests as Account or Manager Account, then Portfolio, then Campaign, then Ad Group, then Ad and Target. The lower four tiers are exactly the entity names the bulksheet uses, which is why designing to them now saves you from re-architecting later.

The structure only stays readable if each ad group holds a single, tightly related product theme. Mix unrelated products into one ad group and you can no longer tell which target drove which sale. Build to the limits Amazon publishes, because they gate how granular you can ever go.

The bulksheet entity model you are designing toward

1. ProductThe top record type in the bulksheet, scoping which catalog the rows below belong to.
2. CampaignThe intent and budget container, sitting inside a portfolio when you group it.
3. Ad GroupOne product theme per group, holding the ads and the targets.
4. Ad and TargetProduct Ad, Product Targeting, and Keyword rows, each with an Operation column of Create or Update; a blank Operation leaves the row unchanged.

CH.02Choose a segmentation logic before you group anything

Portfolios let you group campaigns into buckets, and Amazon describes grouping them by multiple brands, product lines, business lines, or seasons. The decision that matters is picking one consistent logic and holding to it, because mixing schemes inside one account breaks reporting and makes the portfolio spend ceiling meaningless.

• Group by brand when you sell several distinct brands and each needs its own budget guardrail.
• Group by category or product line when one brand has clearly separable product families.
• Group by season or promotion when you run date-bound pushes that need their own spend window.
• Group by goal, such as launch versus defend versus harvest, when intent is your primary management axis.

CH.03Build the campaign skeleton, auto for discovery and manual for control

With the hierarchy mapped and a segmentation logic chosen, build the campaign skeleton per parent ASIN. The pattern is one automatic campaign for discovery and one manual campaign for control, with child ASINs kept in separate ad groups so their data stays clean. Before any of this earns impressions, the detail page itself has to clear Amazon's eligibility bar.

The auto-to-manual harvest loop

Run the auto campaign for 7 to 14 days, move converting search terms into the manual exact campaign, and add each promoted term as a negative in the auto campaign so the cheaper campaign stops cannibalizing clicks that belong in exact. Single keyword ad groups deliver precision on a flagship term, but applied across the whole account they bloat your campaign count toward the 10,000 ceiling, so use them where the control is worth it and not as a default.

CH.04Design a pipe-delimited naming convention the bulksheet can parse

A naming convention is not housekeeping. It is the machine-readable key that lets the bulksheet's parse, filter, and edit-at-scale workflow actually function. Pipes give a spreadsheet a clean delimiter to split on, so you can filter to every auto campaign, or every campaign in one category, in seconds.

Use a fixed template such as SP | Auto | Brand | Category | MatchType | Goal and apply it to every campaign. Keep ad-group names unique within their campaign, and never edit the Record IDs the bulksheet uses to identify entities, because changing an ID detaches the row from its target.

What a parseable name buys you

• Split on the pipe in a spreadsheet and every field lands in its own column for instant filtering.
• Bulk-edit all campaigns matching one field, for example every Auto row, in a single pass.
• Read intent, brand, category, match type, and goal at a glance without opening each campaign.
• Keep reporting clean because the name itself carries the segmentation you chose in Step 2.

CH.05Wire portfolios as your real monthly spend ceiling

This is the step most accounts skip and the one that makes the structure governable. A portfolio budget cap is the maximum spend by all campaigns in the portfolio for the period, and when the cap is reached, every campaign in the portfolio stops delivering. Portfolio caps override campaign budgets: in Amazon's own example, campaigns A and B each carry a 500 dollar lifetime budget, but a 750 dollar portfolio cap pauses both at 750 dollars of combined spend even though each campaign still has budget left.

1. Pick a cap typePortfolios offer exactly three options: no budget cap (the default), a recurring monthly cap that resets the first day of each month, and a date range cap.
2. Trust the over-delivery creditAt period end Amazon will not charge more than the set portfolio budget and credits back any over-delivery at the campaign or portfolio level.
3. Set campaign budgets above the capCounterintuitively, set individual campaign budgets higher than the portfolio cap so a winning campaign is never throttled by its own budget while the portfolio cap governs total spend.
4. Consider the unspent-budget betaThe Unspent campaign budget in portfolios beta lets a Sponsored Products campaign that has spent its full daily budget borrow unspent budget from siblings in the same portfolio, spending up to 100 percent more than its average daily budget on a day, while the portfolio never exceeds its overall cap; unspent budget resets to zero at the start of each month.

CH.06Layer manager accounts for agencies and multi-brand portfolios

One account with portfolios is enough for a single brand. The moment you manage multiple operating companies, geographies, or business units, the tier above the portfolio matters. Nested manager accounts, announced April 15, 2024, let advertisers and partners link multiple Manager Accounts into a multi-level hierarchical group, with sponsored ads and ASDP accounts sitting underneath.

• Stay in one account with portfolios when a single brand or buying team owns all the spend.
• Move to nested manager accounts when separate teams, brands, or regions need data separation with aggregate reporting on top.
• Map the manager-account hierarchy to your real org chart of operating companies, geographies, or business units.
• Keep the portfolio, campaign, ad group, and ad structure identical underneath each account so naming and bulksheets stay consistent across the group.

CH.07A 60-minute account-skeleton checklist and naming cheat sheet

Here is the condensed sequence to stand up a clean skeleton in about an hour, followed by a copy-paste naming string. Clear the detail-page eligibility bar first, because no structure compensates for a page that cannot earn the sale.

• Confirm the detail page clears Amazon's bar: about 60-character title, four or more 1,000-pixel images, three or more bullets, five or more reviews at 3.5 stars, featured offer badge.
• Pick one segmentation logic, by brand, category, product line, season, or goal, and write it down.
• Create one portfolio per segment and set its budget cap to none, recurring monthly, or a date range.
• Build one auto and one manual campaign per parent ASIN, with child ASINs in separate ad groups.
• Name every campaign with the same pipe template, for example SP | Auto | Brand | Category | MatchType | Goal.
• Set campaign budgets higher than the portfolio cap so winners run unimpeded under the ceiling.
• Schedule the search-term report so the 7-to-14-day harvest from auto into exact becomes routine.

Build the skeleton once, name it so a spreadsheet can read it, and the account stays governable at 10,000 campaigns. Capconvert Amazon Ads playbook

From here the structure does its job. Portfolios hold the spend ceiling, names carry the segmentation, the bulksheet edits at scale, and the auto-to-manual loop keeps feeding proven terms into the campaigns where you bid hardest. That discipline, set up once, is what keeps a large account legible instead of chaotic.