vendor/kochava · vendor documented

Kochava S2S events need an app id and event name

JSON to /track/json. kochava_app_id, action, and data.event_name are required. The article's field table and sample disagree on nesting for everything else, so those fields stay unchecked.

What this pack matches

Hosts: control.kochava.com
Paths: …/track/json…
Vendor docs: support.kochava.com/articles/server-to-server-integration/185-post-install-event-setup/

Rules

Codes are stable. A finding in CI, MCP, or the playground lands on the same id.

Field	Required	What it checks	Rule ids	Source
`kochava_app_id`	required	It is the Kochava app GUID, and the S2S event article requires it on every post-install payload. Fix: Set `kochava_app_id` to the app GUID from the Kochava dashboard.	`vendor.kochava.body.kochava_app_id.missing` `vendor.kochava.body.kochava_app_id.empty`	docs
`action`	required	It names the S2S call. The event article's sample sends `event`. Fix: Set `action` to `event` for a post-install event.	`vendor.kochava.body.action.missing` `vendor.kochava.body.action.empty`	docs
`kochava_device_id`	optional	It is a Kochava device identifier. The article requires the key; the value may be empty when `device_ids` carries an ID instead.	`vendor.kochava.body.kochava_device_id.empty`	docs
`data`	required	Kochava documents a `data` object on every post-install event payload. Fix: Add a `data` object with `event_name`.	`vendor.kochava.body.data.missing`	docs
`data.event_name`	required	It is the event name. The article places `event_name` inside `data`. Fix: Set `data.event_name` to the event the marketer expects.	`vendor.kochava.body.data.event_name.missing` `vendor.kochava.body.data.event_name.empty`	docs

Validate a payload

pixellint validate json @payload.json --rulepack vendor/kochava

Or paste it into the playground. Same engine, in the browser, nothing sent anywhere.

cargo install pixellint · npm install pixellint