Google Analytics on November 11, 2026 began warning properties when the email addresses, phone numbers and postal addresses they collect for advertising either fail to reach Google or arrive in a state too poor to use. The change appeared as a short entry on Google's "What's new in Google Analytics" page under the title "New diagnostic in Google Analytics for user-provided data issues," with a separate help page carrying the detail: two alerts, eight explanations for poor data quality, a table of error codes and a set of formatting rules for each type of identifier.
In Short
Google Analytics added alerts on November 11, 2026 that tell a property when its user-provided data, the emails, phone numbers and addresses sent through the Google tag or the Data Manager API, is missing or of poor quality. This matters to advertisers who feed that data into enhanced conversions and Customer Match, because identifiers that never arrive, or arrive badly formatted, cannot be matched to signed-in Google users. The alerts sit in the Admin area and in Task Assistant and point to a likely cause, from empty fields to pages served over HTTP, though Google gives no threshold for what counts as a "low PII rate."
What Google published
The release note is four sentences long. "We've launched a new diagnostic to alert users of issues with user-provided data (UPD) implementation," it begins, according to Google. "If your property fails to receive data or encounters quality issues, diagnostics appear in Google Analytics Admin and Data streams panels." The alerts, the note continues, help users "identify implementation issues, and determine if you need to update your tag configuration or change your collection methods for UPD."
Two links close the entry. One points to Google's overview of user-provided data. The other leads to a help page titled "Troubleshoot diagnostics for user-provided data collection" (answer 17141398), which repeats the release note's opening almost word for word and then sets out what the alerts actually say. That page carries no publication or update date.
The entry is the 19th dated release on Google Analytics' 2026 changelog and the second in November. It landed five days after Google released a beta of Data Manager inside Google Analytics on November 6, a hub in the Admin console for data streams, product links and imported customer data. Google's changelog entry for that earlier release says Data Manager can also be used to "address diagnostic alerts" and "monitor connection health."
Two alerts, one diagnostic
Google's release note speaks of "a new diagnostic," singular. The help page describes two distinct alerts, and they are of very different kinds. The first is binary: data is either arriving or it is not. The second is a judgement about quality, and it carries most of the documentation's weight.
According to Google, alerts fire "if Google Analytics detects issues with your UPD collection or personally identifiable information (PII) rates."
| Alert (Google's wording) | Condition, according to Google | Remedy Google names |
|---|---|---|
| "Your property is not yet receiving UPD from a Google tag or Data Manager API" | "While your property has successfully enabled UPD collection and acknowledged the terms of service, your property is not receiving the UPD." | Change the collection method to automatic collection, CSS selectors or manual code, through the Google tag, Google Tag Manager or Data Manager |
| "Your property's UPD has a low PII rate" | "Your property currently receives UPD, but the amount of PII isn't sufficient for utilization." | Eight sub-sections covering collection method, missing fields, empty values and formatting |
The first alert describes a specific failure. A property has switched the feature on and accepted Google's terms, yet nothing comes through. The remedy Google offers places the problem in collection rather than in Analytics itself: automatically collected methods, CSS selectors and manual code are the routes it lists.
The second alert is harder to pin down. What does "sufficient for utilization" mean in numbers? Google does not say. The page gives no percentage, no minimum volume and no definition of how a PII rate is calculated.
Eight explanations for a low PII rate
Under the second alert, the help page lists eight expandable sections. Each names a cause and, in most cases, a way to check for it.
| Section heading on Google's page | What it covers, according to Google |
|---|---|
| Add manual in-page code for better results | Properties using automatic collection "may receive a higher PII rate" with manual in-page code; links to guides for Google Tag Manager, CSS selectors or JavaScript variables with the Google tag, and the Data Manager API |
| Include missing user data field | Some events carry no UPD fields at all; "the UPD parameter wasn't transmitted in some instances" when the event tag fired |
| Update missing UPD values | The fields are sent, but "the data that you're sending is empty" |
| Update incorrect data formatting | Email, phone or address values fail format checks; error codes appear in place of a hashed value |
| Update missing required address fields | Address used as an identifier without the full set of fields, in the required order |
| Update email data field formatting | Emails "don't match with Google signed-in users because they're incorrectly formatted" |
| User phone number data field is incorrectly formatted | Numbers not in E164 format, missing the "+" prefix, or containing non-digit characters |
| User address data field is incorrectly formatted | Names not alphabetical, country not a two-letter code, postcode with the wrong number of digits |
The first section contains a notable concession. Automatic collection, in which the Google tag scans a page for anything resembling an email address or phone number, is the easiest route to switch on. Google's own troubleshooting page now says it may deliver a lower PII rate than code written into the page.
The explanation for empty values is equally practical. According to Google, "signed-in customers may not have re-entered their first-party information, or it may be collected on the previous page." A second cause concerns the selectors that tell the tag where to find the data: "CSS selectors may not work on all browsers or may function differently between mobile and desktop." For both the missing-field and empty-value problems, the page points to Google Tag Assistant to test each page where events fire, and suggests testing on different browsers and devices.
The codes in the em parameter
When user-provided data is working, the Google tag hashes it in the browser and sends the result to Google. The help page describes how to inspect that output in Tag Assistant: the string after "tv.1~em." should be a hashed value. If it is not, one of the codes below appears instead, which, according to Google, means "you have an error in your UPD set up."
| Code | Google's description |
|---|---|
| Empty or no error code | "If you can view "tv.1", it means that the em parameter is present but it's empty. User-provided data coverage isn't available on the page or the setup is incorrect." |
| e0 | "Field doesn't pass formatting validation checks. For example, email doesn't have "@", or phone number has "abcd"." |
| e1 | "Unsupported browser. This happens when the event occurs in certain legacy browsers. We expect this case to be rare." Google's page suggests triggering the conversion again in an updated Chrome browser. |
| e2 | "SHA256 failed. This could be because there were unexpected characters in the input into the hashing function." |
| e3 | "Web page isn't secure. Events only hash user data when the web page is served in HTTPS protocol not HTTP protocols." |
The e3 code is the bluntest of the set. A page served over plain HTTP will not hash user data at all, regardless of how the tag is configured. Google's broader formatting guidance in the same section is short: "Ensure that you're passing valid user email addresses (with an "@" symbol) and the phone numbers include a country code."
Address rules, and an example that does not fit the standard
The page's treatment of address data is the most prescriptive part of the documentation. According to Google, "at least one identifier of the 3 categories is required," listed as "Email (Preferred)," "Phone Number" and "Address." When address is the identifier, "the following fields must be captured in the following order":
- First name
- Surname
- Street Address
- City
- Region
- Country
- Postcode
A note directly underneath qualifies that list: "Street address, city, and region are optional additional keys to improve match rates." So three of the seven fields described as "must be captured" are, on the same page, optional. The note adds that when an email or phone number is also sent, Google will use it "to match to Google signed-in users even when the address is missing or incomplete."
The field-by-field formatting rules read as follows, according to Google:
| Field | Rule, in Google's words |
|---|---|
| Phone | "Format phone numbers according to the E164 standard and add the "+" prefix." and "Phone numbers should not include non-digit characters." |
| "Emails should be provided in a generally acceptable format (for example, email@gmail.com)." | |
| First name | "First name should be a string of alphabetical characters." |
| Surname | "Surname should be a string of alphabetical characters." |
| Country | "Country should be a 2-letter country code (for example, "UK") per the ISO 3166-1 alpha-2 standard." |
| Postcode | "Postcode should include the required number of digits, such as 5 digits for US postcodes." |
The country example deserves a closer look. Under ISO 3166-1 alpha-2, the code assigned to the United Kingdom is GB. "UK" is a reserved code, not the official assignment. A property following Google's example literally would send a value that does not match the standard the same sentence cites. Google's separate setup page for collecting the data through gtag.js also asks for a two-letter ISO alpha-2 country code and adds that phone numbers in E.164 format run to 11 to 15 digits with the "+" prefix.
The section closes with Google's broadest recommendation: "Sending a greater variety of distinct identifiers, including an email address alongside a phone number, ensures the best possible data collection quality."
How the diagnostic works, according to Google's documentation
Google's pages describe the path from setup to alert in six stages.
- Activation and terms. User-provided data collection is turned on for the property and the terms of service are acknowledged. The first alert presupposes both have happened.
- Tag configuration. According to Google's setup page for gtag.js, the setting sits under Admin > Data collection and modification > Data streams, then the web data stream, then Configure tag settings under the Google tag section, then "Allow user-provided data capabilities." An identification method is chosen there and saved. Google says the person making the change needs at least the Editor role on the property. That page still describes the feature as part of an open beta and subject to change.
- Collection method. Google's setup page offers three methods: automatic detection of user-provided data, specifying CSS selectors or JavaScript variables, and adding a code snippet that sets the user_data parameter on each event. The diagnostic page adds a fourth route, the Data Manager API, and links to its UserData reference.
- Hashing. The tag normalises and hashes the values with SHA256 before sending them, but only on pages served over HTTPS, according to the e2 and e3 descriptions.
- Assessment. Analytics checks whether user-provided data is arriving and whether enough of it is usable. No data produces the first alert; too little usable PII produces the second.
- Alert and verification. The alerts appear in the property's Data collection settings, at Admin > Data collection and modification > Data collection, and in Task Assistant. Google's suggested check is Tag Assistant, where the value after "tv.1~em." shows either a hash or an error code.
Three descriptions of where the alerts appear
Google's documents do not agree on location. The release note and the help page's opening paragraph say diagnostics appear in "Admin and Data streams panels." The help page's own alerts section, a few lines further down, names "Data collection settings (Admin > Data collection and modification > Data collection)" and Task Assistant. The setting that controls collection, meanwhile, lives under Data streams and the Google tag's configuration screen.
Task Assistant is not open to every role. When Google launched the tool on April 29, 2026, its dashboard was visible only to Administrator, Editor and Marketer roles, with Analyst and Viewer roles shut out. User-provided data collection already appeared there as a task under the "Enhance your reporting" category. The diagnostic page does not say which roles can see the alerts in either location.
A feature that has changed shape twice
The diagnostic arrives for a feature that has been in beta for a long time. Google Analytics began collecting user-provided data without requiring a user ID on March 20, 2024, in open beta. That was 966 days before the November 11 release note, by PPC Land's calculation, and Google's setup page still carries the open beta label.
The purpose of the data has also shifted. On November 5, 2025, Google launched new user-provided data infrastructure that refocused the feature on enhanced conversions and Customer Match and removed it as a reporting identity for session and user attribution. That article recorded that acknowledging the feature policy becomes permanent once collection is activated, that the feature is unavailable to properties in the Health industry category, and that early adopters on the legacy infrastructure faced migration in the second quarter of 2026.
The data now matters chiefly as an input to Google's advertising systems. When Nipoon Malhotra, Google's vice president for ads analytics, insights and measurement, set out a measurement package on September 10, 2026, it included moving Data Manager into Google Analytics and Display & Video 360, new built-in diagnostics and enhanced conversions in Analytics. Google attached an average 11% increase in Search conversions to enhanced conversions, a figure it reported about its own product. The November 11 alerts are a narrower piece of that plan: a readout of whether the raw material reaches Google at all.
Enhanced conversions in Google Ads went through their own consolidation earlier in the year. Google replaced three enhanced conversion methods with a single toggle in June 2026, after an April phase that let Google Ads accept user-provided data from website tags, Data Manager and API connections at the same time. The diagnostic page reflects that overlap. Among its related links are two Google Ads help pages on setting up enhanced conversions for web, through Google Tag Manager and through the Google tag.
Diagnostics inside Analytics are not new either. Google first introduced Tag Diagnostics across Tag Manager, Google Ads and Analytics in August 2024, and on June 30, 2025 it added them to the Analytics consent settings hub. The new alerts extend the same approach to a specific data type.
Hashing in the browser, encryption elsewhere
The diagnostic page describes a pipeline that depends on browser-side hashing. The e2 code exists because SHA256 can fail; the e3 code exists because hashing will not run over HTTP.
Google's other customer data product is moving in a different direction. In October, Google told Google Ads customers that from November 16, 2026, Google Ads Data Manager would stop requiring SHA-256 hashed customer data and accept encrypted data by default, with Google normalising and matching it inside a trusted execution environment. That notice covered CRM connections, cloud storage imports, file uploads and the Data Manager API. Analytics was not named.
The November 11 documentation says nothing about encryption. Whether the Data Manager API route into Analytics follows the encrypted default, or whether the Google tag's own hashing will change, is not addressed on either page.
One practitioner's reading
Matteo Zambon, founder of Tag Manager Italia, summarised the release on LinkedIn on November 21, 2026, ten days after the changelog entry. Zambon describes himself on the platform as a Google Tag Manager and analytics expert, a Microsoft Clarity ambassador and a product evangelist for Stape, a server-side tagging company. PPC Land reported his assessment of Google's visual tagging in August, when he estimated that it handled the easy 70 to 80% of tracking cases.
His post defines user-provided data plainly, as "the email, phone number and address a website sends to Google." It also offers a gloss on the second alert that Google's page does not: "UPD arrives, but the share of identifiers that can actually be used (the PII rate) is too low." That definition is his interpretation, not Google's. On collection methods, Zambon wrote that "Google also says that automatic collection may give a lower PII rate, and that manual in-page code can improve it."
He raised one organisational point that sits outside Google's documentation. Checking for the alert, Zambon wrote, also means finding out "who in the company can even open that screen." The point connects to the role limits on Task Assistant, and the help page does not say who sees the alerts.
Why this matters for advertisers and analysts
User-provided data is the material behind enhanced conversions and Customer Match. Every email that fails a format check, every phone number missing its country code and every page served without HTTPS lowers the share of records Google can link to a signed-in account, which is what the industry calls the match rate. The first alert surfaces the simplest of those failures, a property that receives nothing at all, inside the Admin area.
The value of the second alert is more limited. It reports that data quality is poor, then hands over a list of eight possible causes. The error codes still require Tag Assistant and page-by-page testing. And because Google publishes no threshold, a property owner cannot tell how far its data sits from the line that triggers the alert.
There is also the question of who sets the bar. Google's measurement announcements through 2026, from the data strength uplift metric to Data Manager, have encouraged advertisers to send more first-party data into its systems, and the diagnostic is Google's own assessment of whether that data meets Google's own standard of usefulness. The alerts say nothing about match rates achieved, conversions recovered or effects on bidding.
What the documentation does not say
Google does not define the PII rate, state the threshold that triggers the low-rate alert, give a lookback window or refresh frequency, or say whether alerts are also sent by email. It does not say which roles can see them, whether app data streams are covered, or why the release note describes one diagnostic while the help page lists two alerts.
Key facts
- Release note title: "New diagnostic in Google Analytics for user-provided data issues"
- Release note date: November 11, 2026
- Release note location: What's new in Google Analytics, support.google.com/analytics/answer/9164320
- Help page: "Troubleshoot diagnostics for user-provided data collection," support.google.com/analytics/answer/17141398 (undated)
- Setup page: "Collect user-provided data (gtag.js)," support.google.com/analytics/answer/14078702 (undated, open beta)
- Alert 1: "Your property is not yet receiving UPD from a Google tag or Data Manager API"
- Alert 2: "Your property's UPD has a low PII rate"
- Error codes: empty value after "tv.1", e0 (formatting), e1 (unsupported browser), e2 (SHA256 failed), e3 (page not on HTTPS)
- Alert locations named by Google: Admin and Data streams panels (release note); Admin > Data collection and modification > Data collection, and Task Assistant (help page)
- Identifier categories: Email (Preferred), Phone Number, Address
- Standards cited: E164 for phone numbers, ISO 3166-1 alpha-2 for country codes, SHA256 for hashing, HTTPS
- Position in changelog: 19th dated Google Analytics release of 2026, second in November
Timeline
- March 20, 2024 - Google Analytics begins collecting user-provided data without a user ID, in open beta
- August 2024 - Google introduces Tag Diagnostics across Tag Manager, Google Ads and Analytics
- June 30, 2025 - Tag Diagnostics added to the Google Analytics consent settings hub
- November 5, 2025 - New user-provided data infrastructure refocuses the feature on Enhanced Conversions and Customer Match
- December 9, 2025 - Google launches the Data Manager API for first-party data uploads
- April 29, 2026 - Task Assistant launches in Google Analytics for Administrator, Editor and Marketer roles
- June 2026 - Google Ads merges enhanced conversion methods into a single toggle
- August 22, 2026 - Matteo Zambon says Google's visual tagging covers the easy 70 to 80% of cases
- September 10, 2026 - Google announces Data Manager in Analytics, built-in diagnostics and enhanced conversions in Analytics
- October 18, 2026 - Google Ads Data Manager notice says hashing will no longer be required from November 16
- November 6, 2026 - Data Manager in Google Analytics released as a beta
- November 11, 2026 - Google Analytics release note announces the user-provided data diagnostic
- November 16, 2026 - Date set for Google Ads Data Manager to accept encrypted customer data by default
- November 21, 2026 - Matteo Zambon summarises the diagnostic on LinkedIn
Related PPC Land coverage
- Google Analytics refocuses user-provided data on ads conversions - the November 2025 infrastructure change that tied user-provided data to Enhanced Conversions and Customer Match and removed it from reporting identity.
- GA4 now collects user-provided data without a user ID - the March 2024 open beta that let properties collect emails and phone numbers without generating a user ID.
- Google Analytics Data Manager: duplicate Ads setups can log conversions twice - the November 6, 2026 beta of Data Manager inside Analytics, with its connection map and Fix buttons.
- Google Analytics Task Assistant guides property setup with step-by-step tasks - the April 2026 launch of the task list where the new alerts also appear, and its role restrictions.
- Google adds Tag Diagnostics to Analytics consent settings hub - the June 2025 extension of Tag Diagnostics into the Analytics consent settings.
- Google Ads Data Manager stops requiring hashed customer data November 16 - Google's move from SHA-256 hashing to encrypted uploads in Google Ads Data Manager.
- Google kills 3 enhanced conversion methods, replaces all with single toggle - the June 2026 consolidation of enhanced conversions for web and leads.
- Google's data strength uplift metric quantifies first-party data in Google Ads - the September 2026 measurement package that brought Data Manager and enhanced conversions into Analytics.
- Google's visual tagging covers the easy 70 to 80% of cases, Zambon says - Matteo Zambon's August 2026 assessment of Google's tagging changes.
- Google launches Data Manager API to centralize first-party data uploads - the December 2025 launch of the API that is now one of the routes for user-provided data into Analytics.
Summary
Who: Google Analytics, affecting advertisers, agencies and analysts whose properties collect user-provided data (emails, phone numbers and postal addresses) through the Google tag, Google Tag Manager or the Data Manager API. Tag Manager Italia founder Matteo Zambon commented on the release.
What: A new diagnostic with two alerts, one for properties that have enabled user-provided data but receive none, and one for properties whose data has a low PII rate. A help page lists eight possible causes, an error-code table with five entries (empty, e0, e1, e2, e3) and formatting rules for each identifier, including an ISO country example ("UK") that does not match the standard's code for the United Kingdom.
When: The release note is dated November 11, 2026. The help page is undated. Zambon's post followed on November 21, 2026.
Where: The release note says alerts appear in the Admin and Data streams panels; the help page names Admin > Data collection and modification > Data collection, and Task Assistant.
Why: User-provided data feeds enhanced conversions and Customer Match, and identifiers that are missing, empty or malformed cannot be matched to signed-in Google users. Google does not define the PII rate or the threshold that triggers the second alert.
Discussion