pixellint

RTB House impression tags on creativecdn.com have no field contract

Short answer

The logo on the homepage points here because stored checks ran on RTB House impression hosts, and Pixellint does not yet publish a destination pack for them.

Validate a pixel

What the stored tags were

Pixellint keeps playground and tester artifacts in a private sample table. Grouped by host, ams.creativecdn.com is one of the largest video-tracking hosts in that table, on the order of several hundred rows across September 2026, not a single burst. The artifact shape that showed up is https://ams.creativecdn.com/ad/imp-tags with a tk query parameter. That is an impression-tag URL, not a retail page pixel and not a VAST document.

A host count is not a schema. The tk value on those rows is an opaque token. Pixellint does not treat tk as required, optional, or signed. Seeing it on stored tags only says the checks have run on this collector.

How the domain is attributed

DuckDuckGo Tracker Radar lists creativecdn.com with owner RTB House S.A. and links the RTB House privacy policy. The same radar page records sibling hosts such as us.creativecdn.com/ad/imp-tags, tags.creativecdn.com, and regional creativecdn.com tag endpoints. That is enough to put the RTB House name on the logo, and it is not enough to write a parameter contract.

Retail tagging that agencies paste into a storefront often uses creativecdn.com/tags with an id that starts with pr_ and a page suffix such as home, offer, or conversion. Server postbacks in third-party integration notes use a regional host and /partner/omni/postbacks. Neither of those surfaces is the /ad/imp-tags URL in the sample table. Do not debug an impression tag by pasting a shop iframe snippet.

What runs on these URLs today

No vendor rulepack matches creativecdn.com. The directory does not list the host either. Validation therefore stays on the shared core: the URL has to parse, the scheme has to be http or https, insecure transport is flagged, and a broken privacy macro such as gdpr=NaN still errors. A core pass means the URL is well formed. It does not mean RTB House accepted the impression.

Paste the live URL into the playground, or run pixellint validate url on the artifact. If the report says core checks only, that is the accurate coverage state for this host. Directory attribution and a destination pack are different layers, and this host has neither.

What this page does not claim

This page does not list required query keys, token lengths, or event names for /ad/imp-tags. Those would be guessed from the sample table, and Pixellint does not promote observations into vendor requirements. If RTB House publishes a field list for this collector, that document is what a future pack should cite.

The homepage logo links here so the mark does not send you to rtbhouse.com. The page is the Pixellint account of the host the checks ran on. It is not an RTB House product guide and Pixellint is not affiliated with RTB House.

How to lint one tag

Copy the impression URL out of the VAST response, including the tk parameter if it is present, and validate that string. Wrapper hops and other vendors on the same response are separate artifacts. A FreeWheel or Innovid URL later in the same tag does not inherit this page.

If the URL is actually creativecdn.com/tags or a postback to /partner/omni/postbacks, you are on a different RTB House surface. Core checks still apply. They still do not become an RTB House schema. Keep the impression tag and the retail tag in separate fixtures so a failure on one is not blamed on the other.

pixellint validate url @rtb-house-imp.txt

Questions

Does Pixellint validate RTB House impression tags?

It runs the shared URL, macro, and privacy checks. It does not select an RTB House rulepack, because no public field contract for /ad/imp-tags is in the engine.

Is creativecdn.com RTB House?

Tracker Radar attributes the domain to RTB House S.A. and points at the RTB House privacy policy. The retail tagging host creativecdn.com/tags is a different path from /ad/imp-tags.

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.