To answer the original question: No, advanced link binding is not yet supported by Universal Analytics. Although this and many other features will be deployed soon. Universal Analytics is still very beta, but it has been determined that this is the future for Google Analytics.
Yes, the new code is asynchronous, like the old code, and I really could not imagine a situation where you want to disable it. Asynchronous loading in this case means that when you run javascript analytics, your web page continues to load regardless of whether javascript has finished loading or not. Before updating the asynchronous snippet, the best practice for loading analytics code in the footer was to prevent the entire page from freezing due to the lack of the asynchronous nature of the script. Although this has been changed since on long / slow pages the user often interacted with the website before the footer / javascript was able to load and, in turn, caused significant discrepancies in the data.
Wikipedia:
In computer programming, asynchronous events are events regardless of the main program flow. Asynchronous actions are actions performed in a non-blocking scheme, allowing the main program to flow to continue processing.
I also do not propose changing the name of the object , as Concept Rat suggests, since I believe that this only applies if you run many “universal analytics” trackers for different web properties within the same fragment.
https://developers.google.com/analytics/devguides/collection/analyticsjs/advanced#snippet :
Rename a global object
In some cases, the variable name ga may already use an existing object on your page. To avoid overriding an existing object, you can rename the ga function, for example, to __gaTracker. to do this, just replace the ga parameter in the snippet above:
(function (i, s, 0, r, g, a, t) {i ['GoogleAnalyticsObject'] = g; i [g] = g [g] function || () {(I [g] .q = I [g] .q || []). (Push arguments)}, I [g] .l = 1 * new Date (); a = s.createElement (o), m = s.getElementsByTagName (o) [ 0]; a.async = 1; a.src = g; m.parentNode.insertBefore (a, t)}) (Window, document, 'script', '//www.google-analytics.com/analytics.js ',' __ gaTracker ');
Then you can use __gaTracker instead of ga when invoking commands:
__ gaTracker ('create', 'UA-XXXX-Y'); __gaTracker ('send', 'pageview');
If renaming a variable was necessary to load both snippets, I do not believe Google will say this:
https://developers.google.com/analytics/devguides/collection/analyticsjs/ :
The analytics.js snippet is part of universal analytics, which is currently in public beta. New users should use analytics.js. Existing ga.js users must create a new web resource for analytics.js and dual mark their site. It is safe to include both ga.js and analytics.js on the same page.
Also note that if you want to try out universal analytics, you must run it at the same time as your existing implementation, because ultimately they must release a migration tool to stay backward compatible, allowing you to store existing data. To be completely clear: You must fully implement universal analytics if you create a completely new account without existing data.