The Customization tab of the TermsFeed AutoTerms Cookie Consent kit holds 10 fields that turn the kit on and set the consent type, look, and language of the cookie banner. Open it from TermsFeed > Compliance Kits in your WordPress admin with the "Configure" button in the Cookie Consent box. The plugin passes most of the fields to TermsFeed Free Cookie Consent 4.2.0 as keys of the Configuration Parameters.

The right column of the tab shows a Preview of the consent banner, and the "Save Changes" button at the bottom stores every field in one save. Read what the Cookie Consent script does with each key in the Free Cookie Consent API Reference.

The 10 fields of the Customization tab

Look up each field for the values it takes, its default on a new installation, and the Configuration Parameters key it writes in the JSON.

Field Values Default Configuration Parameters key Effect
"Enabled" Checkbox Off None Prints the Cookie Consent script and the vendor scripts on every page of your WordPress website except wp-login.php and wp-register.php, and the Cookie Consent script then shows the consent banner. The "Enable" and "Disable" buttons on the Compliance Kits screen set the same checkbox.
"Compliance preference" "ePrivacy Directive (i.e. OK button)" (implied) or "GDPR Directive (i.e. I Agree & I Decline buttons)" (express) "GDPR Directive (i.e. I Agree & I Decline buttons)" consent_type, and page_load_consent_levels with it Express by default runs only strictly-necessary vendor scripts before the visitor accepts, and implied runs all 4 categories by default on every page load until the visitor turns a category off. The help text reads "Currently, Cookie Consent does not include geolocation functionality." Choose a consent type with Express and Implied Consent in Free Cookie Consent.
"Website name" Text The WordPress Site Title from Settings > General website_name Writes the name that the Preferences Center prints as plain text above its title.
"Notice banner style" "Simple", "Headline", "Interstitial", or "Standalone" "Headline" notice_banner_type Writes the layout as a lower-case value, such as headline. Compare the layouts in Cookie Banner Layouts in Free Cookie Consent.
"Color palette" "Light" or "Dark" "Light" palette Writes light or dark. Restyle either palette with Cookie Banner Colors and Custom CSS in Free Cookie Consent.
"Default language" A select of 36 languages, each shown by its name "English" (en) language Writes the lower-case language code, such as de or en_gb, and the consent banner and the Preferences Center open in that language on every page. The language menu of the Preferences Center switches it for the current page only. Find each language code in Cookie Banner Languages in Free Cookie Consent.
"Insert link for users to open Preferences Center" Checkbox On None Prints <a href="#" id="open_preferences_center">Update cookies preferences</a> at the end of every page. Off, it prints nothing, and the help text asks for your own element with the id open_preferences_center. Place your own link with Add a Cookie Settings Link With Free Cookie Consent.
"Callbacks" A JavaScript object literal The default Callbacks, which grant Google Consent Mode v2 signals once targeting loads callbacks Prints your code in a script of its own. Copy the default and write your own with Cookie Consent Callbacks in WordPress.
"Additional CSS" CSS, in a code editor with CSS hints Empty None Prints your rules in <style id="termsfeed-autoterms-cookie-consent-style"> on every page with the kit on. The help text reads "Use Developer Tools > Inspect Element to find all available CSS classes." Find the classes in the Free Cookie Consent DOM and CSS Reference.
"Cookie Consent version" 4.2.0 4.2.0 None Loads https://www.termsfeed.com/public/cookie-consent/4.2.0/cookie-consent.js, the only version the kit offers.

The full Customization tab of the Cookie Consent kit with every field on the left and the Preview of the consent banner on the right

When a Customization change reaches your WordPress website

A saved Customization field applies from the next page load once the page cache is cleared, and a field written to the JSON needs valid Configuration Parameters. "Enabled", "Insert link for users to open Preferences Center", "Additional CSS", and "Cookie Consent version" are read from their own settings. The other fields reach your WordPress website through the Configuration Parameters, which the tab rewrites when it reloads after the save. A save on either tab updates the other tab. Clear each page cache with WordPress Caching Plugins.

A change to "Compliance preference" resets page_load_consent_levels, and every key you added to the Configuration Parameters yourself stays as you wrote it. Read every rule that keeps the 2 tabs in sync in Cookie Banner JSON Settings in WordPress.

The Customization tab shows this notice while the Configuration Parameters hold invalid JSON, and the fields written to the JSON then change nothing on your WordPress website.

The Configuration Parameters are not valid JSON, so changes made here are not applied. Please correct them on the Configuration Parameters tab.

Some keys of the Configuration Parameters have no field. notice_banner_reject_button_hide, preferences_center_close_button_hide, and page_refresh_confirmation_buttons change only on the Configuration Parameters tab. The plugin writes them as false into the Configuration Parameters of a new installation. Set any of the 3 to true with Cookie Banner JSON Settings in WordPress, and read what each option does in the Free Cookie Consent API Reference.

How the Preview on the Customization tab works

The Preview runs the Cookie Consent script with the saved Configuration Parameters in demo mode, with the unsaved values of the fields written to the JSON applied over them. It redraws the consent banner each time you change "Compliance preference", "Website name", "Notice banner style", "Color palette", "Default language", or "Callbacks". "Additional CSS" shows in the Preview only after you save it.

Demo mode shows the consent banner on every load of the Preview and does not keep an answer. The Preview page reads "This is a preview page." and holds an "Open Preferences Center" button. The Preview runs the default Cookie Consent options while the Configuration Parameters hold invalid JSON, although your WordPress website then does not show the consent banner. Read what the demo option does in the Free Cookie Consent API Reference.

The Preview opens only for users allowed to save the kit settings. Callbacks run in the Preview as they do on your WordPress website. The Preview loads none of your other scripts, so a callback that calls gtag() without the typeof gtag === 'function' check that the default Callbacks carry stops with an error there.

Customization fields that need the unfiltered_html capability

On a save by a user without the WordPress unfiltered_html capability, the plugin keeps the stored "Callbacks" and "Additional CSS" and removes any HTML typed into "Website name". The plugin names the missing capability in an error at the top of the tab. Find each error, and which users lack the capability, in TermsFeed AutoTerms Capabilities and Roles.