Skip to content

TrackingDetailsAndTricks

Zwetan Kjukov edited this page Oct 6, 2015 · 25 revisions

Tracking Details and Tricks

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)
    the WebTracker starts with 20 hits
    that are replenished at a rate of 2 hits per second.
  • AIR applications (equivalent to Android SDK/iOS SDK)
    the AppTracker starts with 60 hits
    that are replenished at a rate of 1 hit every 2 seconds.
  • RedTamarin (command-line and server-side)
    the CliTracker starts 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

Session Management

Pages

Screens

Events

Timing

Exceptions

Custom Dimensions and Metrics

E-commerce

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.

Clone this wiki locally