Google has named Oklahoma, Louisiana, Alabama and Vermont as the next four US states whose privacy laws its advertising products will account for. A Google AdSense Help Center page dated November 16, 2026 says the four states "will have privacy law provisions coming into effect" on or after January 1, 2027, and that publishers can apply Google's Restricted Data Processing mode to them, including through the IAB's GPP National v2 string. A second AdSense page, on US state regulations messages, now lists 24 states, and two Google Ad Manager pages set out which consent strings Ad Manager reads and what happens to an ad request once restricted processing is switched on.

The four-state page is one of two AdSense documents dated November 16 on the new laws. Its single date is looser than the statutes behind it: Alabama's law takes effect on May 1, 2027, and Vermont's on January 1, 2028, according to analyses by Venable and Davis+Gilbert.

In Short

Google has listed Oklahoma, Louisiana, Alabama and Vermont as the next US states whose privacy laws its ad products will account for, and its AdSense consent messages now cover 24 states. That matters to publishers earning from AdSense or Ad Manager, because the setting that switches off ad personalization, and the consent strings that trigger it, decide how much user data reaches advertisers in those states. The new pages do not say Google will apply anything automatically in Oklahoma or Alabama, whose laws, according to law firm analyses, do not require businesses to honor browser opt-out signals, and Alabama's law starts on May 1, 2027 rather than January 1. Ad Manager, meanwhile, reads only five state-specific sections of the IAB's consent string and still accepts a format the IAB retired in January 2024.

What the November 16 page says

The page is titled "Upcoming US states with comprehensive privacy laws" and sits at answer 18821562 in the AdSense Help Center. It contains four paragraphs, reproduced here in full because they are the whole of Google's statement on the four states.

"On or after January 1, 2027, Oklahoma, Louisiana, Alabama and Vermont will have privacy law provisions coming into effect. Google's approach in these states is similar to that of existing US states with active comprehensive laws. Activating Restricted Data Processing (RDP) mode turns off ad personalization, which may assist publishers in honoring opt-outs for targeted advertising and avoiding activities that could be considered a 'sale' or 'sharing' of user data."

"Publishers can also choose to send RDP via GPP National v2, which supports these new states."

"Please note that publishers should still work with their legal teams to understand if RDP is the appropriate solution for their compliance. Publishers who currently leverage the RDP should work with their legal teams to understand if they should expand their use of RDP in additional states."

The last sentence is the operative one. It places the decision about Oklahoma, Louisiana, Alabama and Vermont with publishers and their lawyers. A year ago Google took a different line for a different batch of states: in November 2025 it said account-level RDP settings would apply automatically to traffic from Indiana, Kentucky and Rhode Island from January 1, 2026. The November 16 page contains no equivalent statement.

A separate AdSense page, also dated November 16 and titled "Upcoming US states with universal opt-out mechanism," covered only two of the four states. It said Google would receive Global Privacy Control signals directly from users in Louisiana and Vermont from November 17, 2026 and switch those ad requests into RDP mode. Oklahoma and Alabama do not appear on it.

Four laws, four calendars

The four statutes were all signed in 2026, and they do not share a start date.

State Law Signed Effective date Opt-out signal requirement Gap after Google's January 1, 2027 date
Oklahoma SB 546 March 20, 2026, Governor Kevin Stitt January 1, 2027 None (Mayer Brown, Bass Berry) 0 days
Louisiana Louisiana Data Privacy Act, SB 386 May 29, 2026, Governor Jeff Landry January 1, 2027 Disputed (Future of Privacy Forum: not referenced; Hunton: authorized-agent signal) 0 days
Alabama Alabama Personal Data Protection Act, HB 351 April 17, 2026, Governor Kay Ivey (Hunton; Freshfields gives April 16) May 1, 2027 None (Hunton, Freshfields) 120 days
Vermont Vermont Data Privacy and Online Surveillance Act, S.71 June 16, 2026, Governor Phil Scott January 1, 2028 Required (Koley Jessen, Davis+Gilbert) 365 days

