Adjust analytics opt out page events #825
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Page to edit
url:
https://www.va.gov/analytics-opt-out.html
For:
department-of-veterans-affairs/va.gov-team#36585
Origin of request (internal/stakeholder/user feedback)
Analytics & Insights team audit of Domo dashboards
Description of what's needed (edits/link changes/additions)
We have a chicken-and-the-egg situation with the analytics opt out event being fired:
The internal user flag is set to true at the property level so this event itself is not making it to the All view (which is what is exported to BigQuery). Because of this, we can not create a list of GA user IDs and retroactively remove data from internal users. This is causing discrepancies with our Domo dashboards and GA.
I just doubled up the event (without the internal user param), but open to suggestions for a pre-event name.