RESERVED_METADATA_KEY

The reserved properties key through which the library's own emit sites hand an event's EventMetadata to the tracker (#287).

The tracker built by Autograph always removes this key from the properties of a track or screen event, before AutographConfig.validator runs, so it never reaches a validator or a transport's track/screen properties — even when its value is malformed. Only the fields listed on EventMetadata are read from it; anything else is discarded. identify traits are not read for it: a trait under this key is not removed, and it carries no metadata. The value is a JSON object encoded as a string:

"__autograph": "{\"kind\":\"impression\",\"impression\":{\"min_duration_ms\":500,\"min_fraction_visible\":0.5}}"

A string rather than a nested object because of Swift: Kotlin/Native hands a JsonObject value to Objective-C as a dictionary, not as a JsonElement, so a Tracker implemented in Swift crashes the process the moment it reads a nested object out of its properties. That was measured both for this key and for an app's own nested property, so it is not specific to metadata. A string crosses that bridge intact. The tracker also accepts the object itself, unencoded, which is what a Kotlin caller would naturally write. A string longer than MAX_ENCODED_METADATA_LENGTH characters, or nested deeper than the metadata ever is, is not parsed and carries nothing.

It is a convention, not proof that the library produced the event: an app can put the same shape in its own properties, and the tracker treats it the same way. Only the call-site properties are read — a value under this key in DefaultProperties or in any scope (compose, ScopeStack, an element's autocapture scope, a SwiftUI scope) is removed and ignored.

A Tracker you implement yourself, such as a test fake, does not strip it, so a fake standing in for the real tracker sees this key in the properties of events the library emits.