One of our customers asked for a feature request and I think it's great:
But today, it's more and more common to restrict how the referrer header is sent (to other origins, at least). One example of such a restriction is the HTML tag <meta name="referrer" content="origin"> that may be used in the "head" section of a document.
How does your image-based (1x1 GIF) tracking code work with such restrictions? I imagine the referrer header is the only way you can associate the recorded data with the correct account or site, right? If the referrer header is not sent (or trimmed), tracking does not work.
Couldn't you allow for the visited URL to be specified explicitly, instead of just accepting it implicitly from the referrer header?
The explicit value could even be used as a fallback only, i.e. when the implicit value is not available. Google Analytics includes the account's or site's unique tracking ID in the code as well, which simplifies associating visits with sites.
Let's put this on our roadmap and combine it when we work on our API. It's a nice Friday afternoon project.
The text was updated successfully, but these errors were encountered: