Ad group language targeting is a dimension in Amazon Ads unified reporting that records the language setting a buyer applied to an ad group. It describes a delivery rule, not a creative and not a page: the instruction that an ad group should bid only where a given language is in play. The field exists because programmatic campaigns on Amazon reach people across dozens of countries and on open-web, app and streaming inventory where language does not follow borders. A US campaign reaches Spanish speakers; a campaign in Canada reaches English and French speakers. When delivery data can be grouped by the language rule in force, an advertiser can see what each linguistic slice of a campaign cost and returned.
The field appears among the ad group attributes of the unified reporting dimensions reference that Amazon updated on November 11, 2026. In PPC Land's field-by-field reading of that reference, published the next day, ad group language targeting is one of five ad group fields that apply to DVA+ only, alongside ad group type, ad group external ID, ad group comments and ad group budget amount. DVA+ is the AI-driven campaign type that merges buying across the programmatic platform known until September 29, 2026 as Amazon DSP, Sponsored Display and Sponsored TV. For Sponsored Products, Sponsored Brands and Sponsored Display rows, the column returns null.
Where it sits in the hierarchy
Unified reporting renamed the programmatic levels to match sponsored ads. A DSP order became a campaign, a line item became an ad group, and a creative became an ad. PPC Land's table records "Line item ID" and "Line item name" as the former DVA+ names of Ad group ID and Ad group name. It does not report a former name for the language targeting field, though the setting itself lived on the line item in the legacy DSP.
That lineage shows up in third-party data connectors. Adverity's documentation for its Amazon DSP connector lists a line item language targeting field, described as the language used for targeting within a line item, separate from a creative language field. The unified field carries the same concept under the new vocabulary.
Because the setting belongs to the ad group, the value repeats on every row beneath it. Every ad and every impression served by an ad group carries the same language targeting value, whatever language the creative or the surrounding page used.
How language targeting works in programmatic buying
Amazon has not published a public description of how its language rule is evaluated, so the mechanics are best understood through the protocol all demand-side platforms (DSPs) read. Under OpenRTB, the bid request standard maintained by IAB Tech Lab, a publisher or its supply-side platform (SSP) sends a description of each available impression. Language can arrive through two separate objects.
The Device object carries a language attribute holding the browser or operating system language as a two-letter ISO 639-1 code such as "en" or "es". The Content object, nested in the Site or App object, carries its own language attribute describing the article, video or programme being consumed. OpenRTB 2.6, released in 2022, added langb to both objects to carry IETF BCP 47 tags, which can express variants such as "pt-BR" or "fr-CA" that two-letter codes cannot. PPC Land's explainer on language targeting, published on September 6, 2026, traces that history and notes that OpenRTB 2.5, released in 2016, had added wlang, a list of creative languages a publisher accepts, and a creative-level language field on the bid.
A DSP applying a line item's language rule checks the request against the rule before bidding. If the rule says Spanish and the request signals English, the line item does not bid. Platforms differ in which signal they check. According to PPC Land's language targeting explainer, Google's Display & Video 360 matches the rule against languages declared in the bid request and infers languages from content and user signals when the publisher declares none, so a Spanish-language line item can win an impression on an English-language site. Google's Campaign Manager 360, by contrast, matches only browser settings and treats an ad as ineligible when browser language is unavailable.
Which of these Amazon follows, and whether it uses its own shopping signals as well, is not stated in any Amazon document readable as of November 2026. The answer matters for interpretation. A rule evaluated against device language selects people; a rule evaluated against content language selects environments.
A worked example
Consider a US retailer running a DVA+ campaign with two ad groups. One carries an English language rule and English creatives. The other carries a Spanish rule and Spanish creatives aimed at Spanish-speaking households. Both buy open-web display and streaming video.
A unified report grouped by Ad group name and Ad group language targeting returns two rows with impressions, cost, detail page views and purchases for each. Adding Content language splits each row again by the language of the page or programme. If the Spanish ad group shows a large share of impressions next to English-language content, the rule is being evaluated against something other than the content, most likely device language. Adding Ad language confirms whether each ad group served the creative its rule intended. A single impression can therefore carry three language values in one report, and they need not agree.
Why it matters
Language is one of the oldest targeting controls in digital advertising and one that is under pressure. On August 14, 2026, Ginny Marvin, Google's Ads Product Liaison, announced that Google Ads would remove the language setting from Search and Performance Max campaigns starting in September. Google's reasoning was that "the campaign-level setting has become redundant" as automated systems infer language. The removal came nine months after the end-2025 deadline Google had first set in its help documentation in August 2025.
Amazon's programmatic stack has moved the other way on reporting, if not on controls. The language rule a buyer sets is now a named dimension. For advertisers running multicultural campaigns, that makes the rule auditable in the same report as spend and sales.
The field also matters for account structure. On July 30, 2026, Amazon announced that DSP-only accounts would be upgraded to advertiser accounts covering 34 countries in five regions. On March 30, 2026, Amazon's Global Creatives launch had already let advertiser accounts define standard display creatives once per region, with the language menu listing all languages in the region, such as English, Spanish, French and Portuguese for the Americas. As campaigns and creatives span regions, the ad group language rule becomes one of the few remaining ways to keep a language version on its intended audience.
Migration adds urgency. Under Amazon's published timeline, creation and editing of legacy reports stop on December 17, 2026, and unmigrated reports and their history are deleted on January 31, 2027. Dashboards that read the old line item language column need remapping before then.
Limitations and open questions
The first limitation is coverage. Ad group language targeting is one of 59 dimensions that, according to PPC Land's count, serve DVA+ alone. Sponsored ads advertisers cannot use it, because sponsored ad groups carry no language rule: language there follows the marketplace, and Amazon translates headlines, videos and Sponsored Display creatives automatically instead.
The second is definition. Amazon's dimensions reference, as relayed by PPC Land, does not reproduce a definition, a list of allowed values or a format. It is unconfirmed whether the field returns a single language, a list, an inclusion or exclusion flag, a two-letter code or a full language name. An ad group with no language rule may return null, "all" or nothing, and that ambiguity makes untargeted and non-applicable rows hard to separate.
The third is signal source. Without documentation on whether the rule checks device language, content language or both, the field reports intent, not outcome. Chrome's Accept-Language reduction, tested from Chrome 109 in January 2023, trims the browser language data sent to sites to a single preferred language, which narrows the device signal any DSP can read.
The fourth is the gap between rule and reality. A language rule set on an ad group says nothing about what share of impressions actually met it, especially where publishers omit language from bid requests. Only cross-reading with Content language gives a partial check.
Ad group language targeting is not...
Ad language. The language of the creative itself, declared when the ad is built. A Spanish creative can sit in an ad group with no language rule.
Content language. A supply attribute describing the language of the page, app or programme where the ad appeared, determined by the publisher's content rather than the buyer's settings.
Console language preference. Amazon DSP has let users switch the interface language of the console since March 1, 2024. That setting changes the menus a buyer reads, not where ads serve.
Location targeting. Geographic targeting by country, region or postal code. Country is a common proxy for language, and the confusion between the two is the reason both controls exist.
Recent developments
Amazon published the dimensions reference listing ad group language targeting among 156 attributes on November 11, 2026, and PPC Land's analysis the next day placed it among the DVA+-only ad group fields. DVA+ itself remains in a US closed beta, with general availability in 35 markets planned for the first quarter of 2027, so few advertisers can yet populate the column. Google's removal of campaign-level language targeting from Search and Performance Max in September 2026 leaves Amazon's programmatic stack among the platforms where a buyer-set language rule still shows up in reporting.
Timeline
- 2016 - OpenRTB 2.5 adds
wlangand a creative-level language field to the bid request standard. - 2022 - OpenRTB 2.6 adds BCP 47 language fields
langbandwlangb. - January 2023 - Chrome 109 opens an origin trial for reduced Accept-Language headers.
- March 1, 2024 - Amazon DSP adds a console language switcher for users.
- April 2, 2024 - Microsoft Advertising adds Thai, Malay, Indonesian, Filipino and Hindi to language targeting.
- August 18, 2025 - Google help documentation sets end-2025 removal of language targeting in Search.
- November 11, 2025 - Amazon Ads unified reporting opens in beta.
- March 30, 2026 - Global Creatives lets advertiser accounts define display creatives per region with regional language validation.
- June 8, 2026 - Unified reporting reaches general availability in the Ads Console.
- July 30, 2026 - DSP-only accounts upgraded to advertiser accounts spanning 34 countries.
- August 14, 2026 - Google announces removal of language targeting from Search and Performance Max from September.
- September 29, 2026 - Amazon DSP name retired in favour of DVA; DVA+ enters US closed beta.
- November 11, 2026 - Dimensions reference lists ad group language targeting as a DVA+-only ad group field.
- December 17, 2026 - Legacy report creation and editing scheduled to stop.
- January 31, 2027 - Unmigrated legacy reports and their data scheduled for deletion.
Related PPC Land coverage
- 85 of Amazon's 156 unified report dimensions apply to Sponsored Products - The November 2026 count placing ad group language targeting among DVA+-only ad group fields.
- Explaining language targeting - How platforms detect and target language, including OpenRTB device and content fields and Display & Video 360 behaviour.
- Google Ads drops language targeting in September, nine months past deadline - Google's August 2026 announcement removing the campaign-level language setting.
- Amazon DSP advertisers gain a single global account across 34 countries - The account upgrade that let programmatic campaigns span regions.
- Amazon Ads puts 4-step DVA+ campaign builder in US closed beta - The launch of the campaign type the field serves.
- Amazon launches unified reporting system across advertising products - The November 2025 beta launch of unified reporting.
- Amazon Ads unified reporting exits beta - and takes two old tools with it - General availability in June 2026.
- Amazon advertisers will lose unmigrated reports on January 31, 2027 - The legacy report shutdown timeline.
Summary
Who: Advertisers and agencies buying through DVA+ set the language rule on an ad group; Amazon Ads applies it in bidding and returns it in reports.
What: A unified reporting dimension recording the language targeting setting of an ad group, the unit formerly called a line item in Amazon DSP. It describes a delivery rule, not the language of the ad or the content.
When: Unified reporting opened in beta on November 11, 2025 and reached general availability on June 8, 2026; the November 11, 2026 dimensions reference lists the field; legacy reports close on January 31, 2027.
Where: In the ad group attributes of Amazon Ads unified reporting, in the Ads Console and the Reporting API. It returns null for Sponsored Products, Sponsored Brands and Sponsored Display.
Why: Programmatic campaigns reach multilingual audiences that country settings cannot separate. The field lets advertisers measure what each language-restricted ad group delivered and audit the rule against ad language and content language.
Discussion