Effective dates are those given by both Venable (July 30, 2026) and Davis+Gilbert (July 7, 2026), which agree on all four. Signing dates for Louisiana and Vermont come from the Future of Privacy Forum, Hunton and Koley Jessen. Gaps are PPC Land calculations.

Oklahoma

Oklahoma's law, SB 546, was signed by Governor Kevin Stitt on March 20, 2026, according to Mayer Brown and Bass Berry. The House passed it on February 19, 2026 by 84 votes to 4, according to an analysis by Troutman Amin published in the National Law Review, which also says a House amendment pushed the start from July 1, 2026 to January 1, 2027. The law applies to businesses that control or process the data of at least 100,000 Oklahoma consumers, or of at least 25,000 while deriving more than 50% of gross revenue from selling personal data, according to all three analyses.

Consumers get rights to access, correct, delete and port their data, and to opt out of targeted advertising, sales and certain profiling. A "sale" covers only exchanges for monetary consideration, a narrow definition, according to Mayer Brown and Bass Berry. The attorney general enforces the law exclusively, with a 30-day cure period that Bass Berry and Troutman Amin say does not sunset, and civil penalties of up to $7,500 per violation. On signals the three analyses agree: the law does not require businesses to recognize universal opt-out preference signals such as Global Privacy Control.

Alabama

Alabama's Personal Data Protection Act, HB 351, passed both chambers unanimously on April 7, 2026, according to Burr & Forman. Hunton and Burr & Forman date Governor Kay Ivey's signature to April 17, 2026; Freshfields and PYMNTS give April 16. The law takes effect on May 1, 2027.

Its reach is wide on one measure and narrow on others. It covers businesses that process the data of more than 25,000 Alabama consumers, excluding data handled solely to complete a payment, or that derive more than 25% of gross revenue from selling personal data regardless of how many consumers are involved, according to Freshfields and Burr & Forman. Freshfields says the 25,000 figure ties Montana's as the lowest threshold in the country. Davis+Gilbert's summary table lists different thresholds, 35,000 consumers or 5,000 with more than 25% of revenue from sales. Businesses with fewer than 500 employees are exempt if they do not sell personal data, according to MultiState.

The definition of a sale is narrow and carves out some analytics and marketing services arrangements, according to Burr & Forman and Freshfields. The law requires no data protection assessments and, according to Hunton and Freshfields, no recognition of opt-out preference signals. The attorney general enforces it exclusively, with a 45-day right to cure and penalties of up to $15,000 per uncured violation, according to Freshfields.

Louisiana and Vermont

Louisiana's law takes effect on January 1, 2027. Analyses differ on whether its text covers browser signals: the Future of Privacy Forum says it does not reference opt-out preference signals, while Hunton describes an authorized-agent route that can run through a technology signal such as Global Privacy Control. Vermont's S.71 is the only one of the four that plainly requires signal handling: Koley Jessen and Davis+Gilbert say businesses must treat such signals as opt-out requests. It does not apply until January 1, 2028.

A signal list that tracks the statute books

Set against the Future of Privacy Forum's effective-dates chart, dated July 10, 2026, Google's choice of states for its browser-signal handling follows a visible pattern. The chart marks 12 of the 20 earlier laws as requiring businesses to honor opt-out preference signals. PPC Land's coverage records Google treating Global Privacy Control as an opt-out in 11 of those 12: Colorado first, then Connecticut, Montana, Nebraska, New Hampshire, Texas, Minnesota, New Jersey and Maryland on June 30, 2025, then Delaware and Oregon on November 17, 2025. California, the twelfth, has not been part of those announcements.

