Ad group comments is a dimension in Amazon Ads unified reporting that returns whatever free-text note a buyer has attached to an ad group. It carries no performance data and Amazon does not generate it. The value is typed by a trader, an agency planner or an automated tool, usually to record something the platform's structured settings cannot hold: why an ad group exists, which brief or client request it answers, who approved a change, or what a test is meant to prove. The field exists because campaign settings describe what a buy does, not why. Comments carry the why, and unified reporting lets that note travel into the same export as spend and impressions.

The field sits among the ad group attributes of Amazon's unified reporting dimensions reference, which Amazon updated on November 11, 2026. According to PPC Land's field-by-field reading of that reference, published the next day, Ad group comments applies to DVA+ only, alongside ad group type, ad group external ID, ad group budget amount and ad group language targeting. DVA+ is the campaign type that combines buying across the programmatic platform sold as Amazon DSP until September 29, 2026, Sponsored Display and Sponsored TV. Rows from Sponsored Products, Sponsored Brands and Sponsored Display leave the column empty.

Where the field comes from

Unified reporting rewrote Amazon's programmatic vocabulary into the sponsored ads one. A DSP order became a campaign, and a line item, the unit that holds flight dates, budget, bids, audiences, supply and creatives, became an ad group. PPC Land summarised the mapping in one sentence: "A line item is an ad group, and a creative is an ad." Its reading lists "Line item ID" and "Line item name" as the former names of Ad group ID and Ad group name.

Ad group comments, in practice, is therefore the comments field of what programmatic traders still call a line item. The reference does not give it a former name, according to PPC Land, which found that 100 of the 156 dimensions do carry one. Whether legacy DSP reports exported line item comments under another column heading could not be confirmed for this article.

The structured precedent is in Amazon's programmatic API. Documentation of the DSP v1 ad group endpoint (PATCH /dsp/v1/adGroups), as reproduced by integration vendor withone.ai in an update dated February 25, 2026, lists an optional string called comments, described simply as "Ad group comments". It sits next to an optional purchaseOrderNumber, described as "Purchase order number (externalId)". For both, the documentation states that setting the value to an empty string clears it. Amazon's own API reference was not reachable for this article, so the schema rests on that third-party reproduction.

How the value gets there

A buyer writes the note when creating or editing an ad group. The Amazon Ads API is the documented route; whether the DVA+ campaign builder in the Ads Console and bulk editing expose the same field is not stated in Amazon's published material. No maximum length is stated for the ad group comments string in the reproduced schema, a contrast with the creative object's externalId, which the same documentation caps at 255 characters.

Nothing validates the content. The field accepts any text, there is no controlled list of values, and Amazon attaches no meaning to it in delivery. It does not change bids, pacing, targeting or eligibility. Its only effect is that it appears wherever ad group attributes are displayed or exported.

That sets the column apart. Ad group delivery status reports a state the platform calculates; Ad group budget amount a number it enforces. Ad group comments reports a sentence a person wrote.

How it sits in a report

Unified reporting lets a user add dimensions to a report in the Ads Console or request them through the Reporting API, then break metrics down by those attributes. Comments is a descriptive attribute of the ad group, so every row for a given ad group repeats the same text, whatever the date, placement or device split. A report grouped by Ad group ID with comments added shows one note per ad group. A daily report shows the same note on each day.

One consequence is that the column reports the comment as it stands, not as it stood. If a trader edits the note on November 15, there is no indication in Amazon's published material that a report covering November 1 to 14 would show the earlier text. Amazon's documentation does not say whether descriptive ad group attributes are stored historically or read from the current setting.

The field is also one of 14 ad group attributes in the reference. Four of them are free-text or imported references that serve different owners: Ad group name and Ad group comments, written by the buyer for people; Ad group external ID, written by the buyer for systems; and Ad group OMS ID, which PPC Land describes as "imported from Amazon's order management system (OMS)".

A worked example

Consider an agency running a fourth-quarter DVA+ campaign for a home appliance brand. The campaign has four ad groups: two streaming TV ad groups, one open display retargeting ad group and one audio ad group. The trader names them by a house convention, such as "Q4_STV_Sports_PG", and enters the client's purchase order number in the external ID field.

The comments carry what the naming scheme cannot. The guaranteed streaming ad group gets "Booked against Nov 3 IO amendment, client approved CPM increase by email Oct 28". The retargeting ad group gets "Frequency raised to 4/week on Nov 10 per client brief v3". The audio ad group gets "Test cell - pause if no lift read by Dec 5".

