/ /

About the IAB USNAT v3.0 transition

Updated 7 minutes ago

If your organization has signed the IAB Multi-State Privacy Agreement (MSPA), Osano can send the IAB US National Privacy string, known as USNAT, to your advertising partners. The string tells partners whether you gave each US visitor notice and whether that visitor opted out of the sale or sharing of their personal information and of targeted advertising.

You turn USNAT on from the IAB tab of a Cookie Consent configuration. It needs no code changes and nothing new on your banner. Osano builds the string from settings you already have and from the choices your visitors already make.

USNAT is for MSPA signatories and certified partners only. If your organization has not signed the MSPA, do not enable it. Your configuration keeps sending the US Privacy String (USPv1) as it does today.

Why the version is changing

USNAT is the IAB signal that MSPA signatories send to their advertising partners. In 2026 IAB updated the Multi-State Privacy Agreement and then simplified the signal to match. The result is version 3.0 of the US National Privacy specification.

The MSPA Technical Signaling Implementation Guidelines (version 1.6, effective September 2, 2026) set a transition period from version 2.0 to version 3.0 that ends on February 1, 2027.

Key dates

DateWhat happens
TodayOsano sends USNAT v2.0. The USNAT card on the IAB tab shows "USNAT v2.0".
January 2027Osano switches every configuration with USNAT enabled to v3.0. You are notified before the change.
January 31, 2027Last day v2.0 is compliant under the MSPA signaling guidelines.
February 1, 2027v3.0 is required per IAB MSPA.

What is different in v3.0

Version 3.0 is a shorter string that says the same things about sale, sharing, and targeted advertising.

In v2.0In v3.0
Four separate notice fieldsOne notice field
Three separate opt-out fields (sale, sharing, targeted advertising)One opt-out field covering all three
Fields for sensitive data, consumers under 18, and secondary-use consent, which Osano sends as "Not applicable"These fields are removed
MSPA mode fieldsThese fields are removed
No MSPA IDYour MSPA ID is included
No MSPA versionThe MSPA version is included. Osano sets this for you.
Global Privacy Control signalStill included

Osano already sets the four notice fields together and the three opt-out fields together in v2.0, so the meaning of your signal does not change when the fields are combined.

What stays the same

  • Your configuration. Your answer to the sell or share question, your Do Not Sell / Share settings, and your Marketing category carry over as they are.
  • Your visitors' experience. No new banner controls, and existing choices are kept.
  • How a visitor opts out. A Do Not Sell / Share opt-out, declining the Marketing category, or a Global Privacy Control signal each still count as an opt-out.
  • The US Privacy String (USPv1). If it is enabled, Osano keeps sending it, and its sale opt-out value still matches USNAT.

What you need to do

  1. Confirm your MSPA ID is correct. On the IAB tab, the USNAT card shows the ID you entered. Compare it with your entry in the IAB MSPA identification list. To change it, click Edit on the card. In v3.0, a string without your valid MSPA ID is not covered by the MSPA.
  2. Ask your ad partners about v3.0. Each partner decides when it reads the new version. Ask yours for their timing, particularly any that enforce opt-outs based on your string.
  3. Keep USPv1 on through the transition if you send it today. Turn it off only once your partners confirm they no longer need it.
  4. Publish any configurations with USNAT enabled after the release. This will update the version number for the string and send the updated signal design.

Checking your string after the switch

Run __gpp('ping', console.log) in your browser console from a US location and copy the gppString value. After the switch, section 7 reports version 3. Some public decoders may take time to add v3.0 support, so a decoder that cannot read the new section does not necessarily mean your string is wrong.

Frequently asked questions

Do I have to do anything for the switch to happen? Yes. Osano makes the change for every configuration with USNAT enabled and you will need to Publish any configs where this feature is enabled after that release.

Can I switch to v3.0 early, or stay on v2.0? There is no setting for the version. Osano switches all USNAT configurations together.

Will my visitors be asked for consent again? No. The change is to how the signal is encoded, and existing choices are kept.

We have not enabled USNAT. Does this affect us? No. This only applies to configurations with USNAT turned on. If you enable USNAT before the switch, your configuration starts on v2.0 and moves to v3.0 with everyone else.

What if one of my ad partners is not ready for v3.0? Contact Osano Support and tell us which partner. Keeping the US Privacy String on gives partners that still read it a matching opt-out signal.

Related articles

Was this article helpful?
Subscribe to receive updates on this article