Tag Volume monitoring is your early warning system for tag performance issues. It automatically tracks how often your tags fire and alerts you when something's not right and tags stop firing (suggesting broken implementations). When tags stop firing or fire significantly less than expected, this typically indicates broken tag implementations, trigger configuration problems, changes in site structure or user flow, or technical issues like JavaScript errors preventing tag execution.
This monitoring helps you catch issues before they impact your data quality or user experience, giving you peace of mind that your tracking is working as expected.
⏰ Estimated time: +/- 5 minutes per monitoring rule
What should you have done before getting started?
To set up Tag Volume monitoring effectively, you should have already completed the basic Code-Cube setup:
You'll need:
- At least one container configured in your monitoring setup
- Domain(s) added to your Code-Cube configuration
- Active tags running on your website
Important: If you haven't set up the basics yet, follow our client-side tag monitoring setup guide or server-side tag monitoring set-up guide first. This will ensure you have the necessary containers and domains configured.
Step 1: Access Tag Volume monitoring
- Navigate to the Code Cube portal and open the Tag Monitor configuration page
- Open the section ‘Tag Volume monitoring’
Step 2: Configure the monitoring settings
You can configure multiple rules. Each rules contains of a set of parameters.=
Container ID (required)
Select which container to monitor from the dropdown. This shows all containers you've previously set up in your “client-side error monitoring” or “server-side monitoring“ section.
Tip: If you don't see your container listed, you'll need to add it to one of your monitoring sections first.
Domain (required)
Choose the domain where you want to monitor tag volume. This dropdown contains all domains from your “general settings”.
Tip: If you don't see your container listed, you'll need to add it to the “general settings” section first.
Tag details (required)
Specify which tag you want to monitor:
- Tag name or tag ID: Choose if you want to set-up the rule based on a tag name or tag ID.
- Match condition: Choose how to identify your tag:
exactly matches- Perfect match for the tag name/IDmatches regex- Use regular expressions for (advanced) pattern matchingcontains- Matches tags that include your specified text anywhere in the name/ID- Value field: Enter the tag name or ID that matches your Google Tag Manager configuration
Important: Tag names and IDs are case-sensitive. Make sure to enter them exactly as they appear in your Google Tag Manager.
Trigger (optional)
Add specific conditions to monitor only certain parts of your domain. Leave the trigger empty to monitor the tag across your entire domain. Use triggers when you want to focus on specific sections like checkout pages or product categories.
- Trigger type:
page path- Specific URL pathsfull URL- Complete URLs- Match type:
exactly matches- Exact matchcontains- Partial matchstarts with- Beginning of URLends with- End of URL- Value: Enter the specific value to match
Frequency (required)
Set your monitoring schedule. Of course the frequency is dependent on the amount of times the tag fires (should the tag be firing each day or do you expect a conversion every hour?). Otherwise these guidelines might help you:
every hour- For critical tags that need immediate attentionevery day- For standard tracking tagsevery week- For less critical or low-traffic tags
Step 4: Save the monitoring rule
Click Save to activate your monitoring rule. Your tag volume monitoring will begin according to the frequency you selected.
Managing monitoring rules
Adding multiple rules
Create additional rules by clicking "+ Add monitoring rule" again. Each rule can monitor different tags, containers, or domains with unique settings.
Rule management options
For each monitoring rule, you can use the action icons in the top-right corner:
- 📋 Copy rule: Duplicate an existing rule to create a similar one with modified settings
- ⏸️ Pause rule: Temporarily disable monitoring without deleting the rule
- 🗑️ Delete rule: Permanently remove the monitoring rule
Editing existing rules
Modify any rule by clicking directly on the fields you want to change.
Best practices
Start with your most critical tags
Focus on tags that directly impact your business like conversion tracking, primary analytics, and marketing attribution tags.
Choose appropriate monitoring frequencies
Match frequency to tag criticality: hourly for revenue-critical tags and real-time campaigns, daily for standard analytics tags, and weekly for secondary or low-traffic tags. Of course the monitoring frequency also depends a lot on the amount of visitors on the domain.
Use strategic triggers
Monitor high-traffic pages separately from low-traffic ones, create specific rules for conversion funnels, and exclude admin or test environments to reduce noise.
Tip: Overly broad monitoring can create noise. Use triggers to focus on the pages and user journeys that matter most to your business.
Regular maintenance
Review monitoring rules monthly, remove deprecated tags, and adjust frequencies based on traffic pattern changes and business needs.
Troubleshooting
Rule not generating expected alerts?
Verify the tag name/ID matches exactly (including case), check that the correct container and domain are selected, and confirm the tag is actually firing using browser developer tools.
Too many false alerts?
Adjust monitoring frequency to be less sensitive, add specific triggers to exclude low-traffic or test pages, and review if tag behavior has legitimately changed.
Missing alerts for known issues?
Double-check tag identifier accuracy, verify monitoring frequency isn't too infrequent for the issue type, and confirm the tag is within the monitored container and domain scope.
Next steps
Once your Tag Volume monitoring is active, monitor initial results for the first week to understand normal patterns, then fine-tune your settings based on actual performance. Expand coverage to additional critical tags and consider integrating alerts with your team's workflow tools.
Your tag monitoring setup provides the foundation for reliable, data-driven insights. Well-configured Tag Volume monitoring ensures you'll know immediately when something needs attention, before it impacts your business decisions.