Queue Time Limitation ?

[Nicolas Rio]

Apart from the global limitation listed here (https://developers.google.com/analytics/devguides/collection/protocol/v1/limits-quotas), is there any limitation concerning the maximum time shift I can apply to an event with the Queue Time parameter ?

For example, is it possible to change the date of an event to 2 years ago ?

[Nick Mihailovski]

per the docs:

>Used to collect offline / latent hits. The value represents the time delta (in milliseconds) between when the hit being reported occurred and the time the hit was sent. The value must be greater than or equal to 0. Values greater than four hours may lead to hits not being processed.

The docs should actually read 4 hours past midnight of the configured timezone in the profile.

If you send data later than this time, hits will not be processed.

-Nick

[Nicolas Rio]

Hum... Thank you very much and sorry that I didn't read the last sentence of the doc...

Is there any plan to increase this 4 hour delay to 1 or 2 days in the future ?

Cordialement,

L'agence Interaction fête ses 15 ans le 13 juin prochain à l'Armada, inscrivez-vous !

Nicolas RIO
Chef de projet technique

+33 (0)2 35 120 130
www.interaction-multimedia.com

2013/5/20 Nick Mihailovski <n...@google.com>

--
You received this message because you are subscribed to the Google Groups "google-analytics-measurement-protocol" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-analytics-measure...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Kasper Sørensen]

I would be interested in knowing this as well. Or, alternatively. Why this limit is in place?

2013/5/20 Nick Mihailovski <n...@google.com>

To unsubscribe from this group and stop receiving emails from it, send an email to google-analytics-measurement-protocol+unsubscribe@googlegroups.com.

[Dorian Kind]

Hey Nick,

sorry to resurrect an old thread, but this post of yours seems to be the only information about the queue time parameter, apart from the documentation which you say is not correct. So just to be sure: is my understanding right that the latest time at which it is possible to submit a hit for a given profile using the measurement protocol is 4 AM the following day? Does this mean, accordingly, that the maximum value for the "qt"-parameter is 100800000 minus one (28 hours times 3'600'000 milliseconds)?

Thanks for your feedback & best regards,
Dorian

[Nick Mihailovski]

Yes, currently the latest you can set this value is 4am of the time zone for the configured profile.

You can set this value for a greater time, but there is a high chance this will not get processed.

-Nick

[Dorian Kind]

Hi Nick,

many thanks for your quick answer! One thing though, tracking is done at the property level but time zones are AFAIK configured at the view level. So if I have multiple different time zones inside a single property, which one is relevant for calculating the maximum allowed value for the queue time parameter? Is it the default view? Or does this mean that a "lagged" event may show up in some profiles but not in others, depending on the configured time zone?

Thanks again and best regards,

Dorian