IAB Tech Lab today published guidance that assigns adoption work for the Universal Ad ID, the creative identifier at the center of its Ad Creative ID Framework, to every company that touches an ad creative: brands, agencies, ad servers, demand-side and supply-side platforms, and connected TV platforms. The post, written by Brad Pipkin, Director of Product, Advanced Television at IAB Tech Lab, reduces adoption to two questions each organization is expected to answer, how it receives UniversalAdIDs and how it shares them, and lists eight conditions under which the identifier is only partly supported.

In Short

IAB Tech Lab wrote a guide telling every company in the TV and video ad chain to check where a special ID number for each ad comes into their systems and where it goes out. That matters because the ID only helps with things like limiting how often people see the same ad if it stays attached to the ad from start to finish. The guide asks companies to write down where the ID gets lost, changed or ignored, and to decide which team fixes it.

What IAB Tech Lab published

The document is titled "What's MY Role in Adopting ACIF's Universal Ad ID?" and carries the subtitle "Agnostic guidance across the advertising value chain." It appeared on the IAB Tech Lab website on October 19, 2026, under the advanced-tv tag, and links to the organization's standards page for the Ad Creative ID Framework. It is not a new version of the specification. There are no new fields, no deadlines and no compliance requirements in it. What it offers is an operational checklist, aimed at organizations that have heard of the framework but have not mapped how the identifier moves through their own systems.

According to IAB Tech Lab, ACIF "establishes a standardized approach for identifying advertising creatives using a UniversalAdID attribute shared throughout the advertising ecosystem." The post states the premise in one line: "If your systems or processes touch ad creatives, they touch UniversalAdID."

The framing that follows is blunt. "ACIF and Universal Ad ID adoption succeeds when organizations treat UniversalAdID not as something to 'support someday,' but as a core creative element that must survive intake, transformation, delivery, and measurement without ambiguity," the document reads.

The UniversalAdId element is not new. It entered the IAB's video ad serving template with VAST 4.0 in 2016, and the problem it addresses is old: each ad server, DSP and measurement vendor tends to assign its own internal identifier to the same piece of creative, so the same 30-second spot can carry half a dozen different IDs by the time it reaches a television screen. Reconciliation across those systems is then done by hand, or not at all.

Scenario 1: receiving the identifier

The first half of the guidance concerns intake. According to IAB Tech Lab, "Every organization receives creative details through multiple entry points," and the stated goal is to identify those paths and determine support levels for each. One sentence in this section captures the risk: "A UniversalAdID that enters the organization but is misunderstood is effectively invisible."

Inventory intake paths

The document separates intake paths by type of company. For advertisers, a group in which IAB Tech Lab includes both brands and agencies, it lists four typical intake paths:

  • Insertion order workflows and campaign management systems
  • Creative approval, clearance or compliance tools
  • Manual workflows such as emails, trafficking spreadsheets or email-based submissions
  • Measurement, verification and reconciliation systems

The inclusion of trafficking spreadsheets and email is notable. A large share of video and television creative still moves between agencies and sellers as attachments and rows in shared files, and an identifier typed into a spreadsheet cell is only as reliable as the person copying it.

For ad tech companies and platforms, a group the page defines as ad servers, DSPs, SSPs and CTV platforms, the list runs to five:

  • Ad servers and traffic systems
  • VAST ad tags
  • DSP or SSP bid requests and responses
  • CTV app ingestion pipelines
  • Measurement, verification and reconciliation systems

"Each intake path should be evaluated independently," according to the document.

Support levels on intake

Once the paths are known, IAB Tech Lab asks organizations to classify each as "fully supported" or "partially/conditionally supported," and to document "where the identifier is lost, transformed, or ignored." Full support, in the page's two examples, means the ID "is ingested, validated, stored and propagated unchanged" and "is available downstream for delivery, measurement, reporting and data exports."

Partial support is where the document gets specific. Its four intake examples are an ID accepted only if delivered in a specified field or object, an ID stored but not passed downstream, an ID used only for reporting and not for decisioning, and an ID overwritten or replaced by internal creative IDs. The page notes that the examples are not exhaustive.

The third condition is the one with the clearest commercial effect. An identifier that reaches a reporting table but is never read by the decisioning logic cannot help with frequency capping or competitive separation, the two buying problems the framework was designed to address. The fourth describes a common practice: many platforms assign their own creative IDs at upload, and if the registered ID is replaced rather than kept alongside, the link back to the registry is gone.

