June is a heavy month for industry standards, and publishers who skip the public-comment windows are choosing to live with rules other people write. Beyond this week’s headline bot-management guidance, IAB Tech Lab and IAB Europe have two more comment periods closing this month — each with direct operational consequences for how publishers report campaigns and manage consent.
011. Campaign Data Standards — comment closes June 14
IAB’s Campaign Data Standards aim to end what the industry euphemistically calls “the reconciliation nightmare” — the endless mismatch between how buyers, sellers, and platforms label and count the same campaign. By standardizing campaign data fields and taxonomy, the initiative promises cleaner measurement, faster reconciliation, and less manual cleanup across the supply chain.
The industry is invited to test, validate, and comment by June 14, with a final version expected in Q4 2026. For publishers, this is plumbing that pays off: every hour your ops team spends reconciling mismatched campaign data is an hour and a margin point lost. Standardized fields mean fewer disputes, faster billing, and measurement everyone can agree on.
022. TCF Policy v5.0-B — comment closes June 29
IAB Tech Lab and IAB Europe are advancing the Transparency and Consent Framework (TCF) to Policy Version 5.0-B, with updates that remove a legacy workaround and tighten TCF UI requirements. The public-comment window runs through June 29. This sits alongside continued work on the Global Privacy Platform (GPP) and Data Deletion Request Framework (DDRF) — the broader machinery of privacy-signal interoperability.
TCF changes are not cosmetic. They affect consent-string handling, the consent UI your users see, and how legally defensible your data operations are — particularly for publishers with European audiences. A UI requirement change can mean real CMP reconfiguration work, and getting it wrong has compliance consequences.
03Why this matters
| These standards become your obligations | Once finalized, Campaign Data Standards and TCF updates shape your reporting, billing, and consent operations whether or not you participated in writing them. |
|---|---|
| Comment windows are leverage | This is the rare moment when a publisher's specific operational pain — a field that doesn't map, a UI rule that breaks your CMP — can actually change the standard before it's locked. |
| Compliance is downside protection | TCF and privacy-framework changes carry legal exposure. Tracking them isn't optional housekeeping; it's risk management. |
04What publishers should do this quarter
05What marketers should do
06The bottom line
Standards are written by whoever shows up. This June, IAB has opened three windows that touch reconciliation, AI-bot access, and consent — the exact systems that determine how efficiently and how compliantly publishers run. The comment periods are short and the consequences are long. Engaging now is the cheapest leverage a publisher will get all year.