![]() Hit volume is reevaluated every 10 minutes based on 10-minute averages, and processing resumes when hit volume returns to normal levels. To preserve system stability and efficient use of resources, Real-Time will temporarily stop processing hits if the volume is unusually large during any 30-minute period. When Real-Time reporting is suspended, data collection and all other reporting services aren’t affected. Real-Time reporting is sometimes temporarily suspended in views that you haven’t recently accessed, however Real-Time is reactivated after you visit a Real-Time report in that view. If you don’t see any data in your Real-Time reports, it’s possible that there are no active users. Batching typically occurs on the order of minutes. Mobile hits are batched to conserve battery life, so you may notice delays. Changes made to views may take up to two hours to reflect in Real-Time. It's best to use an unfiltered view when debugging tracking code implementations. If your data looks incorrect in Real-Time, check which filters are being applied to the view. Real-Time reports are not compatible with User ID enabled views.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |