Beeswax conversion tags need tag_id and buzz_key.
The published Buzz conversion image tag on cnv.event.prod.bidr.io/log/cnv with tag_id, buzz_key, value, order and ord. Impression and click routes, cookie sync and postbacks stay outside this pack.
Buzz generates tag_id and buzz_key and says not to edit them. value, order and ord receive format advice when present.
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 |
|---|---|---|---|---|
tag_id |
required | Buzz generates the tag identifier and the conversion tag guide says not to edit it. The sample is numeric, and the page does not publish a character grammar, so only presence is checked. Fix: Keep the tag_id from the conversion tag Buzz generated. | vendor.beeswax-conversion.param.tag_id.missingvendor.beeswax-conversion.param.tag_id.empty |
docs |
buzz_key |
required | Buzz generates the account instance key and the conversion tag guide says not to edit it. The Buzz Key page says that value uses only alphanumeric characters. Fix: Keep the alphanumeric buzz_key from the conversion tag Buzz generated. | vendor.beeswax-conversion.param.buzz_key.missingvendor.beeswax-conversion.param.buzz_key.emptyvendor.beeswax-conversion.param.buzz_key.invalid |
docs |
value |
optional | When present, the conversion tag guide says to set value to a number, and the published example is 30. Omitted values use the number stored on the Buzz event. This check accepts a non-negative integer or decimal and warns on anything else, because the page does not publish a sign, exponent, or separator grammar. Value diagnostic severity: warning. Fix: Set value to a non-negative number, or omit it to use the Buzz event value. | vendor.beeswax-conversion.param.value.emptyvendor.beeswax-conversion.param.value.invalid |
docs |
segment_key |
optional | The conversion tag guide says a segment id is generally set when the event is created and should not be edited. It does not require the parameter on every tag, and it does not publish a character grammar. Fix: Keep the segment_key Buzz generated, or omit it. | vendor.beeswax-conversion.param.segment_key.empty |
docs |
order |
optional | When present, the conversion tag guide says to set order to a number of items, and the published example is 2. Omitted values use the number stored on the Buzz event. This check accepts a non-negative integer or decimal and warns on anything else, because the page does not publish a sign, exponent, or separator grammar. Value diagnostic severity: warning. Fix: Set order to a non-negative number, or omit it to use the Buzz event order. | vendor.beeswax-conversion.param.order.emptyvendor.beeswax-conversion.param.order.invalid |
docs |
ord |
required | The conversion tag guide says the implementation requirement is to replace [CACHEBUSTER] with a random number generated at runtime. The published script uses Math.floor, so this check expects a non-negative integer of digits. The page does not publish a maximum length. Fix: Set ord to a random whole number generated when the tag fires. | vendor.beeswax-conversion.param.ord.missingvendor.beeswax-conversion.param.ord.emptyvendor.beeswax-conversion.param.ord.invalid |
docs |
Validate a payload
pixellint validate url "$ARTIFACT" --rulepack vendor/beeswax-conversion
Or paste it into the playground. Same engine, in the browser, nothing sent anywhere.
cargo install pixellint
·
npm install pixellint