Set-up Tag Monitor (server-side)

This guide walks you through the full setup of Code Cube's Tag Monitor using Google Tag Manager server-side.

What will you do?

• Configure your domains and containers in the Code Cube portal
• Import the Tag Monitor template into your GTM server container
• Set up the tag with sampling and metadata
• Publish and verify your implementation

⏰ Estimated time: 10–15 minutes

🔧 Requirements: Access to your GTM Server container and Code Cube portal

Implementation

• Step 1 – Portal configuration
• Step 2 – Import template in GTM (Server)
• Step 3 – Configure the tag in GTM
• Step 4 – Configure tag metadata
• Step 5 – Deploy and verify

Step 1 – Portal configuration

Before configuring anything in GTM, define which domains and containers should be monitored with Code Cube’s Tag Monitor.

1.1 Domains & Time zone

• Go to the step 'General settings' on the Tag Monitor configuration page
• Add all domains you want to monitor
• Select the appropriate time zone

1.2 GTM container settings

• Go to the step 'Client-side error monitoring’ on the Tag Monitor configuration page
• Add the GTM container IDs you want to enable monitoring for

Step 2 – Import Code Cube template in GTM

Install the Tag Monitor tag template in your GTM container. This provides the logic needed to send tag data to Code Cube.

2.1 Download the template

• Go to 'Server-side error monitoring' in the Tag Monitor configuration page
• Click "Download template"

2.2 Import template to GTM

1. Open your GTM server-side container
2. Go to "Templates" > "Tag Templates"
3. Click "New"
4. Click the three dots > "Import"
5. Upload the downloaded file
6. Save without making any changes

Step 3. Configure the tag in GTM

Now configure how the Tag Monitor tag collects and sends data — including basic settings and sampling.

3.1 Create the tag

1. Create a new tag
2. Choose the imported Tag Monitor template as the tag type.
3. Fill in the required fields:
• Database name: Copy from the configuration page

• Consent: Set to 'No additional consent required’.
• Metadata: Add key exclude with value true

3.2 Set-up the trigger

Use a Custom Event trigger with regex matching and optional sampling to control data volume.

1. Create a new trigger
2. Trigger type: Custom Event
3. Event name: .* (match all)
4. Enable "Use regex matching"

Recommended Sampling Rates:

3.3 Enable required variables

Some built-in variables should be enabled, as these are used by Tag Monitor to identify the container the tag was fired from.

• Go to Variables > Built-in Variables
• Enable:
• Container ID
• Container Version

4. Configure Tag metadata

Add your tag names to the outgoing requests for easier debugging and reporting.

Option A: Automatic update (Recommended)

1. Go to 'Configure tag names' on the configuration page
2. Click Start bulk editing
3. Follow the guided process to update your GTM container via API

Option B: Manual Update

Step 5 – Deploy and verify

Once everything is configured, it’s time to go live and confirm everything works as expected.

5.1 Publish changes

• Submit and publish your GTM workspace
• Choose the right environment (usually production)

5.2 Verify

1. Open the Tag Monitor dashboard in the Code Cube portal
2. Look for incoming data from your configured domain and container
3. Check that tag names are being registered correctly

Step 2. Import Code Cube template in GTM

2.1 Download the template

1. Open the step 'Server-side monitoring' on the Tag Monitor configuration page.
2. Click the download button to download the Tag Monitor template

2.2 Import template to GTM

1. Open your Google Tag Manager server-side container.
2. Navigate to "Templates".
3. Click "New" in the "Tag Templates" section.

4. Click the three dots in the top right corner.
5. Select "Import" and choose the downloaded Tag Monitor template.
6. Save without making any modifications.

Step 3. Configure the tag in GTM

Set up the core Tag Monitor configuration to define how your implementation will collect and process data.

3.1 Create the tag

1. Create a new tag in your container.
2. Select the imported Tag Monitor template as the tag type.
3. Configure these required settings:
• Database Name / Dataset ID: Copy this value from the Code Cube configuration page, step 'Server-side monitoring'.
• Table Name / Table ID: Enter "raw_data_server"
• Metadata: Add key "exclude" with value "true"

3.2 Set-up the trigger

1. Create a new 'Custom Event' trigger
2. Configure to fire on all events:
• Event name: .*
• Enable "Use regex matching"
3. Add sampling for better performance:
• Enable the built-in variable "Random Number"
• Add rule: "Some custom events" where "Random Number" meets criteria.

Recommended Sampling Rates:

3.3 Enable required variables

1. Go to Variables > Built-in Variables
2. Enable:
• Container ID
• Container Version

4. Configure Tag Metadata

Choose ONE of these methods:

Option A: Automatic Update (Recommended)

1. Navigate to "Configure tag names" in the 'Server-side monitoring' section of the configuration page.
2. Click "Start bulk editing"
3. Follow the guided process to update your container via API

Option B: Manual Update

For each tag in your container:

1. Expand "Advanced Settings"
2. Check "Include tag name" under "Additional Tag Metadata"
3. Set the key name to "name"

Step 5: Deploy and Verify

5.1 Publish Changes

1. Submit and publish your workspace
2. Select the appropriate environment (typically production)

5.2 Verification

1. Open the Tag Monitor dashboard in Code Cube portal
2. Check that data is flowing in from your container
3. Verify that tag names are displaying correctly

Troubleshooting