Collect stats about the numerical weather prediction model used by our visitors #143
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.
Since the app uses the same URL
/v2
we can not monitor in the stats whether our users use the new interface to see the WRF results or the GFS results.To address this issue, we replace the standard analytics script with a custom one that attaches a custom property to every “page view” event to indicate the underlying model (GFS or WRF).
As a consequence, we can now segment visits according to that property:
Alternatively, we could rewrite the URL to use distinct URLs such as
/v2/gfs
and/v2/wrf
but I believe custom properties attached to the page view events are a cleaner way to track that information.