vendor/floodlight · vendor documented
Floodlight parameters ride on the path
Not a query string. /ddm/activity/src=123;type=conv;cat=purch;ord=1 is the shape. src is the numeric Floodlight configuration ID. type is the activity group. cat is the activity. ord is the cache buster. Unique counting also needs num alongside ord.
What this pack matches
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 |
|---|---|---|---|---|
src |
required | It is the numeric Floodlight configuration ID for the advertiser. Fix: Set `src` to the advertiser's Floodlight configuration ID. | vendor.floodlight.param.src.missingvendor.floodlight.param.src.emptyvendor.floodlight.param.src.invalid |
docs |
type |
required | It is the activity group tag string. Fix: Copy `type` from the Floodlight activity in Campaign Manager. | vendor.floodlight.param.type.missingvendor.floodlight.param.type.empty |
docs |
cat |
required | It is the activity tag string. Fix: Copy `cat` from the Floodlight activity in Campaign Manager. | vendor.floodlight.param.cat.missingvendor.floodlight.param.cat.empty |
docs |
ord |
required | It is the cache buster, so every fire is counted separately. Fix: Emit a fresh random value for `ord` on every fire, or `ord=1` with `num` for unique counting. | vendor.floodlight.param.ord.missingvendor.floodlight.param.ord.empty |
docs |
num |
optional | Unique counting sends `ord=1` alongside a random `num`. | vendor.floodlight.param.num.empty |
docs |
counting.unique_requires_ord |
required | The tag counts unique users with `num` but omits `ord`. Unique counting sends `ord=1` together with a random `num`. Fix: Add `ord=1` next to the random `num` value. | vendor.floodlight.counting.unique_requires_ord |
docs |
Validate a payload
pixellint validate url "$ARTIFACT" --rulepack vendor/floodlight
Or paste it into the playground. Same engine, in the browser, nothing sent anywhere.
cargo install pixellint
·
npm install pixellint