Most stored Flashtalking hits are ft.stat, not the impression pack

What the stored tags were

In the private sample table, ad-events.flashtalking.com is the larger Flashtalking host, on the order of a few hundred rows from September into October 2026. The path that showed up is /ft.stat followed by a semicolon-separated tuple, for example a stat hit whose first fields look like an account, a placement, and a creative. servedby.flashtalking.com/imp/ is the smaller set, tens of rows, with the legacy impression tuple in the path.

Those two URLs are not interchangeable. An impression tag that validates does not tell you the ft.stat tuple is complete, and a core-only pass on ft.stat does not tell you the impression pack would accept it.

Which pack actually selects

vendor/flashtalking-impression matches servedby.flashtalking.com, servedby-us, servedby-eu, and servedby-emea, and only when the path starts with /imp/. The positional names on that pack are template completeness advice from the published HTML5 fallback and the Innovid Tag Assistant recognizer. Missing tuple slots warn. They are not a claim that Flashtalking's server rejects the tag.

vendor/flashtalking is the OneTag container on servedby.flashtalking.com/container/. vendor/flashtalking-state is /state/ on the same servedby hosts. vendor/flashtalking-ftrack is POST /lgc on d9.flashtalking.com. None of those three match /ft.stat. The FTrack description says current /ft.stat stays outside that pack on purpose.

What to run

For a servedby /imp/ URL, pixellint validate url with --rulepack vendor/flashtalking-impression. For a container snippet, use vendor/flashtalking. For a /state/ tuple, use vendor/flashtalking-state. For a d9 /lgc body, use vendor/flashtalking-ftrack. For /ft.stat, omit the vendor flag and read the core report. Forcing the impression pack onto an ft.stat URL will not select it, because the host and path do not match.

The playground shows the same split. A selected impression pack means destination coverage. A core-only line on ft.stat means the shared checks ran and no Flashtalking field contract did.

pixellint validate url @servedby-imp.txt --rulepack vendor/flashtalking-impression
pixellint validate url @ft-stat.txt

What this page does not claim

This page does not assign meanings to the semicolon fields on /ft.stat. The stored example shows that the tuple exists. It does not establish which position is the placement, which position is the cache buster, or which empty slot the collector rejects. Inventing those names from one tag would be a false contract.

Flashtalking's public site now redirects to Innovid. The checks still see flashtalking.com hosts, so the logo stays Flashtalking and the packs stay under that vendor id. Pixellint is not affiliated with Flashtalking or Innovid.

How to keep the fixtures apart

Store the ft.stat URL and the servedby impression URL as two files. A VAST response often fires both. Validating only the impression and calling the tag clean leaves the larger stored surface unchecked. Validating only ft.stat and expecting impression findings will show core checks and look like the pack is broken.

When a future pack cites a public ft.stat document, this page should point at it and the core-only note should come off those URLs. Until that document is in the engine, the honest report is the one the playground already prints.

Sources

• Flashtalking impression pack, servedby /imp/

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.