Google Tag Manager

Overview

Google Tag Manager (GTM) provides a flexible way to deploy Trodo without modifying your website’s source code. This guide covers setup, configuration, and best practices.

Quick Setup

Open Google Tag Manager

Go to tagmanager.google.com and select your container

Create New Tag

Click Tags → New → Tag Configuration → Custom HTML

Add Trodo Script

Paste the following code:

<script>
  var script = document.createElement('script');
  script.src = 'https://cdn.trodo.ai/scripts/analytics/trodo.script.min.js';  
  script.setAttribute('site-id', 'YOUR_SITE_ID');
  script.setAttribute('auto-events', 'true');
  document.head.appendChild(script);
</script>

Replace YOUR_SITE_ID with your actual Site ID from Trodo dashboard.

Set Trigger

Click Triggering → All Pages (or your preferred trigger)

Save and Publish

Click Save, then Submit to publish your changes

Configuration Options

Basic Configuration

<script>
  var script = document.createElement('script');
  script.src = 'https://cdn.trodo.ai/scripts/analytics/trodo.script.min.js';  
  script.setAttribute('site-id', 'YOUR_SITE_ID');
  script.setAttribute('auto-events', 'true');
  document.head.appendChild(script);
</script>

Full Configuration

<script>
  var script = document.createElement('script');
  script.src = 'https://cdn.trodo.ai/scripts/analytics/trodo.script.min.js';  
  script.setAttribute('site-id', 'YOUR_SITE_ID');
  script.setAttribute('auto-events', 'true');
  script.setAttribute('auto-events-disabled-paths', '/admin,/internal,/checkout');
  script.setAttribute('auto-events-disabled-events', 'text_selection,copy_action');
  document.head.appendChild(script);
</script>

Configuration Attributes

Attribute	Type	Default	Description
`site-id`	string	required	Your Trodo site identifier
`auto-events`	boolean	`true`	Enable automatic event tracking
`auto-events-disabled-paths`	string	`''`	Comma-separated URL paths to exclude
`auto-events-disabled-events`	string	`''`	Comma-separated auto-events to disable

Using GTM Variables

You can use GTM variables in your configuration:

Site ID from Variable

Create a Constant variable for your Site ID
Reference it in the tag:

<script>
  var script = document.createElement('script');
  script.src = 'https://cdn.trodo.ai/scripts/analytics/trodo.script.min.js';  
  script.setAttribute('site-id', '{{Trodo Site ID}}');
  script.setAttribute('auto-events', 'true');
  document.head.appendChild(script);
</script>

Environment-Based Configuration

Use GTM’s environment feature for staging vs production:

<script>
  var siteId = '{{Trodo Site ID}}'; // Different per environment
  var script = document.createElement('script');
  script.src = 'https://cdn.trodo.ai/scripts/analytics/trodo.script.min.js';  
  script.setAttribute('site-id', siteId);
  script.setAttribute('auto-events', 'true');
  document.head.appendChild(script);
</script>

Custom Event Tracking

Via Data Layer

Push events to GTM’s data layer, then forward to Trodo: On your website:

dataLayer.push({
  event: 'trodo_event',
  eventName: 'button_clicked',
  eventProperties: {
    button_name: 'signup',
    button_location: 'header'
  }
});

GTM Tag (Custom HTML):

<script>
  if (window.Trodo) {
    var eventName = '{{DL - eventName}}';
    var eventProps = '{{DL - eventProperties}}';
    window.Trodo.track(eventName, eventProps);
  }
</script>

Trigger: Custom Event = trodo_event

Direct Tracking

After Trodo loads, you can track directly:

<script>
  // Wait for Trodo to be available
  function trackWithTrodo(eventName, properties) {
    if (window.Trodo) {
      window.Trodo.track(eventName, properties);
    } else {
      setTimeout(function() {
        trackWithTrodo(eventName, properties);
      }, 100);
    }
  }
  
  trackWithTrodo('gtm_custom_event', {
    source: 'gtm',
    trigger: '{{Trigger Name}}'
  });
</script>

User Identification

Identify Users via GTM

Create a tag to identify users when they log in:

<script>
  if (window.Trodo && '{{User ID}}') {
    window.Trodo.identify('{{User ID}}');
    window.Trodo.people.set({
      email: '{{User Email}}',
      name: '{{User Name}}',
      plan: '{{User Plan}}'
    });
  }
</script>

