M Motionworks Population Intelligence

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.

1
credit
Profile read per face (owned measurement)
150-300
credits
One-time measurement purchase 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, purchase a measurement with POST /v2/viewcast/measurements/purchase/{type} and read the profile with GET /v2/viewcast/profiles/{display_id} (operationId viewcast_profiles_get).

Primary endpoints

Method URL Credits Status Summary
POST https://api2.mworks.com/v2/set-dynamics/scenarios 25 production Submit a scenario
GET https://api2.mworks.com/v2/set-dynamics/scenarios/{scenario_id} 1 production Read a scenario
GET https://api2.mworks.com/v2/viewcast/profiles/{display_id} 1 production Read a viewshed profile

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

Name In Type Required Description
scenario_id path string Required The scenario's `scenarioId` from the submit or list response.

GET /viewcast/profiles/{display_id} viewcast_profiles_get

Name In Type Required Description
display_id path string Required Motionworks display identifier (`dsp…`), assigned when the asset reached `final_measured`.

Supporting endpoints

MethodURLCreditsSummary
GET https://api2.mworks.com/v2/set-dynamics/scenarios 1 List scenarios
GET https://api2.mworks.com/v2/places 1 List and filter places
GET https://api2.mworks.com/v2/places/{poi_id} 1 Read one place

Underlying data

Recent changes

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