The first time a user loads the RWP a redirect is issued, which strips the HTTP params including UTM codes. This redirect is done in JS, but since Firebase analytics aren't loaded this early, the user's first UTM params are not captured.
We can see in the debug view that individual analytics pings do contain the UTM info, but for reports it's the user's first UTM code that matters.
Describe the bug
The first time a user loads the RWP a redirect is issued, which strips the HTTP params including UTM codes. This redirect is done in JS, but since Firebase analytics aren't loaded this early, the user's first UTM params are not captured.
We can see in the debug view that individual analytics pings do contain the UTM info, but for reports it's the user's first UTM code that matters.
To Reproduce
Expected behavior
User's first source should be "test123"