Optionaladcp_Release-precision AdCP version (VERSION.RELEASE, e.g. "3.0", "3.1", "3.1-beta"). On a request: the buyer's release pin — the seller validates against its supported_versions and returns VERSION_UNSUPPORTED on cross-major mismatch, or downshifts to the highest supported release within the same major. On a response: the release the seller actually served — clients SHOULD validate the response against that release's schema, not against their pin. Patches are not negotiated; surface them as build_version on capabilities for operational visibility. When omitted, falls back to adcp_major_version (deprecated) or server default. Buyers SHOULD emit both adcp_version and adcp_major_version through 3.x to remain compatible with sellers that only read the legacy field. NORMALIZATION: SDKs that read full-semver values from bundle metadata (e.g. ComplianceIndex.published_version = "3.1.0-beta.1") MUST normalize to release-precision ("3.1-beta.1") before emitting on the wire — meta-field values are NOT valid wire values.
Optionaladcp_DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.
Event source configured on the account via sync_event_sources
Optionaltest_Test event code for validation without affecting production data. Events with this code appear in the platform's test events UI.
Events to log
Unique identifier for deduplication (scoped to event_type + event_source_id)
ISO 8601 timestamp when the event occurred
Optionaluser_match?: {Optionaluids?: [{ type: UIDType; value: string }, ...{ type: UIDType; value: string }[]]Universal ID values for user matching
Optionalhashed_email?: stringSHA-256 hash of lowercase, trimmed email address. Buyer must normalize before hashing: lowercase, trim whitespace. Pseudonymous PII, not anonymous — the email namespace is small enough that an unsalted SHA-256 is recoverable via precomputed dictionaries. Treat as PII for retention, consent, and access-control purposes. See docs/reference/privacy-considerations#unsalted-hashed-identifiers-are-pseudonymous-not-anonymous.
Optionalhashed_phone?: stringSHA-256 hash of E.164-formatted phone number (e.g. +12065551234). Buyer must normalize to E.164 before hashing. Pseudonymous PII, not anonymous — the E.164 namespace is small enough that an unsalted SHA-256 is recoverable via precomputed dictionaries. Treat as PII for retention, consent, and access-control purposes. See docs/reference/privacy-considerations#unsalted-hashed-identifiers-are-pseudonymous-not-anonymous.
Optionalclick_id?: stringPlatform click identifier (fbclid, gclid, ttclid, ScCid, etc.)
Optionalclick_id_type?: stringType of click identifier (e.g. fbclid, gclid, ttclid, msclkid, ScCid)
Optionalclient_ip?: stringClient IP address for probabilistic matching
Optionalclient_user_agent?: stringClient user agent string for probabilistic matching
Optionalext?: ExtensionObjectOptionalcustom_data?: EventCustomDataOptionalaction_source?: ActionSourceOptionalsurface?: EventSurfaceOptionalevent_source_url?: stringURL where the event occurred (required when action_source is 'website')
Optionalcustom_event_name?: stringName for custom events (used when event_type is 'custom')
Optionalext?: ExtensionObjectClient-generated unique key for this request. Prevents duplicate event logging on retries. MUST be unique per (seller, request) pair to prevent cross-seller correlation. Use a fresh UUID v4 for each request.
OptionalcontextOptionalext
Request parameters for logging marketing events