google / google/site-kit-wp

Handle the case where the Google Tag event settings are out of sync with the web data stream settings.

Open
#7,524 0 comments 0 reactions 0 assignees View on GitHub
Module: Analytics P2 Type: Enhancement
Dominant language
JavaScript
Stars
1.4k
Forks
384
Avg merge
4d 14h
Merged PRs (30d)
77

Description

## Feature Description

As spotted by @wpdarren, and as mentioned [here](https://support.google.com/analytics/answer/9216061?hl=en), when using a Google Tag in conjunction with a data stream with enhanced measurement enabled, it's necessary to ensure that the relevant events are enabled in the Google Tag's config as well.

These can be configured in the Tag Manager UI (see screenshot below), or via the [API](https://developers.google.com/tag-platform/tag-manager/api/v2/reference/accounts/containers/workspaces/gtag_config). By default, all event types are enabled, so the scenario where there's a mismatch between the events settings will be another edge case that we need to consider.

Perhaps another warning notice would suffice for an MVP, and we could follow up with the ability to allow the user to sync the settings.

![image](https://github.com/google/site-kit-wp/assets/18395600/6f9c2b75-e00f-4b77-939a-83a6432ac742)

---------------

_Do not alter or remove anything below. The following sections will be managed by moderators only._

## Acceptance criteria

*

## Implementation Brief

*

### Test Coverage

*

## QA Brief

*

## Changelog entry

*

Contributor guide

Open the contributing guide

Research direction

Start by tracing how Google Tag event settings and web data stream enhanced-measurement settings are represented and compared in the existing settings flow. Review the linked Google documentation and determine the MVP warning behavior before identifying the relevant UI and API entry points. Done means an out-of-sync configuration is detected and clearly surfaced to the user.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
analytics
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.