Clym Installation -> Advanced settings

Advanced Settings provide greater control over how your Clym widget configurations behave, offering flexibility for performance optimization, data privacy compliance, and integrations with industry frameworks. To enable these features, your site must be running the Standard Script (v2), as they are incompatible with Legacy or SRI versions. If you are not yet using Standard Script (v2), we recommend following the steps outlined in our Migrating to Standard Script (v2) guide before proceeding. Once enabled, Advanced Settings open up options to fine-tune how the widget loads, how scripts execute, and how consent signals are communicated to third-party services.

Using Advanced Settings is especially useful if you need more precise control over privacy frameworks, consent mode integrations, or performance configurations. For example, Native Mode reduces widget size and improves speed by loading outside of an iframe, while Blocking Modes let you choose how strictly scripts are managed based on user consent. Advanced Settings also support temporary IAB stub signals and customizable behavior for Google and Microsoft Consent Modes, ensuring vendors receive the right information at the right time. Whether your goal is improving site performance, aligning with privacy regulations, or fine-tuning vendor integrations, these options allow you to adapt the widget to your organization’s needs.

Advanced Settings Requirements

To enable advanced settings on your website, the Standard Script (v2) must be implemented. These features are not compatible with the Legacy or SRI versions. For guidance on upgrading, please refer to our article: Migrating to Standard Script (v2).

Widget Settings

• Native Mode

In Native Mode, the widget loads without using an iframe. This option is supported only if the initial notification type is set to Top, Bottom, Discrete, or Center. Please ensure that the initial notification type is not set to Full Widget, HIPAA, or IaB TCF. Running in Native Mode improves performance and reduces the widget’s overall size.

• Script Execution

The two main scripts must be loaded synchronously (they are lightweight). Once loaded, the widget itself can run in async, defer, or synchronous mode, depending on your configuration.

Blocking Modes

Blocking Mode determines how strictly scripts are controlled based on user consent:

• Implicit – Automatically blocks all scripts matching service identifiers when sufficient consent is not given.
• Explicit – Only blocks scripts that are manually flagged in your site’s code and lack consent.
• Disabled – No scripts are blocked.

Privacy Framework Support

• IAB GPP Stub Support

When enabled, this sends a temporary IAB Global Privacy Platform (GPP) signal to vendors until the widget has fully loaded.

• IAB TCF Stub Support

When enabled, this sends a temporary IAB Transparency and Consent Framework (TCF) signal to vendors until the widget has fully loaded.

Consent Mode Integrations

• Google Consent Mode – Default Signals

Enable or disable support for Google Consent Mode.

• Google Consent Mode – Wait for Update

Define how long (in milliseconds) Google waits for the default consent signal before applying settings.

• Microsoft Consent Mode – Default Signals

Enable or disable support for Microsoft Consent Mode.

• Microsoft Consent Mode – Wait for Update

Define how long (in milliseconds) Microsoft waits for the default consent signal before applying settings.

Updated on: 16/09/2025