pixellint

vendor/lotame · vendor documented

Lotame Lightning Tag puts the client ID in the path

Lotame documents the loader as /lt/c/{lotameClientId}/lt.min.js. The client ID is an integer. bcp.crwdcntrl.net is not this pack.

The client ID is an integer path segment

A loader with a non-numeric client ID is not the published Lightning Tag.

Rule: vendor.lotame.param.client_id.invalid

What this pack matches

Hosts
tags.crwdcntrl.net
Paths
…/lt/c/…
Vendor docs
my.lotame.com/t/83hxvnt/lt-js-basic-implementation

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
client_id required It is the Lotame client ID. Lotame documents the loader as tags.crwdcntrl.net/lt/c/{lotameClientId}/lt.min.js and Number(lotameClientId). Fix: Replace {lotameClientId} with the numeric client ID from Lotame, such as /lt/c/123456/lt.min.js. vendor.lotame.param.client_id.missing
vendor.lotame.param.client_id.empty
vendor.lotame.param.client_id.invalid		 docs

Validate a payload

pixellint validate url "$ARTIFACT" --rulepack vendor/lotame

Try this failing payload in the playground. Lotame Lightning Tag with a non-numeric client ID.

https://tags.crwdcntrl.net/lt/c/abc/lt.min.js

cargo install pixellint · npm install pixellint