This allows users of common express to provide an analyticsDataSensitive value to control the analytics data sent by v2.0.0 of the @govuk-one-login/frontend-analytics package.
Why did it change
The breaking change in v2.0.0 of @govuk-one-login/frontend-analytics is that it defaults to a new, more cautious approach, to reporting analytics. This will happen by default if teams update their version of @govuk-one-login/frontend-analytics to v2.0.0.
To retain the current v1.x.x approach to reporting analytics teams need to set the isDataSensitive flag to false, which can be done by providing a analyticsDataSensitive value to the setGTM function in this updated version of common-express.
Users who are still using @govuk-one-login/frontend-analyticsv1.x.x will see no change when updating to this version of common express.
…ing by default
Proposed changes
What changed
This allows users of common express to provide an
analyticsDataSensitive
value to control the analytics data sent byv2.0.0
of the@govuk-one-login/frontend-analytics
package.Why did it change
The breaking change in
v2.0.0
of@govuk-one-login/frontend-analytics
is that it defaults to a new, more cautious approach, to reporting analytics. This will happen by default if teams update their version of@govuk-one-login/frontend-analytics
tov2.0.0
.To retain the current
v1.x.x
approach to reporting analytics teams need to set theisDataSensitive
flag to false, which can be done by providing aanalyticsDataSensitive
value to thesetGTM
function in this updated version of common-express.Users who are still using
@govuk-one-login/frontend-analytics
v1.x.x
will see no change when updating to this version of common express.Issue tracking
Checklists
Environment variables or secrets
Other considerations