Flight end date is a dimension in Amazon Ads unified reporting that records the last day of a flight: a period inside a programmatic campaign that carries its own budget, start date and end date. It exists because a campaign's money is usually planned in windows rather than as one sum, and each window needs a hard stop. The end date tells the system when a flight's budget must be spent by, and tells anyone reading a report which period a row of spend belongs to.
The field is one of five flight attributes listed in Amazon's unified reporting dimensions reference, updated on November 11, 2026. Its siblings are Flight ID, Flight name, Flight start date and Flight budget. In PPC Land's field-by-field reading of that reference, all five sit in the "Level of detail" category, and none lists a former name. Orders became campaigns and line items became ad groups in the new vocabulary, but flights, and their dates, kept their labels.
Where the date sits
Amazon's programmatic product was called Amazon DSP until it was renamed DVA on September 29, 2026. Its structure runs from advertiser account to campaign to ad group to ad. Flights attach to the campaign. A campaign has an overall date range, and its flights divide that range into segments, each with an amount to spend.
The flight end date is therefore the closing boundary of one segment, not of the campaign. A campaign running from October 1 to December 31 might hold three monthly flights ending on October 31, November 30 and December 31. Only the last of those coincides with the campaign's own end date. Ad groups, which hold targeting, bids and creative, draw on whichever flight is live at the moment of delivery and carry their own start and end dates as well.
Delivery happens only where the campaign, flight and ad group windows overlap.
How the end date works
In the version 1 DSP API, flights are created and edited as a sub-resource of a campaign. According to API documentation republished by the integration company One (last updated February 25, 2026), a POST request to /dsp/v1/campaigns/{campaignId}/flights takes an array of flight objects. Each requires a budgetAmount, a startDateTime and an endDateTime. The two dates are written in RFC 3339 format, the internet standard for timestamps, which means a value such as 2026-12-31T23:59:59Z carries a date, a time of day and a time zone offset. A companion update operation changes existing flights, and that is the route by which an end date is moved.
So the field holds a moment, not merely a calendar day. Reporting tools tend to show it as a date. Funnel, a marketing data company, lists the column as "Flight End Date Time" in its Amazon DSP budget dataset, which refreshes every four hours. Unified reporting presents it as Flight end date. Analysts joining the two should expect a difference in precision, and the public material reviewed for this article does not state which time zone Amazon applies when it truncates the timestamp to a date.
The end date drives pacing. Amazon's launch notice for order-level metrics, published on September 28, 2023, defines budget at risk as "the amount of budget that may remain unspent if the current spending pattern continues through the end of the flight". Delivery rate measures spend against budget and progress "in the current flight". Both depend on knowing how many days remain, and both appear from the second day of a flight, according to Amazon. Move the end date out by a week, and the same spend suddenly looks less behind.
A worked example
A consumer electronics brand plans $60,000 for a holiday push. Its buyer creates two flights in one DVA+ campaign: $15,000 from November 1 to November 23, and $45,000 from November 24 to December 21, so that Black Friday and Cyber Monday fall at the start of the heavier flight.
By November 15, the first flight has spent $8,000 of $15,000 with eight days left. The budget at risk metric flags a shortfall. The buyer has three options inside the flight model: raise bids, widen targeting, or edit the first flight's end date. Extending it to November 26 would push it into the second flight's window, and the two would overlap. Intentwise, an Amazon ads software vendor, wrote in November 2025 that its bulk flight tool rejects such collisions with the message "Flight overlaps with an existing one." Whether Amazon's own console enforces the same rule is not stated in Amazon's public documentation.
In a unified report, a row grouped by Flight ID with Flight start date, Flight end date, Flight budget and spend would show the first flight closing at, say, $13,500 against $15,000. The end date fixes the denominator: it is what makes the $1,500 an underspend rather than money still to come.
Origin and evolution
The flight is a media planning term older than programmatic buying. It describes the period a campaign runs, and flighting describes concentrating spend into bursts with gaps between them, a practice covered in PPC Land's explainer on flights. Ad servers and demand-side platforms built the idea into software as dated budget segments on orders and insertion orders. Campaign Manager 360, Google's ad server, keeps a help page under the title "Flight end date".
Amazon's platform launched as Amazon Advertising Platform and was renamed Amazon DSP in September 2018. Its orders carried flights, though Amazon has not published a date for when the feature appeared. Later launches leaned on flight boundaries. On November 20, 2024, Amazon introduced short-flight recommendations, real-time optimisation suggestions for DSP flights "running seven days or less", aimed at events such as Prime Day and Black Friday.
The DSP campaign management APIs reached general availability on January 9, 2025, exposing endDateTime to developers. Unified reporting opened in beta on November 11, 2025, the same period in which Amazon merged DSP and sponsored ads into a single campaign manager. Unified reporting reached general availability on June 8, 2026, and the November 2026 reference put Flight end date in the shared schema.
Why it matters
For buyers, the end date is a lever as much as a label. Changing it changes daily pacing targets, and the optimiser responds. Amazon's DVA+ guidance states that flights of 14 days or longer give its systems time to learn, which makes the gap between start and end date a performance input, not only a calendar entry. In its Streaming TV guidance, Amazon describes the reach objective as delivering "your flight budget in full", as PPC Land reported when streaming TV budgets were sized as commitment plus up to five fees. "In full" is measured at the end date.
For finance and agency teams, the field defines billing periods. Underspend, reconciliation and month-end reporting are all framed around when a flight stopped.
For data teams, the date matters because of the migration calendar. Amazon makes legacy reports read-only on December 17, 2026 and deletes unmigrated reports and their history on January 31, 2027. Dashboards that filter or join on flight dates from legacy DSP exports need to be remapped before then.
Limitations and disputes
The field exists only where flights exist. Sponsored Products, Sponsored Brands and Sponsored Display campaigns are not built from flights, and Amazon's documentation says a dimension that does not apply to an ad product "appears as null". A null end date in a mixed report does not mean an open-ended campaign. It means the row has no flight.
The behaviour at the end date is under-documented. Whether unspent budget lapses when a flight closes or carries into the next one, how many flights a campaign can hold, and whether a past end date can be reopened are not set out in any Amazon page found for this article. Vendor help centres describe their own rules, which may be stricter than Amazon's. The API details above come from a republished copy, not Amazon's developer portal.
Automation adds a further question. Amazon's DVA+ guide, PPC Land reported, advises against budget caps, warning they "can cause under-delivery by blocking full budget use." Short, back-to-back flights with hard end dates behave like caps by another name, and practitioners who build monthly flights for accounting reasons may be working against the optimiser.
Flight end date versus adjacent terms
Campaign end date is the last day of the whole campaign. A flight's end date falls on or before it, and only the final flight normally shares it. Ad group end date limits when a specific ad group can serve, independent of flights, so an ad group can stop before its flight ends. Flight start date is the opening boundary of the same window; the two together define the flight's length and the denominator for pacing. Date and Date range in unified reporting are time dimensions describing when the activity in a row happened, not when any plan was scheduled to stop.
Recent developments
The November 2026 reference update placed the flight fields beside sponsored ads data in one table for the first time. Amazon's move of agency fees to account, campaign or ad group level after January 31, 2027 does not include flights. DVA+, the AI-led campaign type merging DSP, Sponsored Display and Sponsored TV buying, entered US closed beta in autumn 2026, with budget flighting listed among its advanced settings rather than the default tier. As of November 2026, DVA+ pacing can be daily, weekly, monthly or lifetime. How Flight end date will be populated for campaigns that rely on those modes instead of explicit flights has not been documented.
Timeline
- September 2018: Amazon Advertising Platform renamed Amazon DSP
- September 28, 2023: Amazon launches order-level delivery rate and budget at risk, both measured to the end of the current flight
- November 20, 2024: Amazon introduces short-flight recommendations for DSP flights of seven days or less
- January 9, 2025: DSP campaign and creative management APIs reach general availability
- November 11, 2025: Amazon Ads unified reporting opens in beta
- November 2025: Intentwise describes monthly flight setup and rejects overlapping flight dates in its tool
- February 25, 2026: Republished DSP v1 API documentation lists startDateTime and endDateTime as required flight fields in RFC 3339 format
- June 8, 2026: Unified reporting reaches general availability
- September 29, 2026: Amazon DSP renamed DVA
- November 11, 2026: Amazon updates its unified reporting dimensions reference, listing Flight end date among five flight fields
- December 17, 2026: Legacy Amazon Ads reports become read-only
- January 31, 2027: Unmigrated legacy reports and their history are deleted
Related PPC Land coverage
- 85 of Amazon's 156 unified report dimensions apply to Sponsored Products - Field-by-field reading of the November 2026 dimensions reference, including the five flight fields.
- Amazon launches unified reporting system across advertising products - The November 2025 beta that brought DSP and sponsored ads data into one schema.
- Amazon unifies DSP and sponsored ads in single Campaign Manager platform - The merger behind the order-to-campaign renaming.
- Amazon Ads unified reporting exits beta and takes two old tools with it - General availability in June 2026 and the retirement of legacy tools.
- Amazon advertisers will lose unmigrated reports on January 31, 2027 - The legacy report shutdown timeline.
- Amazon sizes streaming TV budgets as commitment plus up to five fees - Amazon's budget calculator and its "flight budget in full" reach objective.
- Amazon's $78bn ad machine now sets the defaults agencies buy inside - DVA+ budget options and Amazon's warning against budget caps.
- Amazon Ads puts 4-step DVA campaign builder in US closed beta - The DVA+ builder and the advanced settings that include budget flighting.
- Agencies lose Amazon's legacy DVA fee setting after January 31, 2027 - The move of agency fees to account, campaign and ad group level.
- Explaining flight - The media planning concept of a campaign window and the practice of flighting.
Summary
Who. Amazon Ads defines and populates the field. Programmatic buyers, agencies, finance teams and data vendors such as Funnel and Intentwise use it to judge pacing and close out budget periods.
What. The closing date and time of a flight, a dated budget period inside an Amazon programmatic campaign, exposed as a dimension in unified reporting alongside Flight ID, Flight name, Flight start date and Flight budget.
When. Flights have existed in Amazon DSP for years without a published launch date. The endDateTime field appears in the DSP v1 API, and Flight end date is listed in the dimensions reference updated on November 11, 2026, ahead of the January 31, 2027 legacy report deletion.
Where. In Amazon Ads unified reports in the console and Reporting API, and in the DSP API under /dsp/v1/campaigns/{campaignId}/flights. Sponsored ads rows return null.
Why. Budgets are planned in windows, and every pacing metric needs to know when a window closes. The end date sets that boundary, fixing what counts as underspend and which period each row of delivery belongs to.
Discussion