Measure a campaign that is already in flight

Submit a Set Dynamics scenario for a delivered campaign window, get back the reach and frequency distribution audited to Geopath measurement-currency standards. Use Viewcast Profiles to inspect any face's circulation, OTS, and LTS directly.

300
credits
Viewcast Profile (per face)
25
credits
Set Dynamics scenario submission
Geopath
audit
Currency aligned
1 hour
p95
Scenario turnaround

Set Dynamics is a campaign-level application built on two data products. Viewcast supplies as-delivered circulation and exposure metrics for every unit in your spot list. Placecast supplies the audience composition seen at each unit during the flight window. Set Dynamics fuses the two, deduplicates across format and overlap, and returns campaign-level reach and frequency.

VIEWCAST DATA Circulation, OTS, LTS per unit, per flight day PLACECAST DATA Audience composition at each unit, during flight SET DYNAMICS APPLICATION Fuse · Dedupe · Aggregate campaign-level R+F with provenance

Every response carries a provenance block with the source product, the active model version, a confidence score, and the sample size that produced the measurement. No black boxes.

What you get

  • Set Dynamics scenario results: reach, frequency, impressions, OTS, LTS aggregated across the spot set.
  • Per-face Viewcast Profile: circulation, OTS, LTS at effective-frequency thresholds.
  • Provenance envelope on every response — source, model_version, confidence, sample_size.

When to use this Job

  • You are auditing delivered OOH performance for a flight that ran in the past.
  • You need a Geopath-aligned measurement currency for an agency or media-buyer report.
  • You are comparing planned vs. delivered impressions on a specific spot set.

How it works

  1. 1 Submit a scenario via POST /set-dynamics/scenarios with measurement_type: delivered, a spot set, a delivered period, and a cohort.
  2. 2 Poll the scenario with GET /set-dynamics/scenarios/{scenario_id} until status moves from processing to complete.
  3. 3 For face-level detail, call GET /profiles/{place_id} against any face referenced in the scenario.

Primary endpoints

Method URL Credits Status Summary
POST https://api.mworks.com/v2/set-dynamics/scenarios 25 production Submit a new Set Dynamics scenario for analysis
GET https://api.mworks.com/v2/set-dynamics/scenarios/{scenario_id} 1 production Retrieve a Set Dynamics scenario (polling endpoint)
GET https://api.mworks.com/v2/profiles/{place_id} 300 production Get a single Viewcast profile (face + spot measurements)

GET /set-dynamics/scenarios/{scenario_id} getSetDynamicsScenario

Name In Type Required Description
scenario_id path string Required

GET /profiles/{place_id} getViewcastProfile

Name In Type Required Description
place_id path integer Required
fields query string Optional Comma-separated field names to project.
include query string Optional Additional data: geopath, demographics, history

Supporting endpoints

MethodURLCreditsSummary
GET https://api.mworks.com/v2/set-dynamics/scenarios 1 List Set Dynamics scenarios
GET https://api.mworks.com/v2/places 1 Search places by type / geography / parent / focus status
GET https://api.mworks.com/v2/places/{place_id} 1 Get a single place by ID

Underlying data

Recent changes

  • — Jobs-organized IA pilot. Endpoint tables now generated from OpenAPI specs (api-mworks-com@d211f84).