M Motionworks Population Intelligence
  • Pricing

Plan an OOH campaign before it goes live

Estimate exposure, audience reach, and traffic for a proposed spot set before money is committed. Set Dynamics handles forward-looking scenarios with the same payload shape as delivered measurement; Pathcast provides hourly traffic context on the roads feeding each face.

Try in console Open API reference View methodology
25
credits
Scenario submission
100
credits
Per Pathcast traffic call
0
credits
Markets & segments reference
1 hour
p95
Scenario turnaround

Forecasts run on Pathcast historical traffic patterns at every unit in your plan plus Set Dynamics historical reach and frequency curves for the unit set. The forecast applies seasonality and day-of-week adjustments. Every forecasted metric carries a confidence interval derived from the historical sample size.

PATHCASTDATAHistorical traffic patternsper unit, by hour of weekSET DYNAMICSDATAHistorical R+F curvesper unit set, per audienceSET DYNAMICS FORECASTAPPLICATIONProject · Calibrate · Scorepre-flight R+F with confidence intervals

Every forecast carries a provenance block plus a confidence_interval block with lower and upper bounds at 95 percent. Confidence narrows as the historical sample for the plan units grows.

What you get

  • Forward-looking Set Dynamics scenario: projected reach and frequency for a proposed spot set, cohort, and period.
  • Hourly traffic history and current measurements on the linear paths feeding each face.
  • Viewshed polygons and per-face path lists for any face under consideration.

When to use this Job

  • You are building an RFP response and need projected delivery for a proposed spot set.
  • You are evaluating swap candidates between similarly-priced faces in a market.
  • You need historical traffic context to size the audience opportunity for a new market.

How it works

  1. 1 Submit a scenario via POST /set-dynamics/scenarios with measurement_type: projected and a future period.
  2. 2 For each face under consideration, list its viewshed (GET /pathcast/faces/{place_id}/viewshed) and paths (GET /pathcast/faces/{place_id}/paths).
  3. 3 Pull recent and historical traffic on each path with GET /pathcast/paths/{path_id}/traffic and /history.

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/pathcast/paths/{path_id}/traffic 100 production Hourly vehicle + pedestrian traffic for a path
GET https://api.mworks.com/v2/pathcast/paths/{path_id}/history 100 production Historical traffic for a path across a date range

GET /pathcast/paths/{path_id}/traffic getPathTraffic

Name In Type Required Description
path_id path string Required
year query integer Optional
month query integer Optional
day_type query integer Optional
hour query integer Optional

GET /pathcast/paths/{path_id}/history getPathHistory

Name In Type Required Description
path_id path string Required
start_date query string · date Optional
end_date query string · date Optional

Supporting endpoints

MethodURLCreditsSummary
GET https://api.mworks.com/v2/pathcast/faces/{place_id}/paths 100 List all paths for a face (viewshed)
GET https://api.mworks.com/v2/pathcast/faces/{place_id}/viewshed 100 Get the viewshed polygon + display metadata for a face
GET https://api.mworks.com/v2/markets 1 List all DMA markets
GET https://api.mworks.com/v2/segments 1 List audience segments

Underlying data

Platform (markets, segments)

Recent changes

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