Documentation

Cookiefy Documentation

Learn how to implement GDPR-compliant cookie banners on your website with Cookiefy.

Getting Started

Follow these simple steps to get your cookie banner up and running in minutes.

1
Scan your website

Before implementing Cookiefy, you must first scan your website to discover existing cookies and trackers.

Choose your implementation method

Cookiefy supports both vanilla JavaScript and WordPress integration.

Vanilla JavaScript Implementation

Domain ID Format

Your Cookiefy script will only work on the specified domain. You need your full domain ID which consists of your domain name followed by a dash and your 32-character personal Cookiefy ID.

example.com-a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6

This ID is found in the setup instructions for each domain in your dashboard.

Setup Instructions

  1. Log into your Cookiefy dashboard
  2. Click 'Configure' on your domain
  3. Copy the full domain ID from the setup instructions
  4. Follow the generated script instructions for your specific domain

Strictness Levels

Choose the right level of cookie blocking for your website.

Basic
Simple implementation

Basic cookie management with minimal impact on website functionality.

  • Blocks script-based cookies
  • Easy implementation
  • Low risk of compatibility issues
Recommended
Comprehensive
Balanced

Best balance between GDPR compliance and website functionality. Gets updated most regularly.

  • Blocks most cookies effectively
  • Regular updates
  • Optimized for different CMS
  • Balanced functionality
Strict
Advanced

Maximum GDPR compliance with DOM manipulation. May affect website functionality.

  • Highest level of cookie blocking
  • DOM mutation observers
  • May break website functionality
  • Requires careful testing

Understanding GDPR Compliance

Learn how Cookiefy helps you achieve GDPR compliance and its limitations.

Cookie Scanning

The Cookiefy scanner only recognizes cookies that are set uniquely through your website for new users. It cannot detect existing cookies from previous sessions.

Example: YouTube Embed

If you have a YouTube iframe, different users may have different numbers of cookies (0-100+). The scanner only detects the ~4 cookies that YouTube uniquely sets for new users.

Cookie Blocking

It's important to understand what can and cannot be blocked by client-side scripts.

Can be blocked

JavaScript-based cookies and trackers by blocking entire iframes/scripts behind consent requirements

Cannot be blocked

HttpOnly cookies set by the server. These can only be prevented by blocking the entire request to third parties

Need Help?

We're here to help you get started with Cookiefy.