Placement and site excludes are direct keys
Supply Audit can apply placement and site exclusions. Those keys do not need a custom list. Domain still does.
Published 2026-09-09 · Search job: how to exclude bad ad placements
Corrected September 2 2026, after the first real Supply Audit findings were mostly blocked by a wrong sentence.
We used to refuse placement and site apply with a message about Beeswax app_site lists and a child-seat custom_list the compiler could not emit. Live targeting keys say otherwise. placement and site are direct keys (<exchange_handle>/<placement_id> and <exchange_handle>/<site_id>). Domain and app-bundle still need seat-level list objects.
That wrong sentence had been gating most of the waste the first run could see. Apply still never pauses a campaign, never writes to Beeswax from the audit route, and never changes a budget. It clones targeting. Live delivery changes only if a campaign is later pointed at the new set.
Stored finding keys are composites. Send the value after the pipe to the exchange. The un-split key matches nothing.