how-it-works
- What Is Loupely
- What Is Loupely Lens
- How Credits Work
- Understanding Credits and Plans
- The Browser Capture Layer
- The Server Capture Layer
- Cross-Signal Correlation: What It Is and Why It Matters
- How a Diagnosis Is Generated
- How Triage Recommendations Are Determined
- The 60-Second Capture Buffer
- Browser-Only Mode
- PHP Errors and Warnings
- JavaScript Errors
- WooCommerce Save Pipeline Events
- Hook Execution and Failures
- REST API Requests and Responses
- Authentication and Session Failures
- The Diagnosis Popup: Anatomy
- Triage Routes: What Each One Means
- The Two Keys: Connection Key vs. License Key
- The Admin Event Log
- Email Delivery Events
- Using Credits Across Both Products
- Cron Failures and Scheduled Event Problems
- Using Loupely on Multiple Sites
- Correlation Rules: How Loupely Connects Browser and Server Signals
- The Agency Annual Plan
- What Loupely Captures and Stores
- Using Loupely Without a WordPress Site
- Using Loupely on a Staging Site
- How the Credential Scanner Works
- Glossary: WordPress Hooks, Actions, and Filters
- Glossary: The WordPress REST API
- Glossary: AJAX in WordPress
- Magic Link Authentication
- Account Security and the Magic Link
- What Data Loupely Collects About You
- Third-Party Services Loupely Uses
- The Capture File: What’s in It and How to Use It
- Annual Plans: What’s Included and How They Work
- Loupely and Your Site’s Data
- The WordPress Plugin’s Security Footprint