Clym Pulse
Clym Pulse is a free Google Chrome extension designed for developers, QA teams, and privacy professionals to inspect and validate Consent Management Platform (CMP) behavior on live websites in real time.
Overview
Clym Pulse provides real-time visibility into consent signals, third-party script execution, auto-blocking rules, and privacy framework compliance without requiring manual inspection in Chrome DevTools.
- Cost: Free
- Account Required: No
- Supported CMPs: Works with Clym and third-party CMP implementations.
Key Capabilities
1. Clym Widget Health
When running on sites using Clym, Pulse evaluates:
- Detection & Placement: Identifies script presence and placement in the DOM.
- Loading Mode: Verifies synchronous vs. asynchronous script loading for reliable consent gating.
- Version Control: Reports active Clym script versions.
- UI Mode: Validates native display mode settings for initial notification banners.
2. Auto-Blocking & Consent Posture
- Inspects default consent posture (
opt-invs.opt-out). - Displays current visitor consent decisions and detected geo-location.
- Evaluates script execution states under implicit vs. explicit auto-blocking rules.
3. Third-Party Service Classification
- Detects active third-party tags and classifies them into processing categories (
Advertising,Analytics,Entertainment,Essential,Functional). - Displays real-time status (
Activevs.Blocked) for individual service scripts. - Maps embedded tags to corresponding processing categories.
4. Privacy Framework Signals
Monitors and decodes live consent parameters across industry standards:
- IAB TCF: API availability, GDPR applicability, and consent string payload.
- IAB GPP: API status and GPP string values.
- Google Consent Mode v2: Default and updated states for
ad_storage,ad_personalization,ad_user_data, andanalytics_storage. - Microsoft Consent Mode v2: Signal status and dynamic state updates.
Quickstart
1. Installation
Install the extension directly from the Chrome Web Store.
2. Inspecting a Website
- Open the target site in a clean browser session (or Incognito mode) to test initial visit behavior.
- Click the Pulse extension icon in the toolbar.
- Review detected scripts, active frameworks, and blocking rules.
3. Testing Consent Enforcement
- Open Clym Pulse.
- Interact with the site’s consent banner (e.g., Accept All, Reject Non-Essential, or custom preferences).
- Monitor the Pulse panel to confirm script status transitions (
Active$\leftrightarrow$Blocked) and framework string updates.
Common Implementation Checks
| Symptom | Diagnostic Step |
|---|---|
| Widget Not Detected | Verify script placement in the HTML head; ensure tag managers are not blocking script execution prior to load. |
| Async Loading Flagged | Ensure the Clym core script is loaded synchronously to prevent race conditions during consent gating. |
| Third-Party Active Before Consent | Verify tag-manager firing triggers and confirm script categories in the CMP auto-blocking configuration. |
| Signals Not Updating | Validate initialization order for Google Consent Mode / IAB APIs prior to third-party script execution. |
Data Privacy & Local Execution
- Client-Side Processing: All analysis runs locally in the browser session.
- Data Transmission: Pulse does not send inspected page content, script payloads, or browsing data to Clym or third parties.
Need further assistance? Contact support@clym.io.
