LO-FI WIREFRAME · not final UI
▣ aumik dooh · pulse News Architecture Sign in / Sign up ›

aumik Pulse — DOOH & programmatic OOH, decoded

The newsroom for the out-of-home ad market — for the screen owners who supply inventory (SSP) and the brands that buy it (DSP). Read the news, join the platform.

Programmatic
Programmatic OOH spend crosses 40% of digital OOH as SSP–DSP pipes mature
Standardised deal IDs and faster players are pulling more open-exchange budget into roadside and retail screens. Read ›
Pulse Desk · 2h ago · source: AdExchanger
Browse: ProgrammaticSupply · SSPDemand · DSPTechMeasurementRegulation

Latest

Why this is here

For screen owners · SSP

Own screens? Pulse is how you learn the programmatic playbook — then list your inventory on aumik dooh and start earning fill on dayparts you're not selling.

For advertisers · DSP

Buy media? Track where DOOH supply is opening up — then buy it programmatically through the aumik dooh demand side, with deal IDs and measurement built in.

Get Pulse weekly

One email a week: the moves that matter for supply & demand. No spam.

Latest

Everything across DOOH & programmatic OOH — supply, demand, tech & rules

Subscribe
ProgrammaticProgrammatic OOH spend crosses 40% of digital OOH as SSP–DSP pipes matureAdExchanger · 2h ProgrammaticOpenRTB 2.6 brings native DOOH deal IDs to more exchangesAdExchanger · 2h Supply · SSPScreen owners are bundling dayparts into programmatic packagesDOOH Today · 5h Demand · DSPWhy retail-media DSPs are adding store-front screensDigiday · 1d MeasurementAudience panels vs. impression multipliers: the DOOH metric fightMediaPost · 1d TechEdge players cut sync latency under 2s on cheap Android TV sticksPulse Desk · 2d RegulationNew municipal rules reshape roadside digital billboard hoursLocal Gov Wire · 3d

Stories are ingested, de-duped and classified automatically — see how Pulse pulls the news ›

Programmatic OOH spend crosses 40% of digital OOH as SSP–DSP pipes mature

Programmatic   By Pulse Desk · 2h ago · source: AdExchanger › (summarised & classified automatically; edited by the Pulse desk)

Standardised deal IDs, OpenRTB 2.6 support and a new wave of low-latency players are pulling more open-exchange budget onto roadside, transit and retail screens, according to figures shared this week.

For screen owners (the supply side, SSP), the shift means previously unsold dayparts can be packaged and offered programmatically — turning idle inventory into fill. For advertisers (the demand side, DSP), deal IDs plus emerging measurement make DOOH buyable in the same workflow as the rest of their digital plan.

The bottleneck is no longer the pipe but the player and the data: screens need to render the right creative on time and report back impressions a buyer will trust.

Why it matters

aumik dooh sits on both sides of this pipe — the player & SSP portal for owners and the demand side for buyers. Pulse is the front door.

Comments · 3

R
Ravi M. · screen owner, 40 mall displays · 1h ago
We started listing dayparts as deals last quarter — fill on our 2–5pm slot went from nothing to ~30%. The packaging is the unlock.
P
Priya S. · programmatic buyer · 48m ago
Agreed on supply, but I won't shift real budget until measurement is consistent. Impression multipliers vary wildly by vendor.
Pulse Desk · author · 30m ago
@Priya — measurement is our next deep-dive. The panels-vs-multipliers piece in Latest covers where the standards are heading.

Join the conversation

🔒 Sign up or log in to comment — it's how we know if you're supply or demand. Sign up to comment

‹ Back to Latest

Join aumik Pulse

Read, comment, and get matched to the platform — as supply or demand.

I'm a…
Create account & comment

— or —

G  Continue with Google

Screen-owner & advertiser sign-ups continue into the aumik dooh portal onboarding. Already have an account? Log in.

How Pulse pulls the news

An automated newsroom: Mastra orchestrates ingest → curate → review → publish on a schedule. n8n is the fallback for any step Mastra can't run.

Pipeline

① SourcesRSS feeds · news APIs · press releases · regulator / muni sites · X & LinkedIn lists
② Mastra workflowfetch → dedupe → summarise → classify (category + SSP/DSP relevance) → draft
③ Editorial reviewhuman approve / edit drafts in the desk queue
④ Publish to Pulsefeed · article pages · weekly newsletter
Runs on a schedule (ingest every ~30 min; weekly digest job). Nothing publishes without an editor's approval in step ③.

② Inside the Mastra workflow

1fetch — pull new items from each source (tools per source type)
2dedupe — agent clusters the same story across outlets
3summarise — LLM writes a neutral dek + key points, with source attribution
4classify — tag category + whether it's supply (SSP) or demand (DSP) relevant
5draft — write to the review queue as pending

Why Mastra (n8n fallback)

The LLM-heavy steps — dedupe clustering, summarisation, classification — are Mastra agents/workflows (TypeScript, lives in aumik-agents). If a connector or trigger is awkward in Mastra (a niche scrape, a scheduler quirk), n8n handles that leg and hands the payload back to Mastra over a webhook. See Sources & schedule ›.
draft = {
  title, dek, body, keyPoints[],
  sourceUrl, sourceName, publishedAt,
  category, audience: "ssp"|"dsp"|"both",
  status: "pending"
}

Sources & schedule

What Pulse ingests, how often, and which Mastra tool/agent handles it

SourceTypeCadenceMastra tool / agent
Industry RSS (DOOH Today, AdExchanger OOH, Digiday)RSSevery 30 minfetchFeed tool
News APIs (NewsAPI / GDELT, OOH keywords)APIhourlynewsApi tool
Press releases (PRNewswire / Business Wire OOH)RSS / scrapehourlyscrape tool
Regulator & municipal sites (billboard rules)scrapedailyscrape tool (n8n fallback)
Social (X lists, LinkedIn OOH voices)APIevery 2hsocialFetch tool (n8n fallback)

Mastra vs n8n — the split

Mastra owns orchestration + every LLM step (dedupe, summarise, classify) and the simple HTTP/RSS fetchers. n8n is only pulled in where Mastra lacks a clean connector or a cron/webhook trigger is simpler there — it fetches, then POSTs the raw payload to the Mastra workflow's ingest endpoint. One source of truth (the Mastra workflow); n8n is an adapter, not a parallel pipeline.

‹ Back to pipeline