How listing groups work
A Performance Max campaign that sells products draws them from a linked Merchant Center account. The listing group is the tree inside an asset group that decides which of those products that asset group is allowed to advertise.
It starts as a single node holding the whole feed. You subdivide it by an attribute the feed already carries — brand, product category, product type, item ID, condition or a custom label — and each branch is either included or excluded. Whatever you have not subdivided sits in an Everything else node and stays eligible unless you say otherwise.
The important difference from a Shopping campaign is what a branch does not do. A listing group carries no bid. Performance Max bids towards the campaign target, so the tree is a filter for eligibility and reporting rather than a set of price controls.
Why listing groups matter
Without them, one asset group advertises the entire catalogue behind one set of headlines, images and audience signals. That is fine for a narrow range and poor for a broad one, because the creative that suits a wedding outfit does not suit a work boot, and the campaign has no way to tell the difference on its own.
They are also how you separate products that need different targets. Since the bid follows the campaign, products with very different margins or price points belong in different asset groups, or different campaigns, so each can be given a target it can realistically meet. The listing group is the mechanism that puts them there.
Where listing groups go wrong
The commonest fault is a default tree nobody ever touched: the whole feed in one asset group, one set of assets, and no way to see which products the spend went to. Channel reporting is already thin in this campaign type, so the structure has to do part of that job for you.
The second is overlap. If two asset groups in the same campaign include the same product, the campaign decides which of them serves, and you lose the control you thought you had built. Split cleanly, so every product belongs in exactly one place.
The third is forgetting that the feed keeps changing. New products land in Everything else. If that node was excluded to tidy the tree, your newest stock never serves at all; if it was left included, it inherits creative that may have nothing to do with it.
How to act on it
Decide the split from the business, not from the feed. Margin bands, brand, or the categories your buyers genuinely distinguish are usually better cuts than whatever taxonomy your shop platform exports. Where the feed cannot express the split you want, add a custom label for it and build the tree on that — one attribute you control beats several you do not.
Then re-check the tree after every catalogue change. Look at what fell into Everything else, confirm no product is claimed twice, and make sure each asset group’s creative still matches the products it now covers. The container the tree lives in is the asset group, and the wider mechanics are set out on the page about Performance Max campaigns.
