AI Brief adds languages; unified AI Max reporting is still ahead

What changed

The distinction matters for teams working across markets: broader language support does not establish general beta access, and the forthcoming report should not yet be treated as an available diagnostic tool.

Prepare market-specific terminology and examples before trying AI Brief. A translated brief still needs a local review of the offer, landing page and customer intent. Until the proposed unified view is available, keep the existing exports and campaign notes needed to investigate performance; do not redesign reporting around a promised screen.

The distinction between an available input feature and a planned reporting feature is important in client communication. Teams can prepare to write briefs in the newly supported languages while still explaining that access is restricted. A roadmap statement about reporting should be labelled as a future capability in internal documentation, with the current diagnostic process recorded beside it.

One practical use of the language expansion is a controlled comparison between a locally written brief and a translated version of an existing brief. Review the resulting intent and brand language before using either in campaign work. Record misunderstandings that require human clarification. This evaluates whether the tool reduces preparation effort in that market without confusing a better brief with an independently measured improvement in advertising performance.

Why it matters for advertisers

Language support can remove a practical barrier to preparing briefs across markets. It does not resolve account eligibility or supply the combined reporting needed to explain how search terms, creative and destinations work together.