Skip to main content

Installation: Google Tag Manager Trigger Configuration

Updated this week

This guide shows you how to set up triggers in Google Tag Manager to load your Sona tracking script on specific pages instead of site-wide. You'll learn to create precise page-based triggers and avoid common configuration mistakes that prevent proper script loading. With this approach, you'll have complete control over where your tracking script fires while maintaining clean, organized tag management.

When to Use This / Prerequisites

Use GTM triggers when you want to:

  • Load Sona tracking on specific pages rather than your entire website

  • Test tracking implementation on select pages before full deployment

  • Exclude certain pages from tracking for privacy or performance reasons

  • Maintain granular control over script loading across different site sections

Prerequisites:

  • You must have Google Tag Manager installed on your website and admin access to your GTM container.

Step-by-Step Instructions

Step 1: Access the triggering settings

  • While creating a new tag or editing an existing one, click Triggering

Step 2: Start creating a new trigger

  • Click the + icon on the upper right corner of the Choose a trigger screen to create a new trigger

Step 3: Open trigger configuration

  • Click Trigger Configuration

Step 4: Select trigger type

  • In Choose a trigger type, click Page View

Step 5: Name your trigger

  • Add a descriptive name for the trigger (e.g., "Sona Tracking - Product Pages")

Step 6: Set page view conditions

  • Click Some Page Views to target specific pages

Step 7: Choose targeting method

  • Select Page URL from the dropdown

Step 8: Select operation type

  • Select an operation from the dropdown list (contains, equals, starts with, etc.)

Step 9: Define URL criteria

  • Enter the URL keywords that will trigger the tag

Step 10: Save your configuration

  • Click Save to complete your trigger setup

Great work! Your trigger is now configured and ready to fire the Sona tracking script on your specified pages.

Key Concepts / Best Practices

  • Creating Multiple Triggers for Different Pages

    If you want to load the script on multiple distinct page types, create separate triggers for each one. This ensures reliable firing and makes troubleshooting much easier.

  • Critical Configuration Warning

    Never add multiple page URLs to a single trigger using "AND" logic. When you add multiple URL conditions to one trigger, ALL conditions must be met simultaneously for the trigger to fire, which is impossible since a visitor can only be on one page at a time. This will prevent your script from loading entirely.

  • Best Practices for URL Targeting

    • Use "contains" operations for flexible matching across similar page types

    • Test your URL patterns thoroughly before deploying to production

    • Keep trigger names descriptive and organized for easy management

    • Use consistent naming conventions across your GTM setup

Did this answer your question?