Skip to main content
Privacy and user consent are critical aspects of any online campaign. InZone respects user preferences and allows you to implement full consent management through the script. By default, the script is GDPR-compliant and offers built-in support for handling user consent for analytics and location tracking. InZone provides a function to allow users to opt-out of analytics and location-based tracking, ensuring that your campaigns respect the privacy choices of your audience. This function can be called once the user either accepts or declines consent through your consent management system (CMP). By default, tracking is enabled for both analytics and location-based tracking. However, you can control this behavior either through JavaScript functions or data attributes in the script tag.

​
Usage

You can control tracking through JavaScript functions: 
// Disable tracking
window.InZone.disableTracking();

// Enable tracking
window.InZone.enableTracking();
  • disableTracking(): Once called, no analytics data (such as impressions and clicks) or location data will be collected for that user. Campaigns will still be displayed, but without tracking their interactions.
  • enableTracking(): Restores analytics and location tracking for the user.

​
Data Attributes

You can also control tracking through data attributes in the script tag: 
<script
  src="https://cdn.inzone.com/iz.js"
  data-consent-analytics="true"
  data-consent-country="true"
></script>
  • data-consent-analytics: Controls analytics tracking (default: “true”)
  • data-consent-country: Controls location-based tracking (default: “true”)

​
Best Practices

  1. Explicit consent: Always ensure that users are clearly informed about what data is being tracked (e.g., location, clicks, etc.) and provide them the ability to opt-out.
  2. Default state: In compliance with GDPR and similar regulations, tracking should be disabled by default unless the user explicitly opts in.
  3. Respect user preferences: Even if the user disables tracking, continue displaying campaigns without collecting analytics data (if they accept the ad/marketing category.).

​
Example with CookieFirst

If you have a consent banner on your site, you can integrate the consent management with InZone’s tracking functionality. Since tracking is enabled by default, we recommend disabling it immediately when the script loads and only enabling it after getting user consent: 
// Disable tracking by default
window.InZone.disableTracking();

function callbackFnc(e) {
  var consent = e.detail || CookieFirst.consent;
  // no consent yet or advertising not accepted, keep tracking disabled
  if (!consent || !consent.advertising) {
    window.InZone.disableTracking();
  } else {
    window.InZone.enableTracking();
  }
};

window.addEventListener("cf_consent", callbackFnc);
window.addEventListener("cf_init", callbackFnc);

​
CMP Example

Suppose a third-party marketing platform like “GlobRes.” provides a tracking script for targeted ads. It might supply the following to the website owner’s CMS:
  • Identity: “GlobRes, a data controller.”
  • Purpose: “Delivering personalized ads based on browsing behavior.”
  • Data Collected: “IP address, user agent, pages visited and banner interactions.”
  • Retention: “Persistent.”
  • Technical Note: “Script iz.js tracks only if ‘advertising’ consent is granted.”
The CMP then presents this to users in a cookie banner, logs their consent, and ensures the script remains inactive until consent is obtained. By providing this detailed information, the third-party marketing platform enables the website owner to meet GDPR’s requirements for transparency, lawful processing, and user control, fostering trust and compliance in data-driven marketing.