Remediate Findings from GA4 Migration

[johnny-jesensky-adhoc]

Problem Statement

As part of our GA4 migration efforts, our team has identified numerous things that we would want to optimize regarding tracking (GA), our data pipelines (BigQuery), and reporting (Domo).

The team has not had the time or bandwidth to execute on these things during the migration, but have been keeping record of some of this "low-hanging fruit" that we have identified, and would like to revisit some of it post-migration.

Many of the findings aren't critical, but would help optimize the Platform's costs around GA tracking, BigQuery data processing, and Domo storage.

Hypothesis or Bet

If we devote time to remediating some of the items that have been identified during the migration, we could benefit the Platform in a number of ways.

• More efficient tracking and measurement strategy, through clean-up of Google Tag Manager (GTM), and reducing number of events needed to track the same things.
• Cost optimization in BigQuery through more-efficient and performant queries.
• Cleaner Domo environment, with business logic moved over to BigQuery wherever possible.

We will know we're done when... ("Definition of Done")

• [ ] Items flagged during the GA4 migration will be revisited, and resolved.

Projected Launch Date

Mid 2024 -- post Universal Analytics (UA) sunset date, which is July 1, 2024.

[raywangoctova]

@johnny-jesensky-adhoc Can we narrow the scope of the work for this issue to only GA4? How about the other two bullets on BigQuery and Domo as separate issues?

[johnny-jesensky-adhoc]

@raywangoctova -- Yes, I agree this one should be further broken out. I'll clean this up so it's just focused on our GA4 optimization, and create separate epics for (1) our work to optimize BigQuery and its costs, as well as (2) the same for Domo.