Initial Set Up

Adding your script and classifying with telemetry

Adding the HTML script

When you begin setup, our onboarding steps will surface the exact <script> tag you need and ask you to add it to your site.

You can also find the exact <script> tag to add to the <head> tag section of your site in Consent’s dashboard under Developer Settings.

Once you do this, Consent is in “Reporting Only” mode by default and is only collecting telemetry data (the number of requests made to different domains) for the purpose of automatically filling out your Data Flows page. It does not regulate or block any requests yet, and should have no impact on your site functionality.

Classifying with Telemetry

The telemetry data is then sent to our backend to be processed and classified, and will show up in your “Data Flows” table. Now, all you have to do is wait for enough telemetry data to come in -- the more visitors you have, the more pages they visit, the more quickly your data flows will fill up.

Note: The activity bar measures how many requests were made to a given domain, relative to the total # of requests we detected.

Occasionally, our backend may not be able to auto-classify the tracking purpose for a given domain. In these case, you’ll be prompted for help in the Consent Manager dashboard:

Note: Your dashboard will let you know if there are data flows (in this case, 2) without any tracking purposes that require your review.

If you use popular trackers such as Facebook or Google, you should check out our additional documentation on how to manually configure the data flows for them.

A note on third-party frameworks

For the moment, we’re assuming that you aren’t using a third-party web framework or content management system and have very precise control of the HTML your site generates, because you will need to be able to strictly control the order in which scripts and other content are loaded in order for Consent to be most effective.

If you’re integrating Consent with a site built in a web framework which specifies its own HTML template or with a third-party content management system, you will need to go through more steps, specific to your web framework or content management systems. Please consult with Transcend Support for help.

For a site you’ve built from the ground up, integrating the airgap.js library is as simple as adding a <script> tag referencing the airgap.js library to the base HTML template of your site. The goal is to:

  1. To ensure that the airgap.js script is loaded on every page of your site; and
  2. To ensure that the airgap.js script is loaded first on every page of your site, before any other content or scripts which might result in network requests, e.g. images, even the favicon, CSS, or other Javascript libraries.

To the extent possible, we strongly encourage you to add the airgap.js script to as few places as possible in your codebase. e.g. if your site has an inheritance hierarchy of HTML page templates, you add it as close to the top as possible, so ideally to the base or root template, and not to each individual leaf template.