A discrepancy emerged between Google’s official stance on API-based placement exclusions and real-world observations, notably for Efficiency Max (PMax) campaigns.
The contradiction:
- Google claims API-based placement exclusions don’t work for PMax
- A number of advertisers report profitable API-based exclusions
- UI-based exclusions perform as anticipated
The inconsistency between Google’s acknowledged coverage and precise performance creates uncertainty for advertisers managing campaigns programmatically.
Why we care. This discrepancy will impacts how they handle placement exclusions at scale by means of APIs and automation instruments. The confusion may affect marketing campaign security and model safety methods, particularly for advertisers operating Efficiency Max campaigns throughout a number of accounts.
If exclusions aren’t being applied in an environment friendly method – your advertisements might be exhibiting on websites of disrepute.
Actuality verify. The difficulty was initially introduced up by Navah Hopkins, Model Evangelist of Optmyzr on LinkedIn, based mostly off a dialog she noticed on Google’s assist discussion board. There we see a Google advisor commenting that placement exclusion isn’t supported in PMax campaigns:
Nevertheless, current testing by automation skilled Nils Rooijmans confirmed on LinkedIn, that API-originated placement exclusions are certainly working for Efficiency Max campaigns, contradicting Google’s official place:
One other advertiser within the assist discussion board states they can add exclusions by means of their API.
Backside line. The documented habits suggests Google’s official stance may have updating, as API-based exclusions seem to perform equally to UI-based ones.
