vendor/yahoo-dot · vendor documented

Yahoo Dot pixels need a and .yp

The DSP pixel is an image request. a is the project, and projectId is the JavaScript twin of that name. .yp is the pixel id, including the leading dot. That is the instrumentation Yahoo's pixels API returns.

What this pack matches

Hosts: sp.analytics.yahoo.com
Paths: /spp.pl
Vendor docs: help.yahooinc.com/dsp-api/docs/pixels

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
`a`	required	It is the project ID. Every official image pixel Yahoo returns includes `a`, and the JavaScript twin sends it as `projectId`. Fix: Copy the image pixel from Yahoo DSP so `a` carries the project ID.	`vendor.yahoo-dot.param.a.missing` `vendor.yahoo-dot.param.a.empty`	docs
`.yp`	required	It is the Yahoo Dot pixel ID. Every official image pixel includes `.yp`, and the Conversions API docs identify Dot firings by that parameter. Fix: Copy the image pixel from Yahoo DSP so `.yp` carries the pixel ID.	`vendor.yahoo-dot.param..yp.missing` `vendor.yahoo-dot.param..yp.empty` `vendor.yahoo-dot.param..yp.invalid`	docs
`he`	optional	Enhanced matching sends the email as a SHA-256 hex digest. Fix: Hash the email with SHA-256 and send the hex digest as `he`.	`vendor.yahoo-dot.param.he.empty` `vendor.yahoo-dot.param.he.invalid`	docs
`hph`	optional	Enhanced matching sends the phone number hashed. Fix: Hash the phone number and send the digest as `hph`.	`vendor.yahoo-dot.param.hph.empty` `vendor.yahoo-dot.param.hph.invalid`	docs
`unhashed_email`	required	A parameter carries what looks like a raw email address. Yahoo documents enhanced matching as `he`, a SHA-256 digest. Fix: Hash the email with SHA-256 and send it as `he`.	`vendor.yahoo-dot.unhashed_email`	docs

Validate a payload

pixellint validate url "$ARTIFACT" --rulepack vendor/yahoo-dot

Try this failing payload in the playground. Yahoo Dot missing a.

https://sp.analytics.yahoo.com/spp.pl

cargo install pixellint · npm install pixellint