pixellint

Extreme Reach beacons are named in the directory and not field-checked

Short answer

The logo points here because stored checks ran on beacons.extremereach.io, and Pixellint can name Extreme Reach without a beacon schema.

Validate a pixel

What the stored tags were

beacons.extremereach.io is a steady host in the sample table, on the order of sixty rows from early September through mid-October 2026, including rows on the day this page was written. The path that showed up is /cp-imp. Query names on a stored beacon included cid, creative_id, line_item, companion_id, er_ts, session_id, and er_fp. That list is an observation. It is not the acceptance contract.

The company now publishes as XR at xr.global. The collector host has not moved to an xr.global name in these samples. Match the host you copied, not the wordmark on the marketing site.

Directory versus destination

The vendor directory lists extremereach.io and does not attach a rulepack. A report can therefore attribute the URL to Extreme Reach and still say the checks that ran were core checks. Those are different sentences. Attribution tells you who operates the host. The pack, which does not exist, would tell you which fields are required.

Core findings still fire. An http beacon on a page that expects https, a URL that does not parse, or a privacy macro with a non-value such as NaN are shared errors. They do not become Extreme Reach errors just because the directory recognized the suffix.

What this page does not claim

There is no required cid, no required creative_id, and no event enumeration for /cp-imp on this page. A beacon missing one of the names seen in storage is not, by itself, a Pixellint error. If XR publishes a beacon specification, that document should become the pack, and this paragraph should shrink to a pointer.

Pixellint is not affiliated with Extreme Reach or XR. The logo links here so it does not send you to the company site. The XR homepage is a source for the current name, not for the beacon query grammar.

How to lint one tag

Copy the beacon URL from the VAST impression or quartile node and run pixellint validate url with no vendor flag. Do not point --rulepack at another video vendor because the path looks similar. A DoubleVerify visit.jpg and an Extreme Reach /cp-imp can sit in the same creative and they select different coverage.

Keep companion_id and the impression beacon as they were served. Dropping query pairs to shorten a ticket changes the artifact. The core parser sees the string you pass, not the VAST node you meant.

pixellint validate url @extreme-reach-beacon.txt

What still belongs on the pack pages

Vendors on the same logo wall that do have destination packs should be linted on those packs. Adform video tags, DoubleVerify visit.jpg, NEXD AdCanvas csc-event, XPLN /video, and Adnami /api/tracker each select their own rulepack. Extreme Reach does not borrow their fields.

If a later sample moves from beacons.extremereach.io to a new XR host, treat it as a new artifact. Do not assume the directory suffix still matches. Update the directory only when the host is corroborated, and add a pack only when a public field contract exists.

Questions

Does Pixellint require cid on an Extreme Reach beacon?

No. cid, creative_id, and line_item appeared on a stored /cp-imp URL. They are not a published required set in this engine.

Why does the logo say Extreme Reach if the site says XR?

The host in the samples is extremereach.io, and the directory name is Extreme Reach. XR is the current public site of that company. The mark on the wall is their current logo.

Sources

Check the artifact

Paste the pixel URL or JSON body into the playground. Same engine as pixellint validate. Artifacts you test may be stored; see privacy.