Skip to main content
Important: Please ensure your CMP configuration includes new Vendor ID 1469 for 1st Party data tracking. Additionally, include Vendor ID 301 if cookie sync is enabled. Learn more
Type: Boolean Default: true Description: This option controls whether the Zeotap Web SDK is permitted to perform cookie syncing operations. Cookie syncing is a background process used to match the Zeotap user identifier (ZI) with identifiers from approved third-party advertising platforms or data partners. This matching typically happens via pixel fires or redirects initiated by the SDK.
  • true (Default): When set to true, the SDK will automatically initiate cookie syncing processes with all partners. To restrict reach out to Zeotap representative or Support team.
  • false: When set to false, the SDK will not perform any automatic cookie syncing operations, regardless of consent status.
Cookie sync is controlled based on these flags and does not automatically read the consent status from your CMP. Therefore, if consent has not been provided for any of these partners, ensure the corresponding SDK flag is set to false. Currently we support this for custom consent implementation — refer to the Consent Based cookie syncing configuration to know more.
Usage: You configure allowCookieSync within the options object passed to the window.zeotap.init method. Example: Disabling Cookie Sync If you want to prevent the SDK from initiating any cookie syncs:
SDK Initialization - Disabling Cookie Sync
window.zeotap.init("YOUR_WRITE_KEY", {
  allowCookieSync: false // Explicitly disable cookie syncing
  // ... other configurations
});
Last modified on June 25, 2026