None of the eight states the chart marks "No" for signals (Florida, Indiana, Iowa, Kentucky, Rhode Island, Tennessee, Utah and Virginia) appears in Google's GPC announcements, and neither do Oklahoma or Alabama. Vermont, whose law requires signal handling, has been added. Louisiana is the exception that the analyses leave open. Google's pages give no reason for the split. The comparison is PPC Land's, built from the chart and PPC Land's own reporting.

Twenty-four states on the messages page

The AdSense page "About US state regulations messages," answer 10961479, carries no date. It describes the message type in one sentence: "The US state regulations message type is displayed to users who are subject to privacy legislation specific to the state in which they're located." It adds a caution: "It is your responsibility to make sure your messages meet legal requirements."

The applicability list at the top of the page names 24 states, including all four on the November 16 page. When AdSense introduced the messages in June 2024 they covered five: California, Virginia, Colorado, Connecticut and Utah. In December 2025, Google added Indiana, Kentucky and Rhode Island along with a targeting option labeled "All current and future supported US States."

The page's section on GPP splits the states by which part of the consent string carries their choices: "The US National section will be used to store and transmit the choices of users in the following US states: California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, and Virginia. The Florida section will be used to store and transmit the choices of users in Florida." That paragraph names 20 states. The four new ones are on the applicability list but absent from it, so the page does not say which section will carry their users' choices. The November 16 page says only that GPP National v2 "supports these new states."

State Law (as named by source) In effect from Opt-out signal rule GPP section Google's messages use Google GPC handling began
Alabama Alabama Personal Data Protection Act May 1, 2027 No Not named None
California California Consumer Privacy Act (CPRA) January 1, 2023; Opt Me Out Act (AB 566) January 1, 2027 Yes US National Not in announcements covered
Colorado Colorado Privacy Act July 1, 2023 Yes, from July 1, 2024 US National Before June 30, 2025
Connecticut Connecticut Data Privacy Act July 1, 2023; amendments July 1 and October 1, 2026 Yes, from January 1, 2025 US National June 30, 2025
Delaware Delaware Personal Data Privacy Act January 1, 2025 Yes, from January 1, 2026 US National November 17, 2025
Florida Florida Digital Bill of Rights Act July 1, 2024 No Florida None
Indiana Indiana Consumer Data Protection Act January 1, 2026 No US National None
Iowa SF 262 January 1, 2025 No US National None
Kentucky Kentucky Consumer Data Protection Act January 1, 2026; amendment July 1, 2027 No US National None
Louisiana Louisiana Data Privacy Act January 1, 2027 Disputed Not named From November 17, 2026
Maryland Maryland Online Data Privacy Act October 1, 2025; amendment July 1, 2026 Yes, with drafting ambiguity US National June 30, 2025
Minnesota Minnesota Consumer Data Privacy Act July 31, 2025 Yes US National June 30, 2025
Montana Montana Consumer Data Privacy Act October 1, 2024 Yes, from January 1, 2025 US National June 30, 2025
Nebraska Nebraska Data Privacy Act January 1, 2025 Yes US National June 30, 2025
New Hampshire SB 255 January 1, 2025; amendment January 1, 2027 Yes, from January 1, 2025 US National June 30, 2025
New Jersey S332 January 15, 2025 Yes, from July 15, 2025 US National June 30, 2025
Oklahoma SB 546 January 1, 2027 No Not named None
Oregon Oregon Consumer Privacy Act July 1, 2024 Yes, from January 1, 2026 US National November 17, 2025
Rhode Island Rhode Island Data Transparency and Privacy Protection Act January 1, 2026 No US National None
Tennessee Tennessee Information Protection Act July 1, 2025 No US National None
Texas Texas Data Privacy and Security Act July 1, 2024 Yes, from January 1, 2025 US National June 30, 2025
Utah Utah Consumer Privacy Act December 31, 2023; amendments July 1, 2026 and January 1, 2027 No US National None
Vermont Vermont Data Privacy and Online Surveillance Act January 1, 2028 Yes Not named From November 17, 2026
Virginia Virginia Consumer Data Protection Act January 1, 2023; amendment July 1, 2026 No US National None

