Google Tag Manager
Technical

Technical Specifications: GTM with Reuzenpanda Forms

On the technical side, 2.0, 1.0 and legacy are different applications. For ease of use, and for backwards support, we have kept the same event names and have some overlapping naming conventions.

Definitions

  • Standalone → A standalone hosted form page on:
  • directsamenstellen.nl (2.0)
  • offerte.directsamenstellen.nl (1.0)
  • product.directsamenstellen.nl / page.reuzenpanda.nl (legacy)
  • Popup widget → A popup widget on your site, installed through snippet, added to the page as an iframe
  • Embedded → An embedded configurator on your site, installed through snippet, added to the page as an iframe
  • Widget → A 1.0 form
  • Configurator → A 2.0 form

Overview

The Reuzenpanda configurator (2.0) and widget (1.0) both support GTM integration. This document details the technical setup for integrating GTM with Reuzenpanda forms.

For further assistance, contact Reuzenpanda Support at info@reuzenpanda.nl.

GTM Integration

GTM Configuration

Within the Reuzenpanda back office, there is a setting to install a custom GTM tag. These settings are only applicable for standalone configurators.

If the configurator is embedded via iframe (Snippet code), your GTM container must be manually installed on your site instead of from our backoffice to track correctly.

GTM Event Tracking

Reuzenpanda forms support regular GTM events and custom events to track user interactions. The custom events available for both 1.0 and 2.0 versions are:

  • configurator.load
  • configurator.use
  • configurator.conversion

Note: The 1.0 forms includes some additional events not listed here.

For each event, a dataLayer object is sent to:

  1. The Reuzenpanda GTM container (GTM-58DN284).
  2. Any additional GTM containers installed on the page.

If the Reuzenpanda snippet is installed, it will also install the Reuzenpanda GTM container on your site. When our GTM container consumes a dataLayer object, it will clone and forward it to any other GTM containers present on the page.

Configurator Lifecycle

The configurator lifecycle consists of the following stages:

  • configurator.load → Triggered when a user has the ability to open a widget or start interacting with a configurator.
  • configurator.use → Triggered when a user starts interacting with the configurator.
  • For standalone and embedded setups, this is effectively the same as configurator.load.
  • configurator.conversion → Triggered when a user completes a configuration (e.g., submits a form).

Note: which is applicable if you start measuring using custom click / DOM events for 2.0 configurators.

Embedded configurators initialize twice by default:

  • Once as popup widget
  • Once as embedded

However, by defaul there is no button to open the popup widget. This allows the embedded configurator to also programmatically turn into a popup widget on another page.

The configurator.load event will not trigger for the popup widget initialization on embedded pages as long as there is no button to separately open the popup present on the page.

DataLayer Structure

configurator.conversion Event

For conversion tracking, the following data is included:

  • configuration.configurator_id → The configurator (2.0) OR widget (1.0) ID.
  • configuration.values → The values of the configurator in key-value pairs, where:
  • Key = Field label (formatted in snake_case).
  • Value = User-selected value.
  • Note: The values object for 1.0 widgets only include the contact information, and not the product configuration. In contrast, 2.0 configurators include the full configuration (as long as the labels are unique, last value wins).

Metadata

Note: If using a standalone hosted installation with a custom GTM tag, metadata will not be included in the dataLayer.

For snippet-based installations, the dataLayer includes the following metadata:

  • gtm.widget → Widget OR configurator ID (deprecated as of Jan 2025).
  • gtm.widget_id → Widget OR configurator ID.
  • gtm.configurator_id → Configurator ID.
  • gtm.app → Application name (e.g., quotomator, lead-gen) to differentiate versions.

Data Layer Properties

1.0 (Widget)

gtm.configurator Widget Properties:

  • type → Widget type:
  • widget → Popup widget
  • embedded → Embedded on page
  • legacy → Legacy (product.directsamenstellen.nl widgets never upgraded to Reuzenpanda 1.0)
  • configurator → Standalone configurator
  • theme → Widget theme (e.g., barcelona, malaga, california, etc.)

2.0 (Configurator)

gtm.configurator Configurator Properties:

  • id → Configurator ID
  • isFramed → Boolean (true/false) indicating whether the configurator is in an iframe.
  • type → Configurator type:
  • standalone → Standalone configurator
  • reuzenpanda-widget → Widget form
  • reuzenpanda-embedded → Embedded form

A bit about legacy (product.directsamenstellen.nl/page.reuzenpanda.nl)

The legacy configurator is a standalone configurator that was never upgraded to Reuzenpanda 1.0's widget structure (may 2023). In 2023 all legacy popup widgets were migrated to Reuzenpanda 1.0 widgets. There are still, however, some standalone configurators in use that are not upgraded. These old standalone configurators use the recently removed UA (universal analytics) functionality in analytics, and thus is out of scope for GTM tracking.

Setup