Monitor targets and signal subjects
What a monitor watches, what a signal describes, and independent observations.
A monitor's targets define what it watches. A signal's subject identifies who or what an observation describes. A spending signal can describe a district without requiring a researched account for that district.
Candidate API
The organization owns monitors and signals. Create an independent topic or CSV monitor with POST /v2/monitors. The campaign-nested route remains available. A signal-sheet monitor requires a valid source_campaign_id that supports its record type.
Monitors produce signals only. Importing an account or person and adding campaign membership are explicit actions. Signals expose stable subjects, existing account_ids and person_ids, an optional event_date, and evidence. Campaign provenance is nullable.
District subjects support NCES identifiers and optional Salesforce mappings scoped to the organization. An observation does not add a district to a campaign.
Deleting a source campaign preserves historical signals and monitor configuration. Dependent monitors pause until a valid replacement source is set. Independent topic and custom monitors continue. Explicit monitor deletion remains a separate operation.
These fields and operations are part of the bundled APP-483 candidate. Production activation requires the coordinated ownership migration. The downloaded contract identifies the exact backend source.
Example: two monitors over districts
A web monitor watches the districts selected through a campaign. A separate spending monitor watches a feed that includes other districts.
The spending monitor retains signals for districts outside the web campaign. NCES identifiers and optional Salesforce mappings let integrations join those observations. The web campaign's target selection changes only through an explicit action.