Analytics and Tracking

Full Fabric can load three analytics tools on its pages: Google Tag Manager, Google Analytics and Hotjar. Each is switched on for the whole institution and reports to your own account with that tool. Google Tag Manager and Google Analytics measure applicants, students and visitors: they never load for staff, and they follow the choices people make under your cookie policy. Hotjar loads for everyone, staff included, and does not wait for cookie consent.

At a Glance

Integration Loads for Waits for cookie consent
Google Tag Manager Everyone who is not staff, signed in or not Yes, once a cookie policy is published
Google Analytics Everyone who is not staff, signed in or not Yes, once a cookie policy is published
Hotjar Everyone, staff included No

All three live in Settings → Other integrations, under the Analytics heading. Each page has the same header: an Active or Inactive badge and an Enable or Disable button. Disabling asks for confirmation first. A tool only loads once it is enabled and its ID is saved.

Google Tag Manager and Google Analytics follow the cookie policy published in Settings → Institution → Policies:

  • No cookie policy published: both load for every visitor who is not staff, with all consent granted. While this is the case, their settings pages show a No cookie policy is published warning.
  • Cookie policy published: they wait until the person accepts the matching cookie types, then load straight away, without a page reload. Google Tag Manager loads once analytical or advertising cookies are accepted; Google Analytics needs analytical cookies.

Google Tag Manager also receives Google consent mode signals. Full Fabric first sets every consent type to denied, then grants only what the person accepted: analytical cookies grant analytics storage, and advertising cookies grant ad storage, ad user data and ad personalisation. If your cookie policy uses the IAB Transparency and Consent Framework (TCF), the person's TCF choices are also available to the tags on the page.

Warning: Hotjar does not check cookie choices. When it is enabled it loads on every page for everyone, including staff and signed-out visitors.

Google Tag Manager

  1. Open Settings → Other integrations → Google Tag Manager.
  2. In the Container card, click Add container ID, enter the Container ID from your Google Tag Manager workspace (it looks like GTM-XXXXXXX) and click Save container ID.
  3. In the Data layer card, choose the Version and whether to Send personal data.
  4. Click Enable.

Events Full Fabric Sends

Besides loading your container, Full Fabric pushes events to the data layer. An event is only recorded while Google Tag Manager is enabled, and it is pushed once, in the browser of the person it concerns, on a later page load.

Event Recorded when
profile_creation Someone creates an account through the sign-up form
profile_login Someone signs in through the sign-in form
application_started Someone starts a new application or registration, if its template sends GTM events
application_submitted An applicant reaches the confirmation page after submitting, if the template sends GTM events
payment A payment is completed

Application events are off for every template until you turn them on. In Settings → Templates & documents → Application templates (or Registration templates), open the template, expand Administration and set Send GTM events for this application template? (or ...registration template?) to Yes. Payment events do not depend on this option.

Data Layer Version

Version chooses the format of the events. The newest is marked (latest) and applies until you choose another. The Learn about the versions link under the field opens a help article on each version.

Version Format
1.2025 Events are pushed as recorded. Payment amounts are in the currency's smallest unit (for example cents).
2.2025 application_started, application_submitted and payment carry an ecommerce object with an items list: the programmes or courses applied for, each with ID, name, category, price, currency, discount and quantity. Payments also carry the value and discount in currency units and, for application and deposit fees, which of the two it was. Each of these events includes the person's ID and email, both SHA-256 hashed.

With version 2.2025, Send personal data (off by default) adds the person's first and last name to those events. The email address is only ever sent hashed.

Google Analytics

  1. Open Settings → Other integrations → Google Analytics.
  2. In the Property card, click Add tracking ID, enter the Tracking ID from your Google Analytics admin and click Save tracking ID.
  3. Click Enable.

Note: Google Analytics records one page view when a page first loads. Moving between screens without a full page reload does not record further page views.

Disabling stops Google Analytics loading on applicant and student pages.

Hotjar

  1. Open Settings → Other integrations → Hotjar.
  2. In the Site card, click Add site ID, enter the Site ID from your Hotjar account (under Sites & Organizations) and click Save site ID. The ID is numbers only.
  3. Click Enable.

Hotjar then loads on every Full Fabric page, for staff, applicants, students and signed-out visitors alike. Disabling stops all session recordings and surveys.

Note: Institutions created on production start with Hotjar active and a Full Fabric site ID already saved. Replace the Site ID with your own, or disable Hotjar, if you do not want sessions recorded under that site.

Common Problems

What you see Usual cause Fix
No Google Tag Manager or Google Analytics while testing You are signed in as staff, and neither loads for staff Test signed out, or with an applicant account
No cookie policy is published warning on the page Google Tag Manager or Google Analytics is enabled and no cookie policy is published, so it loads for everyone Publish a cookie policy in Settings → Institution → Policies
Tags stop loading after a cookie policy is published People have not accepted analytical or advertising cookies yet Expected: tags load once they accept
Use numbers only. under Site ID The Hotjar ID contains letters or symbols Copy the numeric site ID from Hotjar
The save button stays disabled The required ID is empty, or unchanged Enter or change the ID
No application events in the data layer The template's GTM events are off, or Google Tag Manager was disabled when the event happened Turn the template option on; past events are not recorded afterwards
The changes could not be saved. or another error in the card The save was refused, for example because your role cannot change institution settings See Permissions below

Permissions

Opening these pages needs Global integrations (core.institutions.global_integration_settings). Saving goes through the institution settings, so the role also needs permission to change institution settings; without it the page opens but changes are refused. See Permissions.