WhoKnew Views™ | Cookie Consent Management

Skip to main content
Table of Contents
Print

Integrate WhoKnew Views™ with cookie consent banners, categorize cookies correctly, and offer visitor opt-out options

If you’re using a cookie consent plugin to comply with GDPR, CCPA, or other privacy laws, you’ll want to know how WhoKnew Views™ cookies fit into your consent categories. Good news: our cookies don’t require explicit consent because they don’t collect personal data—but proper categorization still matters for transparency.


🍪 WhoKnew Views™ Cookie Inventory

The plugin uses three types of cookies, each with a specific purpose:

Cookie NamePurposeDurationCategory
wkv_viewed_{product_id}Prevents duplicate view counting30 min – 2 hrsEssential
wkv_window_{product_id}Smart Visibility window trackingConfigurableFunctional
whoknow_lifetime_view_*First-time vs returning visitor90 daysAnalytics
wkv_window_active_*Once in Window mode trackingConfigurableFunctional

✅ Key Point: All WhoKnew Views™ cookies contain only timestamps and hashed identifiers—no names, emails, IP addresses, or personal data. This is why they qualify as essential/functional rather than marketing/advertising cookies.


📂 Cookie Consent Categories Explained

Most consent plugins organize cookies into categories. Here’s how WhoKnew Views™ cookies should be classified:

🟢 Essential / Strictly Necessary

Cookies required for basic site functionality. No consent needed.

  • wkv_viewed_* – Prevents duplicate counting
  • Critical for accurate analytics display

🔵 Functional / Preferences

Enhance user experience. No consent typically needed.

  • wkv_window_* – Smart Visibility timing
  • Remembers display preferences

🟠 Analytics / Statistics

Aggregate site usage data. Consent recommended.

  • whoknow_lifetime_view_* – Returning visitor detection
  • Fully anonymous, no PII

🔌 Popular Consent Plugin Integrations

WhoKnew Views™ works with all major cookie consent plugins. Here’s how to configure each:

🍪 Cookie Notice by TownPress

Configuration Steps:

  1. Go to Cookies → Settings
  2. In Cookie Script Blocking, leave WhoKnew Views scripts unblocked
  3. Add cookie names to the Cookie List for transparency
  4. Use the cookie banner template from Privacy Helper

🔒 Complianz GDPR/CCPA

Configuration Steps:

  1. Go to Complianz → Cookie Policy
  2. Add WhoKnew Views™ to your cookie list
  3. Set category to Statistics (anonymous)
  4. Mark as “No consent required” (legitimate interest)

Complianz may auto-detect WhoKnew Views™ cookies during scanning.

🤖 CookieBot

Configuration Steps:

  1. Go to Cookiebot Dashboard → Cookie List
  2. Categorize wkv_viewed_* as Necessary
  3. Categorize whoknow_lifetime_view_* as Statistics
  4. Leave as “First-party” (no third-party data sharing)

🛡️ GDPR Cookie Consent (WebToffee)

Configuration Steps:

  1. Go to GDPR Cookie Consent → Cookies
  2. Add WhoKnew Views™ cookies manually
  3. Assign to Necessary or Analytics category
  4. Copy descriptions from Privacy Helper templates

📋 Ready-to-Use Banner Text

WhoKnew Views™ Pro includes pre-written cookie consent text in the Privacy Helper tab. Here’s a quick reference:

📜 Sample Cookie Banner Text:

“We use cookies to enhance your browsing experience and analyze product popularity. These cookies help us show accurate view counts and improve our service.

Essential Cookies: Track product views and prevent duplicate counting
Analytics Cookies: Help us understand visitor patterns (anonymous, up to 90 days)

By continuing to browse, you consent to our use of cookies.”

ℹ️ Pro Tip: Find complete HTML snippets with one-click copy in WhoKnew Views → Settings → Privacy Helper tab. These include cookie banner, privacy policy section, and GDPR short notice templates.


❓ Consent Not Required—Here’s Why

Under GDPR Article 6(1)(f), WhoKnew Views™ operates on legitimate interest because:

  • ❌ No personal data collected – Just timestamps and hashed identifiers
  • ❌ No cross-site tracking – Cookies are first-party only
  • ❌ No third-party sharing – All data stays in your WordPress database
  • ❌ No advertising/marketing – Used only for analytics display
  • ✅ Minimal privacy impact – Visitors can’t be identified or re-identified

⚠️ Transparency Still Matters: Even though consent isn’t technically required, best practice is to list all cookies in your cookie policy and offer opt-out instructions. This builds customer trust and satisfies stricter regional requirements.


🔧 Visitor Opt-Out Options

Visitors who prefer not to be tracked have several options:

Option 1: Browser Cookie Settings

Visitors can block or delete cookies in their browser settings. All major browsers (Chrome, Firefox, Safari, Edge) support this.

Note: This may affect other site functionality beyond WhoKnew Views™.

Option 2: Private/Incognito Browsing

Cookies set in incognito/private mode are automatically deleted when the session ends.

WhoKnew Views™ uses server-side fingerprinting as a fallback for returning visitor detection in incognito mode.

Option 3: Cookie Consent Plugin Rejection

If your consent plugin blocks “analytics” cookies when rejected, the whoknow_lifetime_view_* cookie won’t be set.

Essential cookies (wkv_viewed_*) should remain enabled for accurate counting.


🔒 Cookie Security Features

WhoKnew Views™ cookies are set with modern security flags:

HttpOnly✓ Enabled – Not accessible via JavaScript (XSS protection)
Secure✓ Auto-enabled on HTTPS sites
SameSite✓ Strict – Cookies not sent with cross-site requests

✅ Security Summary: WhoKnew Views™ cookies follow OWASP best practices for cookie security. They cannot be stolen via JavaScript injection, intercepted on unencrypted connections (on HTTPS sites), or abused for cross-site request forgery.


📊 Quick Reference: Cookie Policy Entry

Copy this table directly into your cookie policy page:

<table>
  <tr>
    <th>Cookie</th>
    <th>Purpose</th>
    <th>Duration</th>
    <th>Type</th>
  </tr>
  <tr>
    <td>wkv_viewed_*</td>
    <td>Prevents counting duplicate product views</td>
    <td>30-120 minutes</td>
    <td>Essential</td>
  </tr>
  <tr>
    <td>wkv_window_*</td>
    <td>Manages view counter display preferences</td>
    <td>Configurable</td>
    <td>Functional</td>
  </tr>
  <tr>
    <td>whoknow_lifetime_view_*</td>
    <td>Identifies returning visitors (anonymous)</td>
    <td>90 days</td>
    <td>Analytics</td>
  </tr>
</table>

🎯 Best Practices Summary

  1. List all cookies in your cookie policy for transparency
  2. Categorize correctly: Essential for wkv_viewed_*, Analytics for whoknow_lifetime_*
  3. Don’t block essential cookies in consent plugins—they’re needed for accurate counts
  4. Use Privacy Helper templates for professionally-written cookie notice text
  5. Offer opt-out instructions even though consent isn’t legally required
  6. Keep cookie durations accurate in your policy (check your actual settings)

With proper categorization and transparent disclosure, WhoKnew Views™ integrates seamlessly with any cookie consent solution—keeping your store compliant while maintaining accurate analytics.

Share