Routing Third-Party Analytics/User Tracking/Advertising scripts through CookieHub #74
Description
On the current live site, the following is directly embedded in the page markup:
<script type="text/javascript">
_linkedin_partner_id = "1840292";
window._linkedin_data_partner_ids = window._linkedin_data_partner_ids || [];
window._linkedin_data_partner_ids.push(_linkedin_partner_id);
</script>
<script type="text/javascript">
(function(l) {
if (!l){window.lintrk = function(a,b){window.lintrk.q.push([a,b])};
window.lintrk.q=[]}
var s = document.getElementsByTagName("script")[0];
var b = document.createElement("script");
b.type = "text/javascript";b.async = true;
b.src = "https://snap.licdn.com/li.lms-analytics/insight.min.js";
s.parentNode.insertBefore(b, s);})(window.lintrk);
</script>
This is a high-profile enough tracker that CookieHub will likely prevent it from loading even embedded in this way, but to make sure the request can't fire prior to CookieHub intercepting it, the script that makes the request for https://snap.licdn.com/li.lms-analytics/insight.min.js should be routed through CookieHub using the following fields:
