Clym Web Compliance Tool

Audit Clym CMP integrations instantly. Verify consent signals, script placement, TCF/GPP/GCM, and third-party service detection.

As of June 2026, Clym Web Compliance Tool has users in the Developer Tools category.

Usersno change0%
Ratingno change0%
— reviews
Reviewsno change0%
Version
1.0.0
Manifest V3

History

1 snapshots

Tracking since Jun 10, 2026.

Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
DateUsersRatingReviewsVersion
Jun 10, 20261.0.0
Now1.0.0

Permissions & access

Permissions
scriptingstorageactiveTabwebRequest
Host access
<all_urls>

Screenshots

Clym Web Compliance Tool screenshot 1Clym Web Compliance Tool screenshot 2Clym Web Compliance Tool screenshot 3Clym Web Compliance Tool screenshot 4Clym Web Compliance Tool screenshot 5Clym Web Compliance Tool screenshot 6

About

Audit your Consent Management Platform in seconds. Clym Pulse is a free Chrome
extension that gives website owners, developers, QA teams, and privacy
professionals a live, structured view of how their CMP is actually behaving on
the page: which scripts loaded, which services were blocked or fired, and which
consent signals are being broadcast to ad tech, analytics, and global frameworks.

Just implemented a new CMP, switched vendors, or updated your tag configuration?
Click the Pulse icon and find out, in real time, whether your setup is doing
what you think it is.

Stay Ahead of Compliance Requirements.

────────────────────────────────────
WHY PULSE
────────────────────────────────────

CMP implementations break quietly. A script loads in the wrong position, a tag
fires before consent, a Consent Mode signal stays at "denied" when it should
flip, an IAB TCF string never transmits. By the time you notice, the data is
already gone and the compliance gap is already open.

Pulse surfaces these issues immediately, in plain language, without DevTools
acrobatics. It works with Clym, and it works with any other CMP on the market.

────────────────────────────────────
WHAT PULSE CHECKS
────────────────────────────────────

CMP widget health
See whether the Clym widget is implemented, where the script is loading, whether
it loads synchronously, which script version is running, and whether the initial
notification is shown in native mode. Critical setup issues (wrong load position,
missing widget, version mismatch) are flagged with clear red and green
indicators.

Auto-blocking and consent posture
Inspect the service auto-blocking mode (implicit vs explicit), the default
consent status (opt-in vs opt-out), the visitor decision, and the detected
visitor location. Confirm the right jurisdictional rules are being applied.

Processing categories
At a glance, see how many services fall into each processing category
(Advertising, Analytics, Entertainment, Essential, Functional) and which embedded
tags (for example, Google Consent Mode Advertising) are tied to each category.

Live service detection
Pulse lists every third-party service it detects on the page, including Google
Analytics, Facebook, Hotjar, Smartlook, 360dialog, and many more. Each service is
labeled Active or Blocked in real time, with its detected scripts expandable to
show the actual code that loaded.

Consent state changes in real time
Click Accept, Reject, or change preferences in your cookie banner. Pulse updates
instantly, moving services from Blocked to Active (or the reverse), so you can
watch consent enforcement happen live. This is the fastest way to prove your
banner is actually wired up correctly.

────────────────────────────────────
GLOBAL FRAMEWORK SUPPORT
────────────────────────────────────

Pulse natively inspects the consent frameworks that matter most for modern web
compliance and ad tech measurement.

IAB TCF (Transparency and Consent Framework)
- TCF stub detection
- TCF iframe detection
- __tcfapi function presence
- TCF API status and TCData status
- GDPR applicability flag
- Live TCF string

IAB GPP (Global Privacy Platform)
- GPP stub detection
- GPP iframe detection
- __gpp function presence
- GPP API status and GPP data status
- Live GPP string

Google Consent Mode v2
- Detection of Consent Mode v2
- Default signal timing
- Default signal values
- Live values for ad_storage, ad_personalization, ad_user_data, and
  analytics_storage as they change

Microsoft Consent Mode v2
- Detection of Microsoft Consent Mode v2
- MCM default signals
- State change monitoring

If any of these are missing, misconfigured, or transmitting the wrong values,
Pulse will tell you immediately.

────────────────────────────────────
WHO PULSE IS FOR
────────────────────────────────────

Website owners and merchants
Just rolled out a new banner or switched CMP vendors? Confirm in under a minute
that essentials are blocked before consent, that advertising tags wait for
acceptance, and that your Consent Mode signals reflect real user choices.

Developers and QA engineers
Validate consent gating during builds and releases. Reproduce issues with a
structured view that shows exactly which scripts loaded and which were blocked.
Compare environments. Sign off on releases with evidence in hand.