Trigger: Custom Event = user_logged_in

Custom product events

Fire Trodo.track() from a tag when a data layer event occurs (for example activation or agent completion):

<script>
  if (window.Trodo) {
    window.Trodo.track('{{Event Name}}', {
      workflow_id: '{{Workflow ID}}',
      outcome: '{{Outcome}}'
    });
  }
</script>

Trigger: Your custom event (e.g. agent_run_completed)

Trigger Configurations

All Pages (Recommended)

Load Trodo on every page:

Trigger Type: Page View
Trigger fires on: All Page Views

Specific Pages Only

Load only on certain pages:

Trigger Type: Page View
Trigger fires on: Some Page Views
Condition: Page Path contains /app

Exclude Pages

Exclude admin or internal pages:

Create trigger: Page View - Some Page Views
Condition: Page Path does not contain /admin
AND Page Path does not contain /internal

Load only after consent:

Trigger Type: Custom Event
Event name: consent_granted

// After user grants consent
dataLayer.push({ event: 'consent_granted' });

Tag Sequencing

Load Order

Ensure Trodo loads before dependent tags:

Open your Trodo tag
Go to Advanced Settings → Tag Sequencing
Check “Fire a tag before [Trodo] fires” if needed
Check “Fire a tag after [Trodo] fires” for dependent tags

Wait for Trodo

For tags that depend on Trodo:

<script>
  function waitForTrodo(callback) {
    if (window.Trodo) {
      callback();
    } else {
      setTimeout(function() {
        waitForTrodo(callback);
      }, 50);
    }
  }
  
  waitForTrodo(function() {
    // Your code that needs Trodo
    window.Trodo.track('dependent_event');
  });
</script>

Debugging

GTM Preview Mode

Click Preview in GTM
Navigate to your website
GTM debug panel shows:
- Tag firing status
- Variable values
- Data layer events

Verify Trodo Loading

In browser console:

// Check if Trodo loaded
console.log(window.Trodo); // Should show Trodo object

// Check initialization
console.log(window.Trodo.getSiteId()); // Should show your Site ID

Network Tab

Check for requests to:

cdn.trodo.ai (script load)
api.trodo.ai (event tracking)

Common Issues

Tag not firing

Check trigger conditions in GTM Preview
Verify container is published
Check for JavaScript errors in console

Events not appearing in Trodo

Verify Site ID is correct
Check domain is whitelisted in Trodo
Look for blocked requests (ad blockers)
Verify in Network tab that API calls succeed

Double tracking

Ensure Trodo is only loaded once
Check for duplicate tags in GTM
Don’t load via both GTM and direct script

Script blocked by CSP

Add to your Content Security Policy:

script-src 'self' https://cdn.trodo.ai;
connect-src 'self' https://api.trodo.ai;

Best Practices

Use Folders

Organize your Trodo tags:

Tags/
├── Trodo/
│   ├── Trodo - Base Script
│   ├── Trodo - Identify User
│   ├── Trodo - Track Signup
│   └── Trodo - Track Purchase

Naming Convention

Use clear, consistent names:

✅ Good:
"Trodo - Base Script (All Pages)"
"Trodo - Track Button Click"
"Trodo - Identify Logged In User"

❌ Poor:
"Tag 1"
"New Tag"
"Custom HTML"

Version Control

Use GTM’s built-in versioning:

Add descriptions to each version
Name versions meaningfully: “Added Trodo tracking”
Use workspaces for team collaboration

Testing

Always test before publishing:

Use GTM Preview mode
Test on staging environment first
Verify events appear in Trodo
Check for console errors

Next Steps

Auto-Events

Configure automatic tracking

SDK Reference

Track custom events

TAG MANAGERS

​Overview

​Quick Setup

​Configuration Options

​Basic Configuration

​Full Configuration

​Configuration Attributes

​Using GTM Variables

​Site ID from Variable

​Environment-Based Configuration

​Custom Event Tracking

​Via Data Layer

​Direct Tracking

​User Identification

​Identify Users via GTM

​Custom product events

​Trigger Configurations

​All Pages (Recommended)

​Specific Pages Only

​Exclude Pages

​Consent-Based Loading

​Tag Sequencing

​Load Order

​Wait for Trodo

​Debugging

​GTM Preview Mode

​Verify Trodo Loading

​Network Tab

​Common Issues

​Best Practices

​Use Folders

​Naming Convention

​Version Control

​Testing

​Next Steps