DAP 8.6.0
What's new in DAP 8.6.0
Features
Unified statistics for www and non-www domains
www and non-www traffic is now combined in GA4. So, for instance, instead of seeing separate view counts for gsaadvantage.gov and www.gsaadvantage.gov:
You'll soon start to see a single summed count for gsaadvantage.gov.
Note that this is a change in how the data is collected, not just in how it is displayed, so the change will not be retroactive.
Additional allowed query parameters
lat and lon have been added as allowed query parameters for all agencies.
Bug fixes
Upcoming fix for site leakage between GA4 subproperties
The problem
Agencies have reported that sites that do not belong to their agency sometimes appear within their GA4 subproperty. For instance, the domains report for the Dept. of Treasury might show page view counts for state.gov or opm.gov.
The cause
The full URL field is used to filter data into subproperties but has one known limitation: if a hostname appears within a query string parameter (mostly as a referrer domain) of the actual hostname, it will still be included in the reporting for the subproperty. For example https://usajobs.gov/search/result?query=https://www.ftc.gov/oig will be included in FTC subproperty. While an advanced regex filter was created to address this, GA4's limitations prevent its support.
The solution
Now that GA4 allows filters based on custom dimensions, we are introducing a new custom dimension that captures only the event's hostname. Subproperty filters will be updated to use this hostname dimension instead of the full URL, effectively resolving the issue.
Alongside the code release, we will update the subproperty filters once they migrate to v8.6.
Agency-specific changes
- Department of Commerce: Added
product1as allowed query parameter. - NASA: Added
topicandtitleidas allowed query parameters.