Newsletter Booking Lead Times: Dupple Data
How far ahead were Dupple newsletter placements booked? For 2026 runs with usable close dates, the median was 24 days for 300 Primary Ad placements and 21 days for 217 Spotlight placements. These are historical observations from Dupple's records, not current availability or a promise that a particular issue can be booked.
Published and updated 5 November 2026. Data read 4 November 2026.
Dupple publishes Techpresso, AIpresso, Devshot, Cyberpresso, Finpresso and MarketingShot, and sells sponsorships in them. Our data comes from Dupple booking records and has not been independently audited.
The data at a glance
The table counts newsletter placements with run dates from 1 January through 3 November 2026. Lead time is the number of days between the deal's recorded close date and the placement's run date. The underlying placement CSV includes quartiles and two additional thresholds.
| Publication and format | Runs | 25th percentile | Median | 75th percentile | At least 14 days ahead |
|---|---|---|---|---|---|
| All newsletters, Primary Ad | 300 | 11 days | 24 days | 44 days | 68% |
| Techpresso, Primary Ad | 229 | 13 days | 27 days | 49 days | 74% |
| Cyberpresso, Primary Ad | 33 | 12 days | 16 days | 35 days | 64% |
| Devshot, Primary Ad | 19 | 10 days | 13 days | 19 days | 42% |
| MarketingShot, Primary Ad | 17 | 7 days | 9 days | 32 days | 41% |
| All newsletters, Spotlight Ad | 217 | 12 days | 21 days | 40 days | 69% |
| Techpresso, Spotlight Ad | 217 | 12 days | 21 days | 40 days | 69% |
| All newsletters, Dedicated Send | 10 | 10 days | 24 days | 31 days | 60% |
The rows overlap: publication rows are subsets of their format totals, and the Spotlight total and Techpresso row describe the same 217 runs. Do not add them together. The full dataset covers 527 placements: 300 Primary Ads, 217 Spotlight Ads and 10 Dedicated Sends. Smaller newsletter and format combinations with fewer than 10 runs were omitted. A percentile describes a position in the observed distribution, not a guaranteed booking deadline.
A second question: when did a campaign start?
A deal can contain several placements. Counting every run is useful for planning the full schedule, but later placements from one deal can make the lead-time distribution longer. To answer a different question, we also selected the first newsletter run of each deal. The first-run CSV contains 146 deals with usable dates: the median first run was 10 days after the recorded close date, with a 25th percentile of 4 days and a 75th percentile of 18 days.
In that 146-deal sample, 40% of first runs were within seven days and 34% were at least 14 days after the recorded close. These are rounded shares of the historical sample. A first run and a placement are different units, so the 10-day first-run median is not a contradiction of the 24-day Primary Ad median. The first-run file does not provide a separate breakdown by newsletter or format.
For a concrete planning example, a team that wants a first message on a fixed date should ask about that specific issue before arranging internal approvals. The 10-day median says half of the observed first-run lead times fell at or below that value under the dataset's calculation; it does not say a newly requested date will be available. If the plan includes several later issues, compare the full run schedule as well as the first date.
How the records were selected
The source is Dupple's Sponsors application, using deal, placement, slot and publication records read on 4 November 2026. The window is based on newsletter run date, from 1 January through 3 November 2026. The included formats are Primary Ad, Spotlight Ad and Dedicated Send. The Sponsors application calls a Primary Ad a Main Ad; the table uses the buyer-facing name.
The close date is when a deal was recorded as won in Sponsors. It is not necessarily the day a contract was signed, a customer first asked for a date or an invoice was paid. A salesperson's recording habits can affect the interval. The run date is the scheduled newsletter placement date recorded for that row. A deal with several placements contributes more than one run to the placement file.
The export excludes placements whose deal has no recorded close date, rows where the run date precedes the recorded close date, and formats outside the three listed above. For example, post-signup lead generation is not a newsletter run in this dataset. Of 842 deals in Sponsors, 355 had no recorded close date; the source notes that many were older or imported records. That count describes missing deal dates in the source, not the number of omitted placements in this 2026 window. Missing records can make the observed sample unrepresentative.
Why the small rows matter
The Dedicated Send total contains 10 runs, the minimum used for a displayed row. A few additional or corrected records could move its quartiles substantially. Devshot and MarketingShot Primary Ad rows contain 19 and 17 runs respectively. These figures are useful historical context, but they should not be presented as precise forecasts for every future campaign.
Finpresso and AIpresso each had only one qualifying Primary Ad run in the source and are therefore not shown as separate rows. The absence of a row does not mean a placement was never sold, that inventory is unavailable or that the lead time was zero. Spotlight had enough qualifying runs only for Techpresso in this export. Ask the team about the exact newsletter and date rather than substituting a different publication's median.
The dataset has no prices, advertiser names or deal values. It does not record why a date was chosen, whether an advertiser changed its plan or how long creative approval took. It also does not show the availability of dates that a buyer considered but did not book. These omissions limit what can be inferred from the observed intervals.
Compare scheduling models, not medians across platforms
Dupple's Primary Ad page describes an in-issue sponsorship and the Dedicated Send page describes a separate advertiser-focused email. Their placement data above uses the same recorded-close-to-run definition, but the 10 Dedicated Send runs are a much smaller group than the Primary Ad sample. Ask about current dates, the creative deadline and any other steps for the intended booking.
Other publishers structure delivery differently. The daily.dev Digest advertising page, checked 5 November 2026, describes sponsorships booked in weekly audience slots while individual readers choose a daily or weekly digest cadence. A weekly slot is not the same unit as one dated Dupple issue. The beehiiv Ad Network guide, checked the same day, describes a marketplace workflow for publishers claiming and inserting available offers. Neither source provides a directly comparable close-to-run distribution for this dataset.
If a proposal involves another publisher or a network, ask whether the date refers to a particular issue, a delivery window or a group of placements. The newsletter buying guide lists questions for a booking, while the Primary Ad guide and Dedicated Send guide explain Dupple's formats. Different workflows should not be compared using one provider's median as though it described the other.
Use the CSV without overstating it
Download the placement file for publication and format rows, and the first-run file for one earliest run per deal. Both are aggregates rather than deal-level exports. The 25th, median and 75th percentile fields are in days; percentages are shares of the corresponding row's qualifying records. The placement file also contains the share booked at least 28 days ahead.
Do not average the publication medians to produce an overall median: each newsletter has a different number of runs, and a median of medians is not the median of all underlying placements. The all-newsletter rows are already calculated from their qualifying runs. Similarly, do not combine the 146 first runs with the 527 placement rows; some refer to the same deal and answer different questions.
These exports are a dated snapshot. A correction to a close date or a later booking can change a future refresh. The audience and lead data page describes other Dupple datasets, which have different populations and collection methods. The sponsorship ROI guide discusses campaign outcomes; booking lead time alone cannot tell an advertiser how a campaign performed.
What we could not verify
The records do not establish contract signature dates, the first inquiry date, rejected or unavailable dates, or creative turnaround. Missing close dates and recording practices can bias the sample; small groups can move sharply. Dupple's records are not independently audited. The external sources do not supply a distribution measured in the same way, and historical booking intervals cannot guarantee current inventory or future campaign results.
FAQ
How far ahead were Primary Ads booked?
For 300 qualifying Primary Ad runs from January through 3 November 2026, the median was 24 days between the recorded close date and the run date.
How soon did a new deal's first newsletter run start?
Among 146 qualifying deals, the median first run was 10 days after the deal was recorded as won. This is a deal-level measure, not the placement median.
Does the median mean a date is available ten days from now?
No. The data describes historical records, not current inventory or a promised deadline. Ask about the specific date and publication.
Why is there no separate AIpresso or Finpresso Primary Ad row?
Each had one qualifying run in the source. Rows with fewer than 10 runs were omitted to avoid presenting a very small group as a stable pattern.
Are the data files a list of customers or prices?
No. The downloadable files contain aggregated counts and timing statistics; they do not contain advertiser names, deal values or prices.