Sources: effective dates and signal rules for the 20 earlier laws from the Future of Privacy Forum chart "Effective Dates for Broad State Privacy Laws," as of July 10, 2026; for the four 2026 laws, Venable, Davis+Gilbert, Mayer Brown, Bass Berry, Hunton, Freshfields, Koley Jessen and the Future of Privacy Forum. GPP sections from Google's AdSense messages page. GPC column from PPC Land coverage and Google's November 16 page for Louisiana and Vermont.

The messages page records exactly how Google's own consent tool fills in the GPP string. When the "Do Not Sell or Share My Personal Information" link appears on a page:

  • "SharingNotice, SaleOptOutNotice, SharingOptOutNotice, and TargetedAdvertisingOptOutNotice are set to indicate that notice was provided."
  • "SaleOptOut, SharingOptOut, and TargetedAdvertisingOptOut are set to indicate the user did not opt out."
  • "MspaCoveredTransaction is set to 'No.'"

If the user opts out, "SaleOptOut, SharingOptOut, and TargetedAdvertisingOptOut are updated to indicate that the user opted out," and "All other fields are set to 'Not applicable,' including those for SensitiveDataProcessing and KnownChildSensitiveDataConsents." The page then puts the downstream question back on publishers: "Publishers must work with their ad partners to understand how they respect GPP signals."

The message itself has three parts, according to the page: the link, a Confirm page titled "Opt out of the sale or sharing of personal information," and two buttons. Dismiss closes the message "without opting out," while Opt out records the choice: "When users click Opt out, the message communicates their opt-out status to Google." The page also notes that, with the California Privacy Rights Act in effect, Google automatically changed default CCPA message text to read "Do Not Sell or Share My Personal Information." Publishers who had written custom text were told to revise it themselves.

What Ad Manager will read

The Ad Manager page "Supporting the IAB's Global Privacy Platform," answer 14117049, is undated and uses two names for the same framework: "Platform" in its title and "Global Privacy Protocol (GPP)" in its text. It describes GPP as "a standardized framework for storing and passing user privacy consent preferences," developed by IAB Tech Lab.

Its central rule is a whitelist: "Ad Manager only accepts the following strings within GPP: US National, California, Colorado, Connecticut, Florida, Virginia." The page then names what it rejects: "Ad Manager does not accept IAB Canada TCF, US Privacy String, US State Utah, or IAB Europe TCF as part of GPP support."

That list is shorter than the framework. IAB Tech Lab has kept adding state sections, including sections for Maryland, Indiana, Kentucky and Rhode Island proposed for public comment in October 2025. Read literally, Ad Manager's whitelist means that for 19 of the 24 states on the AdSense messages list, a state-specific section is not among the strings it accepts, and the US National section is the route the page provides. Utah shows the effect most clearly: Google's own messages store Utah users' choices in the US National section, and Ad Manager declines Utah's dedicated section.

Item What the Ad Manager page says
GPP sections accepted US National, California, Colorado, Connecticut, Florida, Virginia
Rejected within GPP IAB Canada TCF, US Privacy String, US State Utah, IAB Europe TCF
GPP National versions "Starting in September 2025, Google will support GPP National v2. We will also continue to support GPP National v1."
GPP v1.0 framework strings Not supported; error GPP_ERROR_STRING_IS_DEPRECATED_SPEC in the publisher console
How strings reach Ad Manager Ad request URL parameters gpp={gpp string} and gpp_sid={gpp section id}
EEA, UK and Switzerland IAB Europe TCF through a certified CMP; "TCF strings sent through the GPP will not be accepted"
TCF version named IAB Europe TCF v.2.3
US Privacy String Deprecated by IAB in January 2024; Ad Manager "will continue to read" it
Multi-State Privacy Agreement Signature not required; Ad Manager certified under IAB Privacy's MSPA Certified Partner Program
Is GPP required? "Use of GPP is not required by Google"

