JP Agent Tracking Bridge (docs) - Custom Tracking Scripts
Article Index
- JP Agent Tracking Bridge (docs)
- How JP Agent Tracking Bridge Works
- Requirements
- WordPress Installation
- Joomla Installation
- Basic Configuration
- Connecting Google
- Google Permissions
- Disconnecting Google
- Installing the Agent Tools
- Start Tagging
- Talking to Your AI Agent
- Tracking Overview
- Structured Tracking Rules
- Custom Tracking Scripts
- Successful Form Tracking
- YOOtheme Essentials Forms
- Email Click Tracking
- Phone Click Tracking
- Google Tag Manager
- Existing GTM Tags
- Publishing Google Tag Manager
- Google Analytics Verification
- Tracking Verification
- Recommended Verification Chain
- WooCommerce Tracking
- WooCommerce Ecommerce Data
- WooCommerce Purchase Statuses
- Consent and Cookie Management
- YOOtheme Pro
- Stop Tagging
- Security
- Google OAuth Security
- History
- Reset and Clear Log
- Working With Existing Tracking
- Troubleshooting
- Google Connection Problems
- Events Appear in dataLayer but Not GA4
- Form Tracking Does Not Fire
- WooCommerce Troubleshooting
- Frontend Layout Problems
- Recommended First Tracking Job
- Recommended WooCommerce Setup
- Developer and Agency Notes
- Agent API Concepts
- Google Tools MCP
- Privacy and Google Data
- Before Finishing a Tagging Session
- Quick Start
- Example Agent Request
- All Pages
Page 15 of 51
Custom Tracking Scripts
Some frontend interactions cannot be reliably detected using a simple click or page rule.
JP Agent Tracking Bridge therefore supports controlled custom tracking scripts for cases such as:
- AJAX form success events
- Custom frontend widgets
- JavaScript application state changes
- Third-party components that expose their own browser events
Custom scripts should be used only when a structured Bridge rule cannot represent the required behavior cleanly.
Custom JavaScript added through the Bridge is still managed as a Bridge tracking resource and can be reviewed, disabled or removed.
