Does Duda require consent on websites it powers?

Conditionally. Duda's core rendering scripts are essential and cannot be blocked without breaking the site. However, its built-in analytics and dynamic content personalization features use tracking cookies that require consent in most jurisdictions.

What tracking does Duda's platform perform?

Duda includes built-in visitor analytics tracking page views, traffic sources, and engagement. Its personalization engine uses cookies to identify returning visitors and customize content, which constitutes tracking under the ePrivacy Directive.

How does ConsentStack handle Duda-built sites?

ConsentStack permits Duda's essential rendering scripts to load without consent. Analytics and personalization layers are blocked until the visitor grants consent, ensuring compliance without breaking the underlying site functionality.

What tracker domains does Duda use?

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

Duda - Website Builder & Tracking Consent

Back to Vendor Library

Overview

Duda is a white-label website builder platform primarily used by agencies, SaaS companies, and hosting providers to create and manage client websites at scale. Unlike consumer-oriented builders, Duda is designed for professional web design workflows with features like team collaboration, client management, and dynamic content personalization. Websites built on Duda run on Duda's infrastructure, meaning the platform's core scripts are fundamental to page rendering and site functionality.

What makes Duda distinctive from a consent management perspective is its role as a website platform rather than a third-party script. Duda's core JavaScript is the rendering engine for the entire site — it's not an optional add-on that can be blocked without breaking the page. However, Duda also provides built-in integrations for analytics, marketing pixels, and third-party widgets that site owners can enable during setup, and these additional scripts do warrant separate consent consideration.

What This Script Does

Duda's scripts serve multiple layers of functionality on websites built with its platform:

Core Page Rendering: The fundamental Duda runtime handles page layout, responsive design adaptation, navigation, animations, and interactive element behavior. This is the base layer without which the website cannot function.
Dynamic Content Personalization: Duda offers built-in content personalization that can display different content based on visitor attributes like geographic location, device type, time of day, or visit count. This feature uses cookies and session data to identify returning visitors and tailor page content.
Integrated Analytics: Duda includes built-in website statistics tracking that monitors page views, visitor counts, traffic sources, and engagement metrics. This operates alongside any third-party analytics tools the site owner configures.
Third-Party Widget Loading: Site owners can add integrations through Duda's app marketplace or custom code injection. Duda's scripts manage the loading and initialization of these additional third-party resources, which may include marketing pixels, chat widgets, social media embeds, and advertising tags.
Form and Lead Capture: Built-in contact forms, pop-ups, and lead generation widgets collect visitor information and send it to the site owner's dashboard or connected CRM platforms.

Consent & Compliance

Duda's compliance profile is layered because its scripts span from essential page rendering to optional analytics and marketing features. The core rendering engine is strictly necessary — without it, the website does not display. However, the personalization, analytics, and third-party integration layers introduce tracking that requires careful consent management.

The dynamic content personalization feature is particularly notable. When it uses cookies to identify returning visitors and customize content, this constitutes tracking under the ePrivacy Directive and would generally require consent in EU jurisdictions unless the personalization is strictly necessary for a service explicitly requested by the user.

Duda's built-in analytics tracking collects behavioral data about visitor interactions, which falls squarely under analytics processing requiring consent under GDPR. Site owners using Duda should treat the platform's native analytics the same way they would treat Google Analytics or similar tools.

For third-party integrations loaded through Duda, the responsibility for consent falls on the website operator. Duda provides the mechanism to load these scripts, but the operator must ensure appropriate consent is obtained before they execute.

Should You Block This Without Consent?

Duda's core rendering scripts are essential to website functionality and cannot be blocked without breaking the site entirely. However, its personalization, built-in analytics, and third-party integration features introduce tracking that goes beyond essential functionality. The core platform scripts should not be blocked, but analytics and personalization features should be governed by consent.

Conditional.

Is Duda GDPR compliant?

Duda typically loads functional 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 Duda 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 Duda, not on Duda itself.

Visit website