Scenario 2: sharing the identifier

The second half covers distribution. "Sharing UniversalAdID consistently is as critical as receiving it," according to IAB Tech Lab. "Loss of the identifier downstream breaks cross-platform alignment and can dramatically reduce the operational benefits that come from these truly unique identifiers."

Distribution paths

For brands and agencies, the page lists four typical distribution paths: cross-team internal handoffs, with the example of a creative agency passing work to a media agency; reporting, data exports, billing and reconciliation feeds; measurement, verification and attribution vendors; and regulatory, compliance or audit exports.

For ad servers, DSPs, SSPs and CTV platforms there are five: outbound ad requests and responses; supply-side or demand-side integrations; reporting, data exports, billing and reconciliation feeds; measurement, verification and attribution vendors; and regulatory, compliance or audit exports.

The overlap between the two lists is deliberate. Billing feeds, verification vendors and audit exports appear on both sides, which is where disputes over delivered impressions tend to land. A creative that cannot be matched between a buyer's billing file and a seller's delivery log is a reconciliation problem, whatever each party's internal reporting says.

Support levels on sharing

The fully supported state for sharing has two parts in the document: the ID "is transmitted intact and unmodified" and "remains associated with the creative across systems."

The four partial conditions on the sharing side are an ID shared only with select partners, an ID included only in reporting and not in data exports, an ID suppressed for legacy integrations, and an ID mapped to internal IDs without external visibility. Together with the four intake conditions, that makes eight named ways in which the identifier survives only in part.

Suppression for legacy integrations points to a specific technical history. Before IAB Tech Lab's VAST CTV Addendum, the UniversalAdId node existed only in VAST 4.x. Older VAST 2 and 3 players had no standard place for it, so a platform serving through those versions had nowhere to put the ID even if it held one.

Ownership and business process

The final section, headed "Your Role: Align On Understanding and Ownership," moves from systems to people. "Clear ownership prevents silent failures that surface only during audits, reconciliation, or live events," according to the document.

IAB Tech Lab asks organizations to make sure relevant teams understand four things: when the ID must be shared and when it is optional, which teams are responsible for enabling or disabling propagation, how partner requirements differ across platforms, regions or media types, and how to respond when partners ask for ACIF compliance validation.

"UniversalAdId adoption is not purely technical," the page states. It names engineering, operations, ad ops and compliance as teams that need a consistent understanding of how the identifier is handled, and it calls for clear ownership of three tasks: troubleshooting missing or invalid IDs, partner escalation, and internal documentation and training.

The reference to "live events" is worth noting. Sports and other live broadcasts are where frequency and competitive separation failures are most visible to advertisers, because a small number of high-value ad breaks carries a large share of spend, and a repeated or conflicting ad in those breaks is seen by a large audience at once.

What the guidance does not say

The page sets out a method, not a measure. It contains no figures on current adoption, no list of companies that support the identifier, and no timeline. It does not say which party in the chain is responsible for registering a creative in the first place. It also does not define what "compliance validation" involves beyond referring to partner requests for it.

The text itself is unpolished in places. The byline reads "Advanced Televsion," and the identifier is written as both "UniversalAdID" and "UniversalAdId," sometimes within the same paragraph. The VAST element is spelled UniversalAdId in the specification.

The linked ACIF standards page fills in part of the background. According to that page, the framework and its companion Validation API specification have both been finalized at version 1.0; the page was last updated on March 18, 2025. The Validation API was released on December 4, 2024, for a 45-day public comment period. The same page also says "Public comment closed on January 18, 2024," a date that precedes the release it refers to; a 45-day period from December 4, 2024, would end in mid-January 2025, so the year appears to be an error on IAB Tech Lab's page.

According to the standards page, ACIF was developed by the IAB Tech Lab Advanced TV Commit Group. It names Ad-ID in the United States and Clearcast in the United Kingdom as examples of creative registries, and describes registering an ad as comparable to registering a UPC barcode for a retail product. The page says the VAST 2024 Addendum makes the UniversalAdId node available in all versions of VAST. Companies running an ACIF workflow can self-attest through IAB Tech Lab's Tools Portal under its Specification Adoption Program. There is no formal certification.