The TCF line matters for publishers with European traffic. Their consent management platform must keep generating IAB Europe TC strings to the v2.3 specification, separately from GPP, in line with the February 28, 2026 TCF v2.3 deadline Google set in November 2025.

On contracts, the page says: "Google does not require publishers to sign the IAB Multi-State Privacy Agreement (MSPA) in order to work with Google. Ad Manager is certified under IAB Privacy's Multi-State Privacy Agreement (MSPA) Certified Partner Program (CPP). MSPA Certified Partners are permitted to process MSPA Covered Transactions without signing the MSPA." Google's own consent message, as noted above, sets the MspaCoveredTransaction field to "No" when it shows the opt-out link.

When a GPP string switches on RDP

For each accepted section, the page lists the fields Google reads and the answers that trigger restricted processing. Each list is introduced with the same sentence: "Google will trigger restricted data processing (RDP) if any the following criteria are met."

GPP section RDP triggers, verbatim Google's statement on scope
US National "User opted out of Sale of the Consumer's Personal Information." "User opted out of Sharing of the Consumer's Personal Information." "User opted out of Processing the Consumer's Personal Data for Targeted Advertising." "Google only reads the above fields of the US National string."
California "User opted out of Sale of the Consumer's Personal Information." "User opted out of Sharing of the Consumer's Personal Information." "Google only reads the above fields of the US States string for California."
Colorado, Connecticut, Virginia "User opted out of Sale of the Consumer's Personal Information." "User opted out of Processing the Consumer's Personal Data for Targeted Advertising." "Google only reads the above fields of the US States string for Colorado, Connecticut, Virginia"
Florida "User opted out of Sale of the Consumer's Personal Information." "User opted out of Processing the Consumer's Personal Data for Targeted Advertising." "Google only reads the above fields of the US States string for Florida."

These are the same sections and triggers that AdSense adopted when it added GPP National v2 support in October 2025. The Ad Manager page applies them to the larger platform.

Minors

A second set of rules covers children and teenagers. Two outcomes are possible: a request is "marked for child age treatment," or it triggers RDP. The phrase "consent or no consent" in Google's wording means either answer in the field produces the flag.

GPP section Marked for child age treatment, verbatim Triggers RDP, verbatim
US National "Consent or no consent to Process the Consumer's Personal Information or Sensitive Information for Consumers Younger Than 13 Years of Age." "No consent to Process the Consumer's Personal Information or Sensitive Information for Consumers from Age 13 to 16." "No consent to Process the Consumer's Personal Information or Sensitive Information for Consumers from Age 16 to 17."
California "Consent or no consent to Sell the Personal Information of Consumers Less Than 16 years of Age" and "Consent or no consent to Share the Personal Information of Consumers Less Than 16 years of Age" None listed
Colorado, Virginia "Consent or no consent to Process Sensitive Data from a Known Child" None listed
Connecticut "Consent or no consent to Consent to Process Sensitive Data from a Known Child" "No consent to Sell the Personal Data of Consumers At Least 13 Years of Age but Younger Than 16 Years of Age" and "No consent to Process the Personal Data of Consumers At Least 13 Years of Age but Younger Than 16 Years of Age for Purposes of Targeted Advertising."
Florida "Consent or no consent to Process the Consumer's Personal Data or Sensitive Data for Consumers Younger Than 13 Years of Age" "No consent to Process Sensitive Data of Consumers At Least 13 Years of Age but Younger Than 16 Years of Age" and "No consent to Process the Sensitive Data of Consumers At Least 16 Years of Age but Younger Than 18 Years of Age"

There is a gap in Google's own tooling here. "Google's consent management solution does not support the ability to collect KnownChildSensitiveDataConsents fields," the page says, which matches the messages page setting those fields to "Not applicable." Google instead recommends that publishers keep using its tools for tagging sites, apps and requests for child age treatment, which it ties to compliance with COPPA "and other relevant regulations." Those tools are changing: in May 2026, Google introduced TFAT, a tag for age treatment with CHILD, TEEN and UNSPECIFIED values, to replace the older child-directed and under-age-of-consent tags in future versions of its publisher tag and SDKs.

