-
Notifications
You must be signed in to change notification settings - Fork 11
TrackingDetailsAndTricks
Throttling
Our library as3-universal-analytics may throttle events,
as well as other hits, if a large number of send calls are made in a short period of time.
By default our trackers use a RateLimiter
-
Online SWF files (equivalent to analytics.js)
theWebTrackerstarts with 20 hits
that are replenished at a rate of 2 hits per second. -
AIR applications (equivalent to Android SDK/iOS SDK)
theAppTrackerstarts with 60 hits
that are replenished at a rate of 1 hit every 2 seconds. -
RedTamarin (command-line and server-side)
theCliTrackerstarts with 100 hits
that are replenished at a rate of 10 hits per second.
Sampling
By default our trackers use a sample rate of 100%,
that means all hits are send, but then if your sites or apps
reach millions of users you might consider sampling down
your data to maybe 40% more or less.
By sampling the hits for your site or app, you will still get reliable report results while staying within the hit limits for your account.
see: How sampling works
By default, Google Analytics will group hits that are received within 30 minutes of one another into the same session. This period is configurable at the property level.
see: Learn how to configure this session timeout period
Manual Session Management
You can manually start a new session when sending a hit to Google Analytics.
The following example shows how to start a new session when sending a screen view:
tracker.setOneTime( Tracker.SESSION_CONTROL, SessionControl.START );
tracker.screenview( "Home Screen" );Automatic Session Management
Not supported yet.
Note:
Our trackers can track E-Commerce Transaction and Item but it seems
those will be deprecated in favour of Enhanced E-Commerce which uses
more complex parameters that we don't support yet.
In fact, analytics.js need to load an additional ecommerce.js,
see Ecommerce Tracking.
We may not support that at all as our focus is on the Measurement Protocol.