Status Update
Comments
dv...@google.com <dv...@google.com> #2
Hi Boris,
I'm Kevin from the Google Analytics API Team.
Currently, the measurement protocol doesn't support passing IP parameter. Also, our
Regards,
Kevin Soriano, Google Analytics API Team
dt...@google.com <dt...@google.com> #3
Thanks for your quick answer, three followup questions for you:
1. Clear in terms of IP address. Is this something that you are still working on, considering the measurement protocol is still in beta?
2. The documentation lacks explanation as to how to send through the user agent? Which field can we use for this, e.g. _ua or ua?
3. The documentation lacks explanation as to how to send page_view events with traffic source fields (e.g. referrer, identifiers, utm parameters) so that it properly categorizes the session and user's source/medium.
cheers
Boris
ue...@google.com <ue...@google.com> #4
Hi Boris,
Please see below for my comments on your concerns.
- Clear in terms of IP address. Is this something that you are still working on, considering the measurement protocol is still in beta?
There's already an existing feature request in order for customers to send IP addresses via Measurement Protocol. However, I'm afraid that we won't be able to provide a timeline on when it will be supported. Can you provide your use-case to me on why you need to send IP addresses via MP so I can add it to the ongoing feature request?
- How can I send through the user agent?
Can you provide your use-case to me on why you need to send user agent via MP so I can share it to our team as well?
- How can I send page_view events with traffic source fields (e.g. referrer, identifiers, utm parameters) so that it properly categorizes the session and user's source/medium.
I'll check this with the rest of our team. I'll let you know once I have more information. In the meantime, you can try creating
Regards,
Kevin Soriano, Google Analytics API team
Description
Comments from monorail:
unknown user: I would like to report the following troubles that I am having with my
six months old $100 Lenovo Chromebook. I have not the slightest idea
to whom I should be sending this message. Any suggestions would be
most appreciated.
I am almost always on my Chromebook using Linux using emacs. My main
directory is connected to Google Drive.
Problem one. I rather often, several times a day, encounter a severe
problem that effectively kills my emacs, namely 'Transport endpoint is
not connected'. I believe that this is telling me that Google Drive
is no longer working well with my Chromebook. I have not a clue about
what to do except to kill my emacs and start emacs again. Such a
restart of emacs immediately solves the problem, in some sense.
Problem two. About once a day my emacs is effectively killed by a
report that my main directory, really on Google Drive, is now entirely
write protected. Some sort of sign that Google Drive is not working
well with my Chromebook. Same 'solution' as for problem one above.
Problem three. I need for my SD card I to have another name.
Although the Files program appears to let me change the name, Linux
sees only the original name, namely 'SD Card'. That makes it
impossible for me to make full use of the ACL2 program, which will not
tolerate a space in a directory name. I have tried various
approaches, e.g. using 'mv' in Linux, even under sudo, but everything
I have tried fails to change the real name of my SD card, to change
the real name which Linux sees. I have even tried to use a hard link,
but that is apparently forbidden. Strange.
Problem four. Suppose that I have a url for a directory on Google
Drive that someone has kindly made public. I need a way to
make that directory appear as part of the Linux file system that I
have with my Chromebook. Some kind of a 'mount' command is what I
think I am hoping for.
Thanks,
Robert Boyer
robertstephenboyer@gmail.com
Thanks to Google for offering so much to so many for free. I am sure
that John McCarthy, may he rest in peace, is very proud of Google.
-----------------------------------