What restricted processing does to an ad request

The fourth page, "Helping publishers comply with U.S. states privacy laws" (Ad Manager answer 9561023, undated), gives the clearest description of RDP among the four documents: "When an RDP signal is present, Ad Manager will not serve ads that are based on a user's prior behavior and will send a non-personalized ad request to bidders." In practice, the bid request that goes to outside buyers is a non-personalized one, and ads chosen on past behavior drop out for that impression.

The setting is not limited to the states with laws. "For traffic in US states, or any region globally, publishers have the ability to configure restricted data processing (RDP)," the page says.

The page also records Google's contractual position. "Google already offers data protection terms pursuant to the General Data Protection Regulation (GDPR) in Europe. We are now also offering service provider terms, which will supplement those existing data protection terms, effective January 1, 2023." For customers on Google's online contracts and updated platform contracts, those terms are incorporated through the data protection terms, and the page says there is "no action required." It restates two policy positions: "we do not sell personal information," and "we don't use sensitive information like health, race, religion, or sexual orientation to personalize ads."

The US Privacy String gets a longer life in Ad Manager than at the IAB. "We acknowledge that the IAB deprecated the US Privacy String in January 2024 in favor of GPP. However, the US Privacy String will continue to be read by Ad Manager in order to provide backward support to partners. It may be deprecated in future releases." No date is given for that step, and the GPP page frames the move as a recommendation: "It is recommended that publishers and CMPs move forward with GPP strings, instead of the US Privacy String, if they choose to use an IAB framework for US state privacy law compliance."

How it works, according to Google's documentation

Taken together, the four pages describe the following path from a user's choice to a restricted ad request.

  1. Opt-out link. A publisher using Google's US state regulations message shows a "Do Not Sell or Share My Personal Information" link to users in the 24 listed states, using the formatting and settings the publisher selected.
  2. Confirm page. A click opens the "Opt out of the sale or sharing of personal information" dialog, with the site's logo if one was added, and two buttons, Dismiss and Opt out.
  3. Signal to Google. Opt out "communicates their opt-out status to Google" and updates SaleOptOut, SharingOptOut and TargetedAdvertisingOptOut in the GPP string, with other fields set to "Not applicable."
  4. Other consent tools. Publishers can instead use a third-party or in-house CMP to pass GPP signals, or the older US Privacy String. GPP data reaches Ad Manager through the gpp and gpp_sid ad request parameters, and only the six accepted sections are read.
  5. Per-request tags. Alternatively, RDP can be activated "for only some users, via GPT and AdSense/Ad Exchange asynchronous ad tags on a per-request basis," which the page links to sites showing a "Do Not Sell My Personal Information" link.
  6. Buyer controls. The "Review your ad partners" control, found under Privacy & messaging, then US states regulations, then settings, lets a publisher choose which third-party buyers may serve ads to eligible users in the applicable states.
  7. The restricted request. Once RDP applies, Ad Manager does not serve behavior-based ads and sends a non-personalized ad request to bidders.

The compliance page says there are "multiple ways" to enable RDP and numbers two of them: the consent management platform route and publisher ad tags. A link at the foot of the page points to a separate article on restricted data processing settings.

Why it matters

For publishers, the November 16 page shifts work rather than removing it. Google says its approach in the four states "is similar" to the existing ones, yet the only instruction it gives is to consult legal teams on whether to extend RDP. The four laws also arrive in stages over 12 months, from January 1, 2027 for Oklahoma and Louisiana to May 1, 2027 for Alabama and January 1, 2028 for Vermont, while Google's page groups them under a single date.

