Custom Fields¶

Waulter provides 10 custom fields (customField1 through customField10) that you can use to pass contextual data to the SDK. Custom fields enable advanced scenario targeting and are included in all data layer events.

Setting custom fields at initialisation¶

Custom fields are set in the WaulterConfig object before the SDK loads. Values can come from any JavaScript source:

window.WaulterConfig = window.WaulterConfig || {};
Object.assign(window.WaulterConfig, {
  id: "YOUR_CONFIG_ID",
  useGtm: true,

  // From localStorage (with fallback)
  customField1: localStorage.getItem("userTier") || "free",
  customField2: localStorage.getItem("language") || "en",

  // From page context
  customField3: document.querySelector('meta[name="page-type"]')?.content || "default",

  // From JavaScript variables
  customField4: typeof userId !== 'undefined' ? "logged-in" : "anonymous",

  // Static values
  customField5: "campaign-summer"
});

Via GTM template¶

When using the Community Template, custom fields are configured directly in the template's field UI. You can use GTM variables:

Via data-* attributes¶

Custom fields can also be set via data-* attributes on the script tag:

<script
  src="https://cdn.waulter.cz/sdk.js"
  data-id="YOUR_CONFIG_ID"
  data-use-gtm="true"
  data-custom-field-1="premium"
  data-custom-field-2="homepage"
></script>

Runtime updates via setCustomFields()¶

Custom fields can be updated after initialisation using the SDK method:

window.WaulterSDK.setCustomFields({
  customField1: 'enterprise',
  customField4: 'logged-in'
});

Behaviour:

• Only the specified fields are updated; others remain unchanged.
• Fires a Waulter:CustomFieldsUpdated data layer event and DOM CustomEvent.
• Updated values are included in all subsequent Waulter:* events.
• The new values take effect for scenario evaluation on the next page load (scenarios are evaluated server-side during SDK initialisation).

Example — update after login:

document.getElementById('loginForm').addEventListener('submit', function() {
  // After successful login, update custom fields
  window.WaulterSDK.setCustomFields({
    customField1: 'premium',
    customField4: 'logged-in'
  });
});

Use in scenario targeting¶

Custom fields are available as targeting variables in scenario rules. This enables dynamic consent experiences based on visitor context.

Common patterns:

All scenario operators work with custom fields: equals, not-equals, contains, startsWith, endsWith, regex, >, <, mod, in.

Inclusion in data layer events¶

Custom field values are included in all Waulter:* data layer events:

// Waulter:Decision event includes custom fields
{
  event: "Waulter:Decision",
  decision: "allow",
  purposes: ["PU046", "PU050", "PU061"],
  customField1: "premium",
  customField2: "en",
  customField3: "homepage",
  customField4: "logged-in",
  customField5: "campaign-summer"
}

This allows you to:

• Segment consent analytics in GTM — create variables and triggers that read custom field values
• Build custom reports — correlate consent decisions with user tier, page type, or campaign
• Debug targeting — verify which custom field values are being sent

Common use cases¶