Overview
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 will learn to create precise page-based triggers and avoid common configuration mistakes that prevent proper script loading. With this approach you get complete control over where your tracking script fires while keeping your tag management clean and organized.
When to use this
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.
Note: you must have Google Tag Manager installed on your website and admin access to your GTM container.
Creating a page-based trigger
Follow these steps to fire the Sona tag on selected pages:
Access the triggering settings. While creating a new tag or editing an existing one, click Triggering.
Start creating a new trigger. Click the + icon in the upper-right corner of the Choose a trigger screen.
Open trigger configuration. Click Trigger Configuration.
Select the trigger type. In Choose a trigger type, click Page View.
Name your trigger. Add a descriptive name, for example "Sona Tracking - Product Pages".
Set page view conditions. Click Some Page Views to target specific pages.
Choose a targeting method. Select Page URL from the dropdown.
Select an operation type. Choose an operation from the dropdown, such as contains, equals, or starts with.
Define your URL criteria. Enter the URL keywords that will trigger the tag.
Save your configuration. Click Save to complete your trigger setup.
Best practices
Note: 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 at the same time for the trigger to fire, which is impossible since a visitor can only be on one page at a time. This prevents your script from loading entirely.
Multiple triggers: to load the script on several distinct page types, create a separate trigger for each one. This ensures reliable firing and makes troubleshooting much easier.
Flexible matching: use "contains" operations for flexible matching across similar page types.
Test first: test your URL patterns thoroughly before deploying to production.
Naming conventions: keep trigger names descriptive and use consistent naming conventions across your GTM setup for easy management.
FAQs
Why is my script not firing on any page?
Why is my script not firing on any page?
The most common cause is adding multiple page URL conditions to a single trigger with "AND" logic. Because all conditions would need to be true at once, and a visitor can only be on one page at a time, the trigger never fires. Split the URLs into separate triggers, one per page type, so each can fire on its own.
Can I load Sona on only some pages?
Can I load Sona on only some pages?
Yes. Choose Some Page Views when configuring the trigger, then target pages by Page URL using an operation such as contains, equals, or starts with. Only pages matching your criteria will load the Sona script.
Should I create one trigger or several?
Should I create one trigger or several?
Create a separate trigger for each distinct page type you want to track. Separate triggers fire reliably and are far easier to troubleshoot than a single complex trigger, and they keep your GTM setup organized when paired with consistent naming.