Status Update
Comments
aa...@google.com <aa...@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
np...@google.com <np...@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
aa...@google.com <aa...@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
Signature:
*: AndroidLogcatService|...|20M 100 myDevice: DeviceImpl
In this report from Dolphin Beta 1, there are almost 9000
AndroidLogcatReceiver
s registered withAndroidLogcatService
, which refer toDeviceImpl
objects which appear to have reasonably large maps of properties. I'm not sure how anyone could actually connect 9000 devices or emulators simultaneously, so I suspect there's a leak.