pixellint

Celtra track.celtra.com is directory attribution, not a field pack

Short answer

The logo points here because stored checks ran on Celtra's track host, and the engine can name the vendor without checking a Celtra schema.

Validate a pixel

What the stored tags were

track.celtra.com accounts for on the order of two hundred stored rows from early September through the start of October 2026. The shape that showed up is https://track.celtra.com/json/ followed by a long opaque path segment. Decoding that segment is not something this page does, and it is not something the engine requires. The host and the /json/ prefix are enough to recognize the collector.

A single decoded example in the table carried an events array whose first name was vastImpression, plus account, video length, stream, and session fields. That is a description of one stored artifact. It is not a Celtra schema. Empty or extra fields on the next tag are not errors until a published contract says so.

Directory versus destination

The vendor directory lists celtra.com and does not attach a rulepack. Directory coverage means the report can say Celtra. Destination coverage means a pack selected and checked fields. These samples get the first and not the second. The playground should say core checks only, with the directory name beside it if the build you are on still prints directory attribution.

Core checks still matter. A tracker URL with a broken scheme, a userinfo password, or gdpr=NaN fails the same way it would on any other host. Those findings are shared rules. They are not Celtra rejections.

The tag generator is a different surface

Celtra's public tag-generator article says Universal VAST videos pick a VAST version in the generator, and encoding presets, including minimum bitrate, come from the tag template. That document is about the VAST tag you traffic into a placement. It does not specify the query or path grammar of track.celtra.com/json/.

Lint the generated VAST document with a VAST validator. Lint the track URL with Pixellint. A valid VAST tag can still point at a track URL that only received core checks. A core-clean track URL does not prove the VAST version in the generator was the one you selected.

What this page does not claim

There is no required event name, no required account id, and no JSON schema on this page. Adding those from the stored sample would freeze one campaign's payload as if Celtra had published it. The pack, when it exists, should cite Celtra's own collector document.

Pixellint is not affiliated with Celtra. The homepage logo links here so it does not send you to celtra.com. The support article linked below is about tag generation, not about this collector's acceptance rules.

How to lint one tag

Copy the track.celtra.com URL from the VAST impression or tracking node and run pixellint validate url on that string. Do not pass a vendor rulepack flag. There is no Celtra pack id to select. If you validate the surrounding VAST XML in vastlint, that is a separate tool and a separate report.

Keep the opaque /json/ segment intact. Truncating it to make the fixture shorter changes the artifact the core parser sees. If the next Celtra document defines that segment, replace this page's core-only guidance with the pack page.

pixellint validate url @celtra-track.txt

Questions

Does a Celtra directory hit mean the JSON was validated?

No. The directory recognizes celtra.com. There is no vendor/celtra rulepack, so track.celtra.com URLs stay on core checks.

Is the tag generator the same host?

No. Celtra's tag generator chooses a VAST version and encoding presets for a placement. track.celtra.com is the collector that showed up in samples. They are different surfaces.

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.