Unveiling Google's New Brand Guidelines for Performance Max: What Advertisers Need to Know

Google Ads is implementing new Performance Max (PMax) campaigns that will require linking business name and logo assets at the campaign level, effective January 30. This change significantly alters how brands manage their representation.
Key Changes:
- Brand guidelines feature: A new setting that provides stricter control over branding in PMax campaigns.
- Campaign-level asset linking: Advertisers must now link BUSINESS_NAME, LOGO, and LANDSCAPE_LOGO assets at the campaign level instead of the asset group level.
Impact on API Users:
- Current limitations: As of Google Ads API v18, creating brand guidelines-enabled campaigns via the API is not possible. Advertisers are required to use the AssetGroupAsset resource to link the necessary assets.
- Future updates: A future API release will introduce full support for managing brand guidelines-enabled PMax campaigns.
- Consistency in asset requirements: All campaigns must include BUSINESS_NAME, LOGO, and LANDSCAPE_LOGO. Validation of these assets will differ based on whether brand guidelines are applied.
Why This Matters:
This update enhances control over brand representation in Performance Max campaigns. By centralizing the BUSINESS_NAME, LOGO, and LANDSCAPE_LOGO at the campaign level, the new brand guidelines streamline asset management and ensure consistency across automated formats. For API users, this change may require workflow adjustments to maintain compatibility and avoid errors.
What’s Next:
Advertisers should prepare for this transition by:
- Ensuring all required branding assets are ready for campaign-level linking.
- Reviewing integrations that report on or update campaign assets to adapt to the new structure.
- Monitoring API updates for enhanced support of brand guidelines-enabled campaigns.
For more information, check Google's Performance Max optimization guide or consult your Google Ads team.
- #googleads
- #performancemax
- #digitalmarketing
- #brandguidelines
- #api
Comments · 0