UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
There are several methods in the advertising industry to create persistent user identifiers - http://www.digitru.st/ and Open Ad Id being the 2 largest. These projects get closer to a persistent advertising ID, similar to mobile devices, but without the user control that mobile advertising ID enables.

Up to 75% of the calls made on a publishers page are made just to sync user IDs between various ad tech partners. Having a consistent browser level user ID with strong controls would create significant browser performance boosts across all devices, improve user privacy, and educating end users about enabling/disabling their advertising ID is easier than talking about cookies. 

What is the expected behavior?

What went wrong?
The current behaviour encourages users to block all advertising and slows page loads by loading a large amount of ID syncs.

Did this work before? N/A 

Chrome version: 58.0.3029.81  Channel: n/a
OS Version: 
Flash Version: