Automated ART19 Campaign Pacing Checks
Every morning, WebRun opens ART19, reads each insertion order and its line items, compares booked impressions against delivered against the days left in the flight, raises a Trello card for every line item behind pace, and posts the shortfall list to WhatsApp before the day starts.
How do I catch a podcast ad campaign that is behind pace?
WebRun checks your ART19 insertion orders every morning, comparing booked impressions against delivered for each line item and the days left in its flight. It raises a Trello card for anything behind pace and posts the shortfalls to WhatsApp, so ad ops moves inventory instead of explaining a miss later.
- Behind-pace line items surface while there are still days to fix them
- Every shortfall carries its projected miss and flight end date
- Cards close themselves once a line item catches back up
Built for podcast ad operations · media sellers · podcast networks · sales planners
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
art19.comin a real browser with your saved login - no setup, no API keys. -
1
ART19 - compare booked to delivered
art19.com
WebRun opens ART19 to compare booked to delivered. - Open ART19 and list the insertion orders currently in flight
- Read each line item: the booked impressions, the impressions delivered so far, and the flight dates
- Work out the share of the flight elapsed and compare it against the share of impressions delivered
- Flag any line item delivering behind that pace, and note the shows it is running on
- Record the days left in each flight, since a small gap late is worse than a large gap early
Done when Every in-flight line item has a pace figure and the behind-pace ones are listed with days remaining.
-
2
Trello - raise a card per shortfall
trello.com
WebRun opens Trello to raise a card per shortfall. - Open your ad operations board in Trello and create a card per behind-pace line item
- Put the advertiser, the line item, the booked and delivered impressions, and the flight end date on the card
- Sort cards by days remaining, so the flights closest to ending sit at the top
- Close the card automatically on a later run once the line item catches back up to pace
Done when Trello holds one live card per behind-pace line item, sorted by days remaining.
-
3
WhatsApp - post the pacing list
whatsapp.com
WebRun opens WhatsApp to post the pacing list. - Post a short WhatsApp list of the line items behind pace this morning, worst first
- Show the projected shortfall on each if nothing changes before the flight ends
- Flag anything with under a week left, since those need inventory moved today
- Leave every inventory change and every advertiser conversation to your team
Done when You have today's pacing list in WhatsApp with the projected shortfalls.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it change campaign settings or move inventory?
No. WebRun reads pacing in ART19 and reports it. Reallocating inventory, adjusting a line item, or talking to the advertiser stays with your ad operations team.
Does it contact advertisers?
No. Nothing leaves your team. The Trello cards and the WhatsApp list are internal, so a shortfall reaches your ad ops lead and never the client without a person sending it.
How is behind pace calculated?
It compares the share of the flight that has elapsed against the share of booked impressions delivered. A line item halfway through its flight with a third of its impressions delivered is behind.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.