Compliance and privacy professionals
Run fast implementation reviews on your own sites or on vendor properties.
Document third-party data flows, processing categories, and consent framework
support. Produce evidence for audits, DPIAs, and vendor assessments.

Agencies, MSPs, and consultants
Audit client sites in seconds before kickoff. Demonstrate value mid-engagement
by showing exactly what was broken and what is now fixed. No screen recording
or DevTools spelunking required.

────────────────────────────────────
TYPICAL USE CASES
────────────────────────────────────

- Post-launch validation of a new CMP rollout
- Pre-release QA: confirm tags only fire after consent
- Migration checks when switching consent vendors
- Verifying Consent Mode v2 is sending the right defaults and updates
- Confirming IAB TCF and GPP strings are present and well-formed
- Vendor and partner due diligence on third-party scripts and trackers
- Reproducing tracking complaints from users or regulators
- Training and education: showing non-technical stakeholders what a banner
  is actually doing under the hood

────────────────────────────────────
HOW IT WORKS
────────────────────────────────────

1. Install Pulse from the Chrome Web Store
2. Open any website
3. Click the Pulse icon in your Chrome toolbar
4. The panel slides open with a live read on widget status, services,
   processing categories, and consent framework signals
5. Interact with the page's cookie banner and watch the panel update in
   real time

No account, no configuration, no setup. Pulse runs the moment you open it.

────────────────────────────────────
WORKS WITH ANY CMP
────────────────────────────────────

Pulse was built by Clym, the compliance platform behind ReadyCompliance® and
RealtimeCompliance™, but it is not limited to Clym sites. Pulse inspects any
page, detects whichever CMP is installed, and reports on the universal signals
that ad tech and regulators care about: IAB TCF, IAB GPP, Google Consent Mode
v2, and Microsoft Consent Mode v2.

If you are running Clym, Pulse adds extra visibility into widget health,
auto-blocking mode, and processing categories. If you are running another CMP,
Pulse still surfaces every consent framework signal the page transmits.

────────────────────────────────────
PRIVACY AND PERMISSIONS
────────────────────────────────────

Pulse performs its analysis locally in your browser. The pages you visit, the
cookies you inspect, and the scripts you audit are not sent to Clym or to any
third party.

Permissions are limited to what is required to inspect the active tab and
remember your panel preferences between sessions. Pulse does not request access
to your browsing history, your identity, or other extensions.

────────────────────────────────────
BACKED BY CLYM
────────────────────────────────────

Pulse is built and maintained by Clym, a SaaS compliance platform trusted by
businesses across data privacy, accessibility, and transparency.

- ReadyCompliance®: pre-configured settings for 150+ global regulations,
  including GDPR, UK GDPR, CCPA / CPRA and other US state laws, LGPD, PIPEDA,
  POPIA, the Australia Privacy Act, and more
- RealtimeCompliance™: continuous monitoring and classification of 1,200+
  third-party services
- Average support response time under one hour
- 30-minute deployment for the full Clym platform: a single JavaScript snippet
  or DNS setting

Clym is SOC 2 Type II audited (Security, Availability, Confidentiality).
Customer data on the Clym platform is encrypted at rest (AES-256) and in
transit (TLS 1.2+).

If Pulse uncovers gaps on your site, Clym's platform can help you close them
with consent management, accessibility, data subject request handling,
governance reporting, and more, all from one integration.

────────────────────────────────────
SUPPORT AND FEEDBACK
────────────────────────────────────

We read every review and every support message. If Pulse misclassifies a
service, misses a framework signal you rely on, or could use a feature you
need, tell us.

- Website: https://www.clym.io
- Contact: https://www.clym.io/contact
- Documentation: https://knowledge.clym.io/en/article/pulse-jerqdi
- Book a demo of the full Clym platform: https://www.clym.io/contact

Clym does not provide legal advice. Pulse is a technical tool to help you
understand and document the behavior of websites you operate and visit. For
legal interpretation of compliance obligations, consult qualified counsel.

Audit your CMP implementation with confidence. Install Clym Pulse and see
what your website is really doing.

Stay on the safe side®.

Technical

Version
1.0.0
Manifest
V3
Size
827KiB
Min Chrome
111
Languages
1
Featured
No

Metadata

ID
gjlkjjdmhhnahkblladcaahagdbmfmem
Developer ID
u5013a613fc154a3219f411d4bd8d9567
Developer Email
[email protected]
Created
Jun 9, 2026
Last Updated (Store)
Jun 9, 2026
Last Scraped
Jun 10, 2026
Website
clym.io

Data sourced from the Chrome Web Store · last verified Jun 10, 2026.