utm_term appears to be empty in the re:dash datasets. it appears to be populated properly in amplitude, so I'm guessing the problem lies in this repo somewhere, but I haven't put my finger on it yet.
we're using this parameter to track performance of trailhead variations. once https://github.com/mozilla/fxa/issues/1018 is resolved, we should be able to use amplitude for that, but it would be good to fix this so we have a backup way to analyze that data (or other experiments/reliers that use this parameter).
utm_term appears to be empty in the re:dash datasets. it appears to be populated properly in amplitude, so I'm guessing the problem lies in this repo somewhere, but I haven't put my finger on it yet.
we're using this parameter to track performance of trailhead variations. once https://github.com/mozilla/fxa/issues/1018 is resolved, we should be able to use amplitude for that, but it would be good to fix this so we have a backup way to analyze that data (or other experiments/reliers that use this parameter).