How to set up Stape Conversion Tracking module for Drupal

1. Set up the server GTM container and host it on Stape.

2. To install the module, select the version you need from the releases page and use one of the installation options.

3. Configure the module. You will need to configure three sections: General Settings, Data Layer, and Webhooks.

3.1. General Settings section.

This section contains all the options for configuring the GTM snippet installation on every page of your Drupal site.

Add the following data:

• Active - turn on the switch to add the GTM snippet to every page on your Drupal website. 
• Web Container ID - add the GTM web container ID (you can find it in your GTM account in the tab Accounts). The format should be the following: GTM-XXXXXXX.
• Custom Domain - use the subdomain you have created for server-side tracking. It should start with https:// without any extra slashes at the end: https://gtm.example.com

• Custom Loader - this is Stape’s power-up used to minimize the impact of ad blockers on your tracking. This option is available only if you use Stape's sGTM hosting and set up the Custom Loader power-up. To enable this option, specify your container identifier in the Stape admin panel settings.

• Cookie Keeper - this is Stape’s power-up used to prolong cookie lifetime in Safari and other browsers with ITP. This option is available only if you use Stape's sGTM hosting and set up the Cookie Keeper power-up. Please also make sure to enable Stape User ID in your container power-ups. The User ID power-up creates a persistent, privacy-conscious user identifier and attaches it to each incoming request handled by your sGTM container.

3.2 Data Layer section.

In this section, you can see toggles that enable Data Layer events. With their help, you can enrich the data by incorporating product and user details. You can configure event names to get the _stape suffix to prevent any clashes in GTM. If it’s off, events keep their normal names. Also in this section, you can set the Product Collection Limit.

Here you can find a list of events and their payload, which are added via the app for Drupal.

3.3 Webhooks section.

In this section, you can set up webhooks sending to a specified URL for various events, such as purchases and/or refunds.

To enable webhook configuration, turn on the Enable Webhooks switch. After that, provide the GTM Server Container URL and /path where the webhooks should be sent in the format: https://gtm.example.com/data

Turn on the appropriate toggles based on the event type - Purchase Webhook and/or Refund Webhook.

If you would like to find out more about webhooks and configure them, please check our blog posts:

• What are webhooks, webhook servers, and how to use
• Debug incoming webhooks in Google Tag Manager server preview
• Server-to-server tracking in server Google Tag Manager

Click Save configuration.

4. Send data from web to server-side Google Tag Manager container. The two most common approaches to this are:

• Configuring server-side Google Analytics 4

• Using a Data Tag and Data Client

5. Configure data tracking within the server Google Tag Manager container.

Most popular marketing and analytics tools offer support for server-side tracking and provide tags for sGTM.

Test Drupal module configuration

Verify your configuration on the website

To confirm your setup, open any page on your website and access your browser's developer console. Navigate to the Network tab and search for your subdomain. If you see a request returning a 200 status code, your configuration is working correctly.

Debugging triggered events in GTM

Debugging events in GTM for a Drupal website follows the same process as with any other platform. To verify that your configured dataLayer events are being triggered, launch the GTM container in preview mode. Then, perform the necessary actions on your site (e.g., adding a product to the cart) and check if the corresponding tags are firing in GTM.