When the agency's analyst pulls a unified report by Ad group ID, Ad group name and Ad group comments, those notes sit next to spend, impressions and conversions. A planner or a new trader can read the context without searching email. A Sponsored Products campaign added to the same report shows blank comment cells, because the field does not apply there.

Why it matters

The value of comments is administrative. Agencies rotate staff, clients audit spend, and finance teams ask why a buy changed. In traditional media, that record lived on insertion orders and in trafficking notes. In programmatic platforms, it tends to scatter across email, chat and spreadsheets. A comments field kept inside the platform, and exportable with the delivery data, puts the audit trail on the same row as the money.

The timing raises the practical stakes. Under the schedule PPC Land reported on November 12, 2026, creation and editing of legacy Amazon reports stop on December 17, 2026, and unmigrated reports and their history are deleted on January 31, 2027. Any warehouse table or dashboard that carried line item notes from a legacy DSP export has to be remapped to the unified field before then. Agency billing is moving down the hierarchy at the same time: after January 31, 2027, manager-account fees can be applied at account, campaign or ad group level, which gives ad group-level context more weight in client reconciliations.

Limitations and open questions

Coverage is the first limit. Ad group comments is one of 59 fields that, according to PPC Land, serve DVA+ alone. An advertiser running sponsored ads and DVA+ together cannot use it as a common annotation layer across products. DVA+ itself remains in US closed beta, so few ad groups can yet carry the field in unified reporting.

Data quality is the second. Free text has no schema, so a comments column cannot be filtered reliably, aggregated or joined to other data without cleaning. Two traders describing the same event will write it differently. An empty cell may mean nothing happened, or that nobody recorded it.

Confidentiality is the third. Notes written for internal use can end up in exports shared with clients, partners or reporting vendors. Amazon's published material does not describe any permission control specific to the comments field.

History is the fourth. As noted above, Amazon has not documented whether the report shows the current note or the note in force on each date, which matters for audits.

Ad group comments is not...

Ad group name. Also free text written by the buyer, but it is a label, it is required, and it appears everywhere the ad group appears. Naming conventions often encode structure. Comments carry context that does not fit a label.

Ad group external ID. A buyer-supplied reference meant for other systems, which the reproduced API schema ties to the ad group's purchase order number. It is a key; comments are prose.

Campaign PO number. An optional purchase order reference at campaign level, according to PPC Land. It records an authorisation, not an explanation.

Ad comments on social platforms. On Meta, TikTok or YouTube, "comments" usually means public replies from users under an ad, counted as an engagement metric. Ad group comments is an internal attribute never shown to consumers.

Recent developments

On November 11, 2026, Amazon updated the unified reporting dimensions reference listing Ad group comments among 156 attributes, and PPC Land's analysis on November 12 placed it among the DVA+-only ad group fields. The same week, Amazon set December 17, 2026 as the date legacy reports become read-only, ahead of their deletion on January 31, 2027. Unified reporting itself reached general availability in June 2026, seven months after its November 2025 beta launch. As of November 2026, Amazon has published no description, length limit or history rule for the comments column beyond its name and product applicability.

Timeline

  • September 2018 - Amazon Advertising Platform renamed Amazon DSP; buys organised as orders and line items.
  • January 9, 2025 - Amazon DSP campaign and creative management APIs reach general availability, covering campaigns, ad groups, targets and creatives.
  • November 11, 2025 - Amazon Ads unified reporting opens in beta.
  • February 25, 2026 - Third-party reproduction of the DSP v1 ad group schema shows an optional "comments" string, cleared by an empty value.
  • June 2026 - Unified reporting reaches general availability in the Ads Console.
  • September 29, 2026 - Amazon DSP name retired in favour of DVA; DVA+ enters US closed beta.
  • November 11, 2026 - Dimensions reference lists Ad group comments as a DVA+-only field.
  • December 17, 2026 - Legacy report creation and editing scheduled to stop.
  • January 31, 2027 - Legacy report pages and unmigrated report data scheduled for deletion; legacy DVA campaign-level agency fee setting ends.

Summary

Who: Traders, agencies and advertisers buying through DVA+ write the notes; Amazon Ads defines the field and returns it in reports. Analysts, account handovers and client audits consume it.

What: A unified reporting dimension that returns the free-text comment attached to an ad group, the unit formerly called a line item in Amazon DSP. It has no effect on delivery.

When: The comments string appears in Amazon's DSP v1 ad group API as reproduced in February 2026. The November 11, 2026 dimensions reference lists the field, and 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 is empty for Sponsored Products, Sponsored Brands and Sponsored Display rows.

Why: Settings record what a buy does but not why. A note stored on the ad group and exported with delivery data keeps that context on the same row as the spend.