QC Initial Domo Report -- Standard Content Engagement KPIs

[johnny-jesensky-adhoc]

Description

This ticket is account for QC'ing the Standard Content KPIs dashboard with the newly create GA4 view. Focus on QC'ing the metrics specifically for changes in the naming conventions, confirm beast modes/charts are functioning and if they aren't identify what is the cause of the issue.

Note: this dashboard is made up of 15 cards, powered by two GA datasets (and one medalia), and uses 12 beast modes. All of that information and more and be found in this document.

Tasks

• [x] Create duplicate dataset and cards. Once Phil creates new view, route duplicate cards to new view.
• [x] Follow up with Phil for any changes that need to be made to the dataset.
• [x] Doing column per column comparison between the UA and the GA4 Views
• [x] Look for and document differences in variable names, formatting, etc.
• [x] Check if event labels, categories, actions -- etc that are used within BeastModes -- we might have to derive this
• [x] Copy report -- Save As -- use new GA4 Dataset --
• [x] Set permissions of copied report so it's just available by our team.
• [ ] If we pass these checks -- we can plan to certify that the reports are fresh.
• [x] If data issue, or discrepancy is found, mark in ticket and notify team.

• [x] Document findings from QC, and potential changes here.

Acceptance Criteria

• [x] Report has been copied -- using the new GA4 view.
• [x] Notes from QC or potential changes to ETLs have been documented on this page.
• [x] All data issues have been flagged, and if needed, another ticket has been created for them.
• [ ] If data is looking good -- we need to flag as fresh.

[johnny-jesensky-adhoc]

@ChristineYoungZA, @Blivaditis -- can y'all take a pass at adding in tasks on what might be needed to QC Domo reports -- starting with the Content KPIs.

[Blivaditis]

Notes from QC: the only metrics missing between the GA4 dataset and the UA one are product description and page name. Additionally Christine and I commented in the QC record artifact identifying which additional metrics are needed to recreate beast modes/charts.

[Blivaditis]

Six charts were not able to be recreated in current state, four charts share an issue of needing product_url added (identified by Christine) and the remanning two need scroll depth to be recreated (identified by Basil). Update: only missing scroll depth now will be fixed once added.

[Blivaditis]

ETL has been created, making a new dataset which powers three charts, further testing may be needed. All cards (besides scroll depth) have been converted to the GA4 dataset and are populating with data. The new dataset is producing significantly higher Hits and interactions than its UA counterpart, will look into further for possible solutions.

Theory: unnecessary events are tracking causing inflated #s

[johnny-jesensky-adhoc]

Most of the QC has been completed -- we found a few things we need to validate, and tweak upstream -- that work will be captured as part of this separate validation ticket.

FYI @ChristineYoungZA, @Blivaditis