Campaign PO number is a dimension in Amazon Ads unified reporting that carries a purchase order (PO) number attached to a campaign. A purchase order is the document a company's finance department raises to authorise spending before it happens, and its number is the reference that department expects to see again when the bill arrives. Amazon does not generate the value. A buyer types it in, usually an agency on behalf of a client or a brand's own media team, so that every row of spend in a report can be traced to the internal approval that paid for it. The field exists because Amazon's identifiers mean nothing to an accounts payable system, and a client's PO number means nothing to Amazon's.
The field sits among the campaign attributes of the unified reporting dimensions reference, which Amazon updated on November 11, 2026. PPC Land's field-by-field reading of that reference, published the next day, describes it in one word: "optional". The reference gives no former name for it, although 100 of its 156 dimensions do carry one, and PPC Land's reading does not attach a product marker to it. Which of Amazon's five ad products populate the field is therefore not stated in public sources as of November 2026.
What a purchase order does
In corporate procurement, the PO comes before the money. A marketing team agrees a budget with a vendor, the finance function issues a PO for that amount, and the vendor's invoice must later quote the PO number to be paid. Many accounts payable departments run a three-way match of PO, delivery record and invoice before paying, so an invoice without a recognisable PO number can sit unpaid.
Advertising adds a layer. Agencies typically sign an insertion order (IO) with the media seller, which sets out what is bought, at what price and over which dates, while the client issues its PO to the agency, or directly to the platform when it pays the bills itself. The two documents describe the same money from different sides. The IO is the seller's contract; the PO is the buyer's internal authorisation.
Other platforms build the PO into billing rather than reporting. Google's Search Ads 360 help centre defines a PO number as "a unique number assigned to an invoice" and states that users with admin and billing permission "can assign a purchase order number to each transaction that generates an invoice". Changes "apply immediately and will appear on that specific month's invoice", where the number is printed "after all line items".
Amazon's approach, as visible in unified reporting, puts the reference on the campaign instead.
How the value gets into a report
The field is free text entered at campaign level, in the console or through the Amazon Ads application programming interface (API). If nobody enters anything, the report shows nothing. Amazon's own API reference could not be read for this article, but third-party reproductions of its schema show how the programmatic side has handled PO numbers. Integration vendor withone.ai's copy of the DSP v1 ad group endpoint (PATCH /dsp/v1/adGroups), updated in February 2026, lists an optional string called purchaseOrderNumber, described as "Purchase order number (externalId)". In other words, on the unit formerly called a line item, the PO number and the "external ID" have been one value.
The campaign level has its own lineage. Unified reporting renamed Amazon's programmatic objects to match sponsored ads: what DSP reports called an order became a campaign, and a line item became an ad group. Funnel, a marketing data company, documents an "Order External ID" dimension in three legacy Amazon DSP report types: campaign, inventory and product. By analogy with the ad group, where the external ID is documented as the purchase order number, Campaign PO number looks like the order-level equivalent carried into the new vocabulary. Amazon has not confirmed that mapping. The reference gives the field no former name, so the connection is an inference from the object model, not a statement in Amazon's text.
Like any descriptive attribute, the value repeats on every row of the campaign. If a buyer replaces one PO number mid-flight, no public documentation says whether historical rows keep the old value.
How Amazon bills, and where the PO fits
Amazon's invoices are not built around POs in its public documentation. For its programmatic platform, Amazon introduced a billing dashboard on December 15, 2020, for self-service advertisers. "Previously, billing details were available in PDF invoices that were emailed," the announcement said. On December 16, 2024, Amazon put invoices for sponsored ads and DSP in a single billing centre, where advertisers "can access a single page to view and download worldwide invoices, both individually and in bulk", according to Amazon. None of the three announcements mentions purchase order numbers.
Adbrew, an Amazon advertising software company, describes the structure of a DSP invoice in its help centre. According to Adbrew, Amazon issues one consolidated invoice per month covering every campaign that delivered in that period, rather than one invoice per order. Campaigns appear by name and number, each with lines for supply cost, platform fee and audience fee. Standard terms are "Net 30 from the invoice date, unless your agreement states otherwise". Adbrew's description does not include a PO field on the invoice.
That gap is what the reporting field fills. When one monthly invoice covers 20 campaigns funded by four POs, a report carrying spend and Campaign PO number can split the total by PO.
A worked example
A home appliance brand approves three POs for the fourth quarter: PO-88120 for streaming TV, PO-88121 for display retargeting and PO-88122 for a holiday sponsored ads push. Its agency runs five Amazon campaigns, entering the relevant number on each.
In early December, Amazon's November invoice arrives as a single total. The agency pulls a unified report at monthly grain, grouped by Campaign PO number, and gets three rows of spend that sum to the invoice, less tax and adjustments. The client's finance team can book each against its PO without a lookup table. If a trader renames "Q4 STV" to "Q4 STV - holiday", the PO number keeps the link, because it did not change. If one campaign was left blank, its spend lands in an empty PO row; if the field does not populate for sponsored ads, the third PO cannot be reconciled this way at all.
Why it matters
For agencies, invoice reconciliation is a monthly chore with real consequences: late payment, disputed fees and clients refusing an unrecognised reference. A PO dimension in Amazon's own reporting moves the key out of campaign names and side spreadsheets.
The timing makes the field harder to ignore. Under the schedule Amazon published on November 12, 2026, legacy report creation and editing stop on December 17, 2026, and unmigrated reports and their history are deleted on January 31, 2027. Any finance export keyed to legacy DSP order columns, including Order External ID, must be rebuilt on unified dimensions before then.
Billing structures are shifting at the same time. Amazon's legacy campaign-level agency fee for DVA can be set until January 31, 2027, after which manager-account fees applied at account, campaign or ad group level take over. PPC Land also reported on November 14, 2026 that under DVA+, the AI-driven campaign type that merges programmatic buying with Sponsored Display and Sponsored TV, managed clients pay a percentage fee invoiced separately.
Limitations and open questions
Scope is the first unknown. Amazon's reference, as read by PPC Land, does not state which ad products support the field. The API evidence for PO numbers comes from the programmatic side, which suggests DVA+, but sponsored ads campaigns may or may not carry it.
Validation is the second. The field is free text with no documented format or length limit; typos reach the report unchanged, and nothing stops two campaigns sharing a number.
Granularity is the third. A single campaign can be funded by more than one PO, for example when a fiscal quarter ends mid-flight. One campaign-level value cannot express that split; the ad group-level purchase order field, or separate campaigns, would be needed.
Overlap is the fourth. If Ad group external ID also holds a PO number, the reference contains two PO-like fields at different levels with no documented rule for which wins when they disagree.
Visibility on the invoice is the fifth. No public Amazon page says whether the campaign PO number is printed on Amazon's invoices. Without that, it supports reconciliation after the fact, not a PO on the bill as in Search Ads 360.
Campaign PO number is not...
Insertion order ID. A reference to "a contractual agreement between an advertiser and Amazon Ads", according to the reference as quoted by PPC Land. It identifies the seller-side contract. The PO number identifies the buyer's internal authorisation.
Campaign OMS proposal ID. A number "imported from Amazon's order management system (OMS)", tied to how managed DVA+ buys are sold. It originates in Amazon's sales process, not the buyer's finance system.
Ad group external ID. The ad group-level reference, which API documentation reproduced by third parties ties to an ad group purchase order number. It labels a single ad group, not the whole campaign.
Campaign ID. Amazon's own system identifier, unique and assigned automatically. The PO number is assigned by the buyer and need not be unique.
Recent developments
The field reached its current definition in the November 11, 2026 dimensions reference, which PPC Land analysed the next day, noting that 59 of 156 dimensions serve DVA+ alone and that 100 carry former names. In the same week Amazon confirmed December 17, 2026 as the date legacy reports become read-only. DVA+ itself remains in US closed beta, with general availability in 35 markets planned for the first quarter of 2027, so the volume of campaigns where a PO number will matter most is still growing.
Timeline
- September 2018 - Amazon Advertising Platform renamed Amazon DSP; buys organised as orders and line items.
- December 15, 2020 - Billing dashboard launches in Amazon DSP for self-service advertisers, replacing emailed PDF invoices as the main view.
- January 12, 2024 - Global consolidated invoice statement download for sponsored ads.
- December 16, 2024 - Single billing centre for sponsored ads and Amazon DSP invoices worldwide.
- January 9, 2025 - Amazon DSP campaign management APIs reach general availability.
- November 11, 2025 - Amazon Ads unified reporting opens in beta.
- February 2026 - Third-party reproductions of the DSP v1 ad group schema show purchaseOrderNumber described as the externalId.
- June 8, 2026 - Unified reporting reaches general availability.
- September 29, 2026 - Amazon DSP renamed DVA; DVA+ enters US closed beta.
- November 11, 2026 - Dimensions reference lists Campaign PO number as an optional campaign attribute.
- December 17, 2026 - Legacy report creation and editing scheduled to stop.
- January 31, 2027 - Unmigrated legacy reports scheduled for deletion; legacy DVA campaign-level agency fee setting ends.
Related PPC Land coverage
- 85 of Amazon's 156 unified report dimensions apply to Sponsored Products - The November 2026 field-by-field reading that lists Campaign PO number as optional.
- Amazon advertisers will lose unmigrated reports on January 31, 2027 - The legacy reporting shutdown timeline.
- Agencies lose Amazon's legacy DVA fee setting after January 31, 2027 - The move to manager-account fees at account, campaign or ad group level.
- Amazon launches centralized billing system for sponsored ads and DSP - The December 2024 single billing centre for worldwide invoices.
- Amazon's $78bn ad machine now sets the defaults agencies buy inside - The DVA+ guide, including the separately invoiced managed-service fee.
- Explaining insertion order - The seller-side contract that a PO mirrors on the buyer's side.
- Explaining master services agreement - The umbrella contract above individual orders.
Summary
Who: Agencies and advertisers enter the value; Amazon Ads defines the field and returns it in unified reports. Finance and accounts payable teams use it to match spend to approvals.
What: An optional campaign-level reporting dimension holding a buyer-supplied purchase order number, distinct from Amazon's Campaign ID, the insertion order ID and the OMS proposal ID.
When: Listed in the unified reporting dimensions reference updated on November 11, 2026, with legacy reports closing between December 17, 2026 and January 31, 2027.
Where: In the campaign attributes of Amazon Ads unified reporting, in the Ads Console and through the API. Which ad products populate it is not stated publicly.
Why: Amazon invoices monthly across many campaigns, while clients approve spend by PO. A PO number on each campaign lets one invoice be split and booked against the approvals that funded it.
Discussion