IAB Tech Lab published guidance on October 19 for companies adopting the Ad Creative ID Framework (ACIF), asking every organization that handles ad creatives to document how it receives and shares the UniversalAdID attribute.

What happened

The post is by Brad Pipkin, Director of Product, Advanced Television at IAB Tech Lab. It splits the work into two questions: how does a company receive UniversalAdIDs, and how does it share them. For each, it asks teams to list every path first. Advertiser intake paths include insertion orders, creative approval tools and trafficking spreadsheets. Ad tech paths include ad servers, VAST ad tags, DSP and SSP bid requests, and CTV app ingestion.

Teams then rate each path as fully or partly supported. The post’s examples of partial support include an ID accepted only in a specified field, stored but not passed downstream, overwritten by an internal creative ID, or suppressed for legacy integrations. Sharing paths cover reporting, billing and audit exports.

Why it matters

The post says that when the identifier is lost downstream, cross-platform alignment breaks and much of the benefit of a unique creative ID goes with it. It also says adoption is not purely technical, and asks organizations to settle who troubleshoots missing IDs and who can switch propagation on or off.

One detail worth reading closely

In our reading, this is an audit template more than a specification change. The post names no company and sets no deadline. Its examples of where an ID gets lost are everyday workflows, such as a trafficking spreadsheet or a billing export, so the quickest check for a marketing team is to follow one creative from agency handoff to final report and see where the ID stops. Related: Ad Tech Can’t Agree on One Language for AI Buyers, and Teads and Koddi Open Wolt, Gopuff UK and Hopper Retail Media to OpenRTB Buying.

Source: IAB Tech Lab