TagControl is our solution to making Tag Auditor more actionable, by letting our customers block their tags at all levels unlike a Tag Manager which only blocks at the root level.
What does this mean exactly? Let's take Google Tag Manager. They can stop a root tag from firing like double click and that’s where it stops. If a customer was ok with DoubleClick but not some of the tags that may piggy back from there, then the only recourse was to stop DoubleClick all together. TagControl can stop DoubleClick from firing but also any other “piggy-backed" tag. So, in this instance the user could keep DoubleClick and then block any piggy backed tags they don’t need and/or want.
This release includes some major changes to what had been done before. One of the first things we addressed was sign-on. With this release we have put Single Sign-on (SSO) in place, so customers can now use the same log in as privacy.evidon.com. To log in to TagControl, visit tagcontrol.evidon.com. For this initial release, customer accounts will need to be granted access by our team.
UI:
Logging in to tagcontrol.evidon.com will give you access to the Tag Control UI. Once inside the UI permissions are set at 3 levels.
Once logged into the UI you will see a couple different sections.
2 main points to this section.
Note: Once the policy has been generated, it will be enforced on any site that the TagControl tag has been placed.
Critical Tags: Critical tags are tags that affect the basic functionality of a site. If a site would not work without a tag, it should be considered “critical.”
Approved Tags: Approved tags are tags which are part of your whitelist.
In each of the tables mentioned above:
o If blank, it’s an unknown tag.
TAG:
The tag itself now runs in three modes. These modes are held in the config.json (see below). This was a necessity to help manage the tag better. The modes are represented by the following numbers:
During Observe mode we added in features to gate the data coming through. When we put our first customer on Tag Control the data proved to be faster than what we thought. To solve this, we added the following parameters. These parameters are stored in the config.json.
{
mode: 1,
meterMax: 1000,
pageMax: 3,
scanInterval: 30,
whitelist: [“google.com”, “facebook.com” ]
}
meterMax: provides a maximum range of users in which the Observe tag will send data. In the above config.json example, since the meterMax value is set to 1,000 this means that only 1 in 1,000 users who arrive on the website will send data.
pageMax
Is the maximum numbers of observe data requests that can go out for any given page load. In the above config.json example this is set to 3. This means that for every 1 in 1,000 users, an Observe request will be sent a maximum of 3 times for the current page load.
scanInterval
An interval of time in seconds in which the Observe tag will wait to re-scan the document for tags. In the above config.json example, this is set to 30. This means that for every 1 in 1,000 users, an Observe request will go out every 30 seconds, a maximum of 3 times for the current page, following gates while in observe mode.
The above definitions are in the config.json (example url below). Upon saving your policy, the whitelist is updated automatically in the json.
https://tagcontrol-cdn.evidon.com/{companyid}/config.json
As for the script: Below is the script.
<script src=https://tagcontrol-cdn.evidon.com/script/v1/tagcontrol.js companyId=”{companyId}”></script>
The tag is supplied by us along with the company ID to be plugged in above. The tag then sits in the head of the website.
On top of this we have a callback wrapper that is implemented after the primary tag. This wrapper is used for first party tags like Google Tag Manager.
<script>
function append(e,a,n){var t=document,r="script",c=t.getElementsByTagName(r)[0];c||(c=t.head);var d=t.createElement(r);d.async=!0,d.id=e,d.src=a,c.parentNode.insertBefore(d,c)} window.tagControl.tagControlCallback = function () {
// Add first party JavaScript here
// =========================
append('google-recaptcha', 'https://www.google.com/recaptcha/api.js', true);
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-CODE');
// End of first party js =========================
}
</script>
The Evidon first-party wrapper should also be placed in the header, directly below the Tag Control JavaScript tag.
Peer-to-peer support and answers on developing CMS templates, modifying privacy scripts or building integrations.
Find answers and ask questions on content management, personalization and targeting.
Find answers and ask questions on WCAG and SEO quality management.
Find answers and ask questions on consent and monitoring solutions.