The Ad Manager whitelist is the more technical risk. A consent platform that records a Utah, Maryland or Tennessee user's choice only in that state's own GPP section is sending something Ad Manager says it does not accept, which leaves the US National section as the working route for most states. The messages page already tells publishers to check how their ad partners "respect GPP signals."

For advertisers, each added state enlarges the share of US impressions that can run without personalization, and the pattern in Google's browser-signal handling suggests where automatic opt-outs are likely to apply. On the evidence of these pages and the law firm analyses, Oklahoma and Alabama appear set to depend on publishers and their consent tools rather than on a browser setting.

The pages leave several things unsaid. None gives a date for Ad Manager's own reading of GPP for Oklahoma, Louisiana, Alabama or Vermont, or says which GPP section Google's messages will use for those states. Google does not explain why its date for Alabama and Vermont precedes their laws, why Utah's section is refused, or when the US Privacy String will stop being read. The two Ad Manager pages and the messages page carry no publication or update dates.

Key facts

  • Source documents: "Upcoming US states with comprehensive privacy laws," Google AdSense Help, answer 18821562, dated November 16, 2026; "About US state regulations messages," Google AdSense Help, answer 10961479, undated; "Supporting the IAB's Global Privacy Platform," Google Ad Manager Help, answer 14117049, undated; "Helping publishers comply with U.S. states privacy laws," Google Ad Manager Help, answer 9561023, undated
  • Source URLs: https://support.google.com/adsense/answer/18821562 ; https://support.google.com/adsense/answer/10961479 ; https://support.google.com/admanager/answer/14117049 ; https://support.google.com/admanager/answer/9561023
  • Feature names: Restricted Data Processing (RDP) mode; US state regulations messages; "Review your ad partners" control; GPP National v2
  • States named on the November 16 page: Oklahoma, Louisiana, Alabama, Vermont, provisions "on or after January 1, 2027"
  • States on the messages applicability list: 24
  • GPP sections Ad Manager accepts: US National, California, Colorado, Connecticut, Florida, Virginia
  • Rejected within GPP: IAB Canada TCF, US Privacy String, US State Utah, IAB Europe TCF
  • Error code for GPP v1.0 strings: GPP_ERROR_STRING_IS_DEPRECATED_SPEC
  • Ad request parameters: gpp, gpp_sid
  • Service provider terms: effective January 1, 2023
  • US Privacy String: deprecated by the IAB in January 2024; still read by Ad Manager
  • Oklahoma: SB 546, signed March 20, 2026, effective January 1, 2027
  • Alabama: Alabama Personal Data Protection Act, HB 351, effective May 1, 2027
  • Louisiana: Louisiana Data Privacy Act, SB 386, effective January 1, 2027
  • Vermont: Vermont Data Privacy and Online Surveillance Act, S.71, effective January 1, 2028

Timeline

Summary

Who: Google, through two AdSense Help Center pages and two Ad Manager Help Center pages, and the publishers and advertisers whose ad requests come from 24 US states with comprehensive privacy laws. The state legislatures of Oklahoma, Louisiana, Alabama and Vermont passed the four newest laws.

What: Google named Oklahoma, Louisiana, Alabama and Vermont as states with privacy provisions arriving on or after January 1, 2027, said RDP can be sent for them through GPP National v2, and listed 24 states for its US state regulations messages. The Ad Manager pages set out which GPP sections it reads, which it rejects, the exact fields that trigger restricted processing and child age treatment, and what RDP does to an ad request.

When: The four-state page is dated November 16, 2026. The other three pages are undated. The laws take effect on January 1, 2027 in Oklahoma and Louisiana, May 1, 2027 in Alabama and January 1, 2028 in Vermont.

Where: AdSense and Ad Manager traffic from the 24 listed US states, with RDP also available for any region globally.

Why: New state laws give consumers the right to opt out of targeted advertising and data sales. Google offers restricted processing and consent-string handling as tools publishers can use, while placing the decision on whether to use them in each state with publishers' legal teams.