Google Analytics has spent the autumn adding admin and data-quality tooling more than new reports. The biggest items are Data Manager (beta) on 6 November 2026, a diagnostic for user-provided data problems on 11 November 2026, and hostname Include filters on 21 September 2026. If you run GA4 for a business with several domains, apps or a large team, these change how you keep the property clean and who controls it.
Key takeaways
- Data Manager (beta, 6 November 2026) puts product links, data streams and first-party data in one admin hub, and lets you act on diagnostic alerts and watch connection health.
- The user-provided data diagnostic (11 November 2026) surfaces in Admin and Data streams, so assign someone to look at those panels weekly.
- Hostname Include filters (21 September 2026) let you allowlist domains, but they block events with empty hostnames and skip Measurement Protocol events, so test before you rely on them.
- The User Groups Admin API (5 October 2026) is for large organisations that manage access at scale and need User Admin or Org Admin permissions.
- App conversion reporting (29 September 2026) may not be available to every property, so check eligibility before planning around it.
- Most of this is admin work a capable in-house team can do. Bring in a partner for multi-domain filter design, user-provided data implementation and access governance across many properties.
What did Google Analytics release between September and November 2026?
Seven releases matter for most teams. Some are small, some touch how data is collected, and one is still in beta. The table sorts them by who should care and what to do first.
| Release date | Change | Who it affects | First action |
|---|---|---|---|
| 9 September 2026 | Dashboards available in Google Analytics | Anyone building recurring views for stakeholders | Try one dashboard for a real weekly meeting |
| 21 September 2026 | Hostname Include filters | Teams with spam traffic or several approved domains | List every legitimate hostname, then test |
| 29 September 2026 | App conversions in conversion reports and independent attribution settings (may not be available to every property) | Google Ads customers with apps | Confirm eligibility with your support team |
| 5 October 2026 | User Groups Admin API | Large organisations with many users and properties | Review whether manual access changes are worth scripting |
| 6 November 2026 | Data Manager (beta) | Admins and anyone who owns links and streams | Open it and compare against your current setup |
| 11 November 2026 | User-provided data diagnostics | Teams sending user-provided data | Read the alerts in Admin and Data streams |
| 18 November 2026 | Firebase agent skills for the Google Analytics for Firebase (GA4F) SDK | App developers | Pilot on a low-risk screen-view change |
The pattern is clear enough. Google is giving admins more ways to see problems and fewer reasons to maintain brittle manual lists. That favours teams who actually look at their admin panels.
How does Data Manager in Google Analytics (beta) change admin work?
Data Manager is a single place in the admin console for product links, data streams and first-party data. The notes also say you can use it to address diagnostic alerts and monitor connection health. It launched as a beta on 6 November 2026.
That sounds modest, but think about how these things are usually spread out. A product link sits in one admin screen, a data stream in another, and the first-party data setup lives wherever whoever built it left it. When something stops flowing, the first hour goes on finding where to look. A hub that shows link and connection health in one view shortens that hour.
The practical value is for the person who inherits a property. Open Data Manager and you should be able to answer four questions quickly: what is connected, what is sending data, what is raising alerts, and who set it up. If you cannot answer those from the hub, that gap is your first documentation task.
Two cautions. It is a beta, so labels, layout and capabilities may change, and you should not rewrite your runbooks around screen names that might move. And a hub shows state; it does not fix a bad link or a mis-tagged stream. Treat it as a faster way to find problems, not a replacement for someone owning them.
What not to do: do not make configuration changes to production links just to explore the new screen. Look first, compare with your documented setup, and change things through your normal review process.
What does the user-provided data diagnostic tell you?
On 11 November 2026 Google launched a diagnostic that alerts you to problems with your user-provided data (UPD) implementation. If a property fails to receive data or has quality issues, the alerts appear in the Admin area and in the Data streams panels. The notes say they help you work out whether to update your tag configuration or change how you collect UPD.
User-provided data is the information a user gives you, such as an email address entered in a form, which you pass to Google in a controlled way. It is easy to get slightly wrong. A form field gets renamed in a site release, a consent condition changes, or a tag fires before the value exists. Nothing breaks loudly. Match quality just drifts.
Before this diagnostic, you often found out through a downstream symptom, like a conversion count that looked thin. Now there is a place that should tell you earlier. That is useful, but only if someone reads it.
A simple routine works:
- Name one owner for the alerts, not a shared inbox.
- Check Admin and the Data streams panels weekly, and after every release that touches forms or checkout.
- When an alert appears, decide first whether it is a tag configuration problem or a collection method problem. The notes frame the choice that way, and it points you to different teams.
- Record what you changed and the date, so you can tell later whether the alert cleared because of your fix.
If you do not send user-provided data at all, you can ignore this. Do not start collecting it just because a diagnostic exists. That decision belongs with your privacy and legal teams, and the vendor documentation on user-provided data is the right starting point for them.
Should you use hostname Include filters in GA4?
Probably yes, if you have been fighting spam traffic, but with care. Since 21 September 2026, Google Analytics supports Include data filters for hostnames. You can list the domains that are allowed to send event data to your property. Before that you could only exclude, which meant adding each new spam source after it showed up.
An allowlist flips the maintenance burden. You maintain the short list of domains you own and trust, rather than chasing an endless list of ones you do not.
The notes give two behaviours that can bite you:
- Measurement Protocol events are not filtered. Hostname Include filters are not applied to events sent from the Measurement Protocol, so that data stays unblocked. Do not assume the filter covers server-side events.
- Empty hostnames are blocked. An Include filter automatically blocks events with empty hostnames, such as gtag.js traffic. Google's reasoning is that a missing hostname usually signals spam or abnormal traffic. If you have a legitimate source that sends an empty hostname, it will disappear.
Here is a worked example. A retailer runs its main site, a separate checkout domain, a help centre on a subdomain and a booking tool. The team builds an allowlist from the marketing site alone, and checkout events vanish the next day. The fix is simple, but the damage is a gap in the data that you cannot backfill.
So build the list from evidence. Pull the hostname dimension from your existing reports over a long enough period to catch seasonal pages and rarely used tools. Add every domain someone on the business side says they own. Then compare the two lists before you save anything. Check Google's filter documentation for how to preview or stage a filter on your property, since the notes do not describe a testing mode and you should not assume one.
And if your property exists to collect from only one hostname, this is a five-minute job. The effort scales with the number of domains, not the size of the traffic.
How does the User Groups Admin API help with access at scale?
On 5 October 2026 Google Analytics added a User Groups Admin API. It lets you manage user group access to properties and accounts programmatically. You can create groups, edit them and delete them by their unique identifier. You can add and remove members and assign a permission level of Member or Owner. Using it requires User Admin or Org Admin permissions on the organisation.
Who is this for? Not a ten-person marketing team. If you manage a handful of users by hand, the interface is fine and a script is extra maintenance. The API earns its keep when you have many properties, agencies rotating in and out, or a joiner and leaver process that already runs through an identity system.
The real benefit is consistency and an audit trail. If access changes come from a script that lives in version control, you can see who changed what and when, and you can reproduce the configuration. Manual clicking gives you neither.
Be careful with the permission model. A script with Org Admin rights is powerful, so store its credentials like any other privileged secret and limit who can run it. Test against a non-critical group first. Read the reference docs and the Developer Changelog for the exact methods before you design anything.
If you only have a few users, skip it. Use user groups in the interface if they help, and revisit the API when the manual process starts to hurt.
What about app conversions, Firebase agent skills and Dashboards?
Three smaller items are worth a paragraph each, because they matter to specific teams.
App conversions for Google Ads customers (29 September 2026). App conversions are now supported in conversion reports, including performance, attribution analysis and attribution models. Conversion attribution settings can also be adjusted independently for app conversions. The notes say the feature may not be available to your property, and that Google is working to expand it. They also say cross-channel budgeting features currently support web conversions only. So if you run both web and app campaigns, do not expect budgeting views to include your app. Ask your support team about eligibility before building a reporting plan around it.
Firebase agent skills for the GA4F SDK (18 November 2026). App developers using the Google Analytics for Firebase SDK can now use Firebase agent skills so coding agents can change behavioural and conversion tracking in iOS and Android apps. The notes say initial integration and screen view logging are supported, with more development tasks coming. That is a narrow starting scope. If you try it, keep a human review step on anything an agent changes, because tracking code errors tend to be silent. Start with a screen view change in a test build and compare the events before and after.
Dashboards (9 September 2026). Dashboards are now available in Google Analytics. If your team currently exports data into another tool just to produce a weekly view, try building that one view here and see whether it is good enough. Judge it on a real use, not a demo.
How do you roll this out and measure it?
Do it in order, smallest risk first. A sensible sequence for a mid-sized team:
| Step | Task | Suggested owner | How you know it worked |
|---|---|---|---|
| 1 | Open Data Manager and compare it with your documented links and streams | GA4 admin | Every link and stream is accounted for in your documentation |
| 2 | Read UPD diagnostics in Admin and Data streams, if you send UPD | Tracking lead | Alerts are triaged, with a fix or a documented reason |
| 3 | Build a hostname inventory from existing reports and business input | Analyst plus web owner | Two independent lists agree |
| 4 | Apply a hostname Include filter during a quiet period | GA4 admin | Event volume from approved hostnames holds steady |
| 5 | Decide on the User Groups Admin API | Security or IT owner | A written yes or no, with a reason |
| 6 | Check app conversion eligibility with support | Paid media lead | You know whether the feature applies to your property |
Measurement here is mostly about stability, not growth. After a hostname filter goes live, watch daily event counts and key event counts for the approved hostnames against the same weekdays in the previous weeks. A drop that does not match a known cause is your signal to check the allowlist and the empty hostname behaviour. Spam volume should fall, but do not celebrate until legitimate volume is flat.
For UPD, the measure is the alert state itself and the downstream numbers that depend on it, such as conversion volume you expect from forms. For Data Manager, the measure is time to answer a basic question about a link or stream. Time it before and after, if you want a number you can defend.
What to ignore: anything that promises a traffic or revenue lift from these features. None of them is a measurement of marketing performance. They protect the quality of the data you already have.
Where does an implementation partner help, and where can you go it alone?
Most of this you can do yourself. Opening Data Manager, reading diagnostics and checking support eligibility need an admin and an afternoon. A single-domain hostname filter is similar.
A partner earns its fee when the problem is bigger than a setting. Examples:
- You run many domains, regional properties or acquired sites and need a hostname allowlist designed across all of them, with a plan for the empty hostname and Measurement Protocol cases.
- You send user-provided data and the diagnostics show recurring problems that trace back to forms, consent handling or a tag manager setup nobody fully owns.
- You manage access across a large number of properties and want the User Groups Admin API tied into your identity process.
- You have both web and app properties and need consistent conversion definitions.
If that sounds like you, start with the GA4 partners directory to see who works on this, and use the GA4 RFP template to write the brief. A good brief names your domains, your user-provided data sources, your current alert state and who will own the setup afterwards. Vague briefs get vague proposals.
When you compare firms, ask each to explain how they would test a hostname filter before it goes live, and how they would hand over the documentation. Those two answers tell you more than a list of certifications. You can also compare shortlisted firms side by side on the compare page.
One last position. Do not hire for the novelty of a beta. Data Manager may change, and a partner who sells you a deep project around a screen that is still settling is selling you something you do not need yet. Pay for the parts that will still matter next year: clean hostnames, trustworthy user-provided data and tidy access.
Sources
- Google Analytics Help: What's new in Google Analytics — Release notes for 9 September, 21 September, 29 September, 5 October, 6 November, 11 November and 18 November 2026.
Frequently Asked Questions
What is Data Manager in Google Analytics?
Data Manager is a hub in the Google Analytics admin console for connecting and controlling product links, data streams and first-party data. You can also use it to address diagnostic alerts and monitor connection health. It was launched in beta on 6 November 2026, so expect the interface to change.
Do GA4 hostname Include filters apply to Measurement Protocol events?
No. According to the release notes, Include filters for hostnames are not applied to events sent from the Measurement Protocol, so that data stays unblocked. Events with empty hostnames, such as gtag.js traffic, are blocked automatically by an Include filter.
Where do user-provided data diagnostics appear in Google Analytics?
They appear in the Google Analytics Admin area and in the Data streams panels when a property fails to receive data or has quality issues with user-provided data. They help you decide whether to change your tag configuration or your collection method.
Who can use the User Groups Admin API?
Anyone with User Admin or Org Admin permissions on the relevant organisation can use it. It lets you create, edit and delete user groups, add and remove members, and assign Member or Owner permission levels. Check the reference docs and the Developer Changelog for the exact calls.
Are app conversions available in every GA4 property?
Not necessarily. The 29 September 2026 notes say the feature may not be available to your property and that Google is working to expand it. Ask your Google support contact about eligibility if you rely on app conversion reporting.