Drupal is a registered trademark of Dries Buytaert
cms 2.1.3 Update released for Drupal core (2.1.3)! drupal 10.5.11 Update released for Drupal core (10.5.11)! drupal 11.3.11 Update released for Drupal core (11.3.11)! drupal 11.2.13 Update released for Drupal core (11.2.13)! drupal 10.6.10 Update released for Drupal core (10.6.10)! cms 2.1.2 Update released for Drupal core (2.1.2)! drupal 11.1.10 Update released for Drupal core (11.1.10)! drupal 10.5.10 Update released for Drupal core (10.5.10)! drupal 10.4.10 Update released for Drupal core (10.4.10)! drupal 11.2.12 Update released for Drupal core (11.2.12)! drupal 11.3.10 Update released for Drupal core (11.3.10)! drupal 10.6.9 Update released for Drupal core (10.6.9)! drupal 10.6.8 Update released for Drupal core (10.6.8)! drupal 11.3.9 Update released for Drupal core (11.3.9)! drupal 11.3.8 Update released for Drupal core (11.3.8)! drupal 11.3.7 Update released for Drupal core (11.3.7)! drupal 11.2.11 Update released for Drupal core (11.2.11)! drupal 10.6.7 Update released for Drupal core (10.6.7)! drupal 10.5.9 Update released for Drupal core (10.5.9)! cms 2.1.1 Update released for Drupal core (2.1.1)!

gtl

1 sites No security coverage
View on drupal.org

This module adds the capability to only track visitors from a certain geographic location (Switzerland) with the Google Tag Manager. It sets a cookie (gtl) and fires a dataLayer event (gtl_allowed) when a trackable user is first identified.

Dependecies

  • smart_ip (for IP geo lookup)
  • google_tag (or similiar for GTM integration)

Installation

  1. Setup the smart_ip module.
    • Install an IP datasource (e.g. MaxMind GeoIP2 Lite Country database)
    • Roles to Geolocate: anonymous and authenticated users
    • Acquire/update user's geolocation on specific Drupal native pages: /tracking/check
  2. Install this module
  3. Enable the /tracking/check:GET REST endpoint and allow access for anonymous visitors as well as authenticated users (in /admin/config/services/rest).
  4. Setup the Google Tag Manager container to support the new functionality

Google Tag Manager Setup

  1. Create a first-party cookie variable for the cookie name gtl.
  2. Create a custom event trigger for the event name gtl_allowed.
  3. Add the first-party cookie to existing triggers as a condition so that the trigger is only fired if the cookie value matches 1. Apply this to all triggers that are only allowed to fire for trackable visitors. (e.g. PDF link clicks)
  4. Add the custom event trigger to existing tags that only fire once per page visit. (e.g. Google Analytics pageview).

Activity

Total releases
1
First release
Nov 2025
Latest release
6 months ago
Release cadence
Stability
100% stable

Releases

Version Type Release date
4.1.0 Stable Nov 11, 2025