Is consent required for Plerdy on my website?

Yes. Plerdy sets persistent identification cookies and records detailed visitor interactions including mouse movements, clicks, scroll depth, and session replays. This constitutes analytics tracking under GDPR and ePrivacy requiring prior consent. Session replay in particular may capture personal data entered into forms.

What cookies does Plerdy set?

Plerdy sets cookies including _plerdy_uid and related identifiers for persistent visitor identification across sessions. Its script from a.plerdy.com records click coordinates, scroll positions, form interactions, and DOM snapshots for session replay. Screen resolution, browser version, and referral source are also collected.

How does ConsentStack detect Plerdy?

ConsentStack categorizes Plerdy as analytics and detects its tracking script from a.plerdy.com. When analytics consent is granted, Plerdy initializes and begins recording heatmap and session replay data. Without consent, the script is fully blocked and no interaction data is captured or transmitted.

What tracker domains does Plerdy use?

ConsentStack has catalogued tracker domains for Plerdy including plerdy.com. These are the network destinations Plerdy's scripts contact, which a consent platform blocks until a visitor agrees.

Plerdy (a.plerdy.com) - Heatmap & Session Replay Consent

Back to Vendor Library

Overview

Plerdy provides a suite of on-site behavioral analytics tools focused on conversion rate optimization. The platform captures granular visitor interaction data through heatmaps, session recordings, funnel analysis, and event tracking. Plerdy positions itself as an alternative to tools like Hotjar and Crazy Egg, with additional SEO auditing capabilities built into its analytics dashboard.

What This Script Does

Plerdy's tracking script loads from a.plerdy.com and initializes with a site-specific tracking ID. Once active, it records detailed visitor interactions including mouse movements, clicks, scroll positions, form field interactions, text selections, and page navigation paths.

The script sets cookies (typically _plerdy_uid and related identifiers) to maintain persistent visitor identification across sessions. These cookies enable Plerdy to stitch together multiple visits from the same browser into a unified behavioral profile.

Session replay functionality captures a DOM snapshot stream — recording page structure changes, input interactions, and visual states throughout the visit. This data is compressed and transmitted to Plerdy's collection servers. Heatmap data aggregates click coordinates and scroll depth measurements across all visitors to generate visual interaction density maps.

Plerdy also monitors page load performance metrics and collects technical data including screen resolution, browser version, operating system, and referral source. Network requests are sent to a.plerdy.com endpoints carrying encoded interaction payloads.

Consent & Compliance

Plerdy's functionality is entirely analytics-focused. Session recordings, heatmaps, and behavioral tracking are not necessary for the website to function and exist solely to provide site operators with visitor behavior insights.

Under GDPR and the ePrivacy Directive, Plerdy's persistent tracking cookies and extensive behavioral data collection require explicit prior consent. Session replay in particular raises heightened privacy concerns as it captures detailed records of user interactions, potentially including personal data entered into forms. Under CCPA, the collection of device identifiers and behavioral profiles constitutes personal information collection requiring disclosure.

The consent category is analytics.

Should You Block This Without Consent?

Yes. Plerdy records detailed visitor behavior including mouse movements, clicks, scroll activity, and session replays. It sets persistent identification cookies and transmits comprehensive interaction data to external servers. All of this constitutes non-essential analytics tracking that requires prior consent under GDPR and ePrivacy regulations.

Is Plerdy GDPR compliant?

Plerdy typically loads analytics trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Plerdy can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Plerdy, not on Plerdy itself.

Visit website