Closed GoogleCodeExporter closed 9 years ago
hello, no news?
Original comment by Francois...@gmail.com
on 4 Jun 2012 at 5:00
Any news? we need this information to take a decision.
Original comment by webmas...@straumann.com
on 8 Nov 2012 at 8:50
No, still waiting.
Original comment by Francois...@gmail.com
on 8 Nov 2012 at 11:54
[deleted comment]
It's critical to know when this will be fixed. Otherwise mobile developers
would need to implement their own tracking in a persistent stack and send those
pageviews/events only when online.
Original comment by moham...@hidefweb.com
on 11 Mar 2013 at 6:21
This is working as expected, and is well documented for Android, though it
pertains to GA hits sent from any environment, including iOS:
Data must be dispatched and received by 4 a.m. of the following day, in the
local timezone of each profile. Any data received later than that will not
appear in reports. For example, if a hit is queued locally at 11:59pm, it must
be dispatched within 4 hours, by 3:59am, to appear in reports. On the other
hand, a hit queued at 12:00am must be dispatched within 28 hours, i.e. 3:59am
of the following day, in order to appear in reports.
https://developers.google.com/analytics/devguides/collection/android/v3/dispatch
Original comment by awa...@google.com
on 8 Nov 2013 at 11:53
To #6.
Well that is not TRUE. we tried to put iPad offline for 15 mins note down what
hits should appear after bringing it back online in half and hour and it seems
all data is lost. Whereas FLURRY had all data accurately dispatched. This is
kind of unreliable so no option but to look other analytics services.
Original comment by rohanrid...@gmail.com
on 13 Aug 2014 at 8:01
Original issue reported on code.google.com by
Francois...@gmail.com
on 18 May 2012 at 1:16