JP Agent Tracking Bridge (docs) - Tracking Verification
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 24 of 51
Tracking Verification
A configured event is not automatically a verified event.
JP Agent Tracking Bridge uses several verification levels:
- CONFIGURED - The required configuration exists.
- BROWSER VERIFIED - A real browser interaction produced the expected Bridge/dataLayer event.
- GTM VERIFIED - Google Tag Manager processed the expected event and tag.
- DESTINATION VERIFIED - The destination, such as Google Analytics, received the event.
- END-TO-END VERIFIED - The complete real interaction has been verified through the full tracking chain.
- INCONCLUSIVE - Available testing was not sufficient to confirm the result.
Configured does not mean verified.
