Kadam cookie matching checks documented template fields.

Template completeness advice for the documented SSP and DSP cookie-matching routes. Partner and user IDs stay opaque. Redirect configuration, callback ownership, duplicate selection, cookie state and receiver acceptance remain external. Complete HTTP captures retain the engine's existing URL-query and form-body merge; this profile does not prove query-only carriage or form transport support.

What this pack matches

Hosts: s.uuidksinc.net, d.uuidksinc.net
Paths: Full path expression: /match/[^/]*/
Vendor docs: help.kadam.net/en/articles/16532646-cookie-matching

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
`partner_id`	recommended	The official SSP and DSP templates place the provisioned partner ID in this physical path slot. Nonempty presence is template advice. No numeric, UUID, length, allocation or decoded-ID grammar is documented. Presence diagnostic severity: warning.	`vendor.kadam-cookie-sync.param.partner_id.missing`	docs
`remote_uid`	recommended	Both official matching templates substitute the partner's user ID in remote_uid. Nonempty presence is template advice. Values and extras remain opaque. Ordinary engine extraction also accepts a form-body carrier in a complete capture; no query-only or receiver acceptance claim is made. Presence diagnostic severity: warning.	`vendor.kadam-cookie-sync.param.remote_uid.missing`	docs

Validate a payload

pixellint validate url "$ARTIFACT" --rulepack vendor/kadam-cookie-sync

Try this failing payload in the playground. An example with a validation finding.

https://s.uuidksinc.net/match/partner-synthetic/

cargo install pixellint · npm install pixellint