[Analytics] env property not reporting via tessen

[roadlittledawn]

Description

Each site can specify properties to track for a tessen.page() call. Since each site reports all data for any environment it's running in, we want to be able to distinguish prod from other envs. It looks like the env is resolved as expected but the function getProperties() (which is supplied via a site's gatsby-config.js doesn't seems to set it inside of trackPageView()

Steps to Reproduce

Expected Behaviour

Relevant Logs / Console output

Example of raw data reported currently

[jpvajda]

I'm going to add this to sprint 2 as I really would like to get all of our analytics issues sorted and resolved so we can focus on other things. @zstix any thoughts?

[roadlittledawn]

we could also add an option in each sites' gatsby-config.js to disable page view tracking for non-prod envs too (a la the tessen doc), FWIW. but i still think it would be good to get the path and env properties to be sent along with the page view data.

[moonlight-komorebi]

haha. sorry for all the time on this. in the end, got a simple pr out for this.

most of my time was spent researching what is wrong / why this isn't working. it looks like getProperties is getting dropped. an initial search lead me to believe that functions passed as parameters to plugin options were getting dropped during build time, but im not confident in the end as to what the cause is. in any case, the fix is pretty straightforward and simplifies things overall.

links for reference:
https://spectrum.chat/gatsby-js/general/defining-a-plugin-option-as-a-function~42c75d64-0e25-467f-882a-197bfd528a11
gatsbyjs/gatsby#14199
gatsbyjs/gatsby#13440

update: it looks like the last link has the answer / heart of this problem defined exactly.
Note that plugin options of gatsby-ssr.js and gatsby-browser.js get stringified by Gatsby, so they cannot be functions.
since we are utilizing the options for our tessen calls in gatsby-browser.js, we are running into this.