Access modes & geometry
plannedThe AccessMode determines whether a verification script receives a reference to the creative element: in full mode the OM Service supplies slotElement / videoElement in the context, while limited mode supplies geometry data only; domain mode was removed in 1.5.4 and falls back to limited when selected. The geometryChange event carries adView / viewport / obstructions, and the Reason enum explains why a measurement is not possible.
What this page will cover
- Semantics and fallback rules of the full / limited / domain (deprecated) access modes
- The three-part structure of the geometryChange payload
- Reason values and obstruction causes
- The native-side registration API for friendly obstructions
Source material
| Source | File / path | commit | Fetched | Integration status |
|---|---|---|---|---|
| InteractiveAdvertisingBureau/Open-Measurement-JSClients | src/common/constants.js | b6f12bd | 2026-09-22 | integratedThe AccessMode / Reason / NativeViewKeys enums are integrated into spec.json |
| docs.iabtechlab.com/omsdk-1.6/ios | Enums/OMIDFriendlyObstructionType.html | — | 2026-09-22 | integratedFriendly obstruction types exist only on the native side and are integrated into spec.json enums |
Gaps to verify
- The field-level layout of the geometryChange payload must be verified field by field against the official spec PDF, including the differences between the iOS / Android and JS implementations (the friendly obstruction registration API exists only natively).
Related chapters
- Session model overview
- Enumeration registry
- Event payloads & geometry fieldsplanned