How ACIF got here

PPC Land has followed the framework since the beginning. In April 2024, IAB Tech Lab released a draft VAST CTV Addendum that would bring UniversalAdId from VAST 4.x into VAST 2 and 3, aimed at cross-media measurement and at reconciliation between linear and CTV campaigns.

In June 2024, IAB Tech Lab opened the Ad Creative ID Framework for public comment, developed with the 4A's, the ANA and Ad-ID, with feedback accepted until July 12, 2024. The stated targets then were the same as now: frequency capping, competitor separation, cross-platform reporting and campaign reconciliation in CTV.

When IAB Tech Lab set out its plans for the year in January 2025, ACIF appeared in its 2025 technical standards roadmap as a long-term item for cross-television measurement. The following month, PPC Land reported that the framework had gained support from four registries: Auditel in Italy, Ad-ID in the United States, ARPP in France and Clearcast in the United Kingdom. Their formats differ. Ad-ID codes run to 12 characters starting with four letters, Auditel's CUSV code has 14 characters, ARPP's has 21, and Clearcast uses a pattern with a three-letter agency code. Adform's documentation at the time also stated that registered IDs could not be used for dynamic or rotator ads.

In June 2025, IAB Tech Lab integrated UniversalAdId into the Open Measurement SDK, starting with version 1.5.5, so that apps and ad SDKs could pass the registry and ID values from VAST to measurement partners at session start.

Two months later, IAB Tech Lab outlined the CTV standards it still needed after a workshop held in August 2025. ACIF featured there, and so did its obstacles: who is responsible for registering ads, how to keep IDs attached through the supply chain, and how to prevent spoofing. Today's guidance addresses the second of those directly, and partly the first, by treating each organization as accountable for its own intake and distribution paths. It does not touch spoofing.

The identifier's reach depends on the version of VAST in use across the supply chain. In September 2026, Amazon DSP added support for VAST 4.0 through 4.3 on third-party publisher supply in 34 markets, while Amazon's own Stores and Fire TV inventory still accepted only VAST 2 and 3 creatives. That article did not say whether UniversalAdId is carried within Amazon's VAST 4 support.

Why the guidance matters for buyers and sellers

The framework's value to advertisers rests on a simple chain. If a registered creative ID survives from the agency's trafficking sheet to the adserver, through the bid request and into the measurement vendor's logs, then a buyer can cap frequency across platforms, keep competing brands out of the same break, and match delivery to invoices without manual mapping. Each link that drops or rewrites the ID ends that chain at that point.

That is why IAB Tech Lab has focused on intake and output paths rather than on the specification itself. The specification has existed for some time. Two and a half years after the framework was opened for comment, the organization is now asking each company to document where its own systems store the ID without passing it on, use it for reporting but not decisioning, or overwrite it with an internal code. These are exactly the conditions under which a buyer cannot tell from the outside whether the identifier is being honored.

For agencies, the most immediate implication is internal. The guidance names the handoff from creative agency to media agency as a distribution path in its own right, and lists email and trafficking spreadsheets as intake paths. Those are not systems a platform vendor can fix. For DSPs, SSPs and CTV platforms, the list points at bid requests and responses, legacy integrations and outbound ad responses, where a missing field is a product decision.

Whether any of this translates into wider adoption depends on what follows. A self-attestation program and a checklist leave the work, and the auditing of it, to the companies involved.

Timeline

Summary

Who: IAB Tech Lab, in a post by Brad Pipkin, Director of Product, Advanced Television, addressed to brands, agencies, ad servers, DSPs, SSPs and CTV platforms.

What: Guidance on adopting the Universal Ad ID under the Ad Creative ID Framework, built around two questions (how each organization receives the ID and how it shares it), with lists of intake and distribution paths, eight examples of partial support, and a call to assign ownership for missing or invalid IDs.

When: The guidance was published on October 19, 2026. ACIF was opened for comment in June 2024, and IAB Tech Lab's standards page says version 1.0 is finalized.

Where: On the IAB Tech Lab website, under its advanced TV work, applying across the video and CTV advertising supply chain.

Why: A creative identifier only supports frequency capping, competitive separation, measurement and reconciliation if it survives every system it passes through, and IAB Tech Lab's guidance targets the points where it is stored, overwritten, suppressed or ignored.