Cint Lucid pixels check campaign measurement fields.

Documented Cint/Lucid campaign image pixels, default reporting metadata and explicit GDPR consent profile. ID spelling, optional video/custom data and account acceptance remain open where public sources do not define them.

What this pack matches

Hosts: tracker.samplicio.us
Paths: Full path expression: /tracker/[^/]*/pixel\.(?:gif|giff|png)
Vendor docs: help.cint.com/docs/lucid-media-measurement-terminology

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
`campaign_id`	required	The documented route carries the supplied Lucid campaign ID. Verify that the configured campaign is present; no identifier alphabet or length is inferred. Presence diagnostic severity: warning.	`vendor.cint-lucid-pixel.param.campaign_id.missing` `vendor.cint-lucid-pixel.param.campaign_id.empty`	docs
`sid`	recommended	The published default pixel includes this site or publisher reporting field. Missing metadata limits reporting granularity; supplied values remain opaque and account mapping needs external context. Presence diagnostic severity: warning.	`vendor.cint-lucid-pixel.param.sid.missing`	docs
`pid`	recommended	The published default pixel includes this placement reporting field. Missing metadata limits reporting granularity; supplied values remain opaque and account mapping needs external context. Presence diagnostic severity: warning.	`vendor.cint-lucid-pixel.param.pid.missing`	docs
`crid`	recommended	The published default pixel includes this creative reporting field. Missing metadata limits reporting granularity; supplied values remain opaque and account mapping needs external context. Presence diagnostic severity: warning.	`vendor.cint-lucid-pixel.param.crid.missing`	docs
`cachebuster`	recommended	The published Lucid image template supplies cachebuster, and Cint implementation guidance recommends the platform cache-buster macro. A single request cannot prove randomness, freshness or uniqueness. Presence diagnostic severity: warning. Evidence: vendor template.	`vendor.cint-lucid-pixel.param.cachebuster.missing` `vendor.cint-lucid-pixel.param.cachebuster.empty`	docs
`idfa`	optional	Optional mobile advertising identifier. Public guidance does not define an identifier alphabet, length or universal presence.		docs
`video_action`	optional	Optional video action. Published start, stop, skip and complete values are examples, so custom action names remain open.		docs
`video_completion`	optional	Optional viewed amount expressed as time or percentage. No exclusive unit, numeric grammar or universal 0-to-100 bound is inferred.		docs
`c1`	optional	Optional custom campaign data. Values, including empty and encoded text, remain opaque.		docs
`c2`	optional	Optional custom campaign data. Values, including empty and encoded text, remain opaque.		docs
`c3`	optional	Optional custom campaign data. Values, including empty and encoded text, remain opaque.		docs
`c4`	optional	Optional custom campaign data. Values, including empty and encoded text, remain opaque.		docs
`c5`	optional	Optional custom campaign data. Values, including empty and encoded text, remain opaque.		docs
`gdpr`	optional	Explicit GDPR applicability signal. Destination consent advice is scoped to observed values that are all literal 1; absence, other values and unresolved macros do not establish jurisdiction.		docs
`gdpr_consent`	optional	Supplied consent is structurally inspected as TCF v2. Local decoding does not establish jurisdiction, current GVL applicability, account acceptance or every TCF 2.2 policy obligation. Presence diagnostic severity: warning.	`vendor.cint-lucid-pixel.param.gdpr_consent.empty` `vendor.cint-lucid-pixel.param.gdpr_consent.invalid`	docs
`gdpr_consent_expected`	recommended	The documented Lucid measurement profile expects consent when GDPR applicability is explicitly 1. Fix: Provide the applicable TCF consent signal or verify the upstream partner and collection context.	`vendor.cint-lucid-pixel.gdpr_consent_expected`	docs
`tcf_consent_profile`	recommended	The documented Lucid TCF profile expects vendor 508 and purpose consents 1, 7, 8 and 9. Fix: Verify the supplied consent with the publisher/CMP and the deployed Lucid integration.	`vendor.cint-lucid-pixel.tcf_consent_profile`	docs

Validate a payload

pixellint validate url "$ARTIFACT" --rulepack vendor/cint-lucid-pixel

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

https://tracker.samplicio.us/tracker/campaign_ID/pixel.gif?sid=site_ID&pid=placement_ID&crid=creative_ID

cargo install pixellint · npm install pixellint