Not automatically. Cross-origin browser restrictions limit what the parent page can inspect, so reliable game-ready measurement normally needs supplier cooperation or a separately labelled test observation. The same-origin policy restricts cross-origin script access; it does not grant your analytics code visibility into the embedded game’s internal state. (developer.mozilla.org)
Ask the supplier for a documented event contract covering:
- Ready, error, unavailable and session-ended events.
- Event version and payload schema.
- Expected sending origin and frame.
- Game and launch identifiers.
- Whether retries or duplicate events are possible.
- Which events are supported consistently across studios.
If the integration uses postMessage, validate the sender’s origin and source, and validate the message structure. Use a specific target origin when sending messages to a known recipient. (developer.mozilla.org)
For network timing, Timing-Allow-Origin can expose otherwise restricted Resource Timing attributes. It is not a game-ready signal and does not provide unrestricted access to a nested game’s internal state. (developer.mozilla.org)
If instrumentation is unavailable, report a manual or synthetic observation with its method and timestamp. Use “game-ready timing not instrumented” rather than presenting frame navigation or page rendering as a substitute.