Learn why Gartner just named Builder a Cool Vendor

Announcing Visual Copilot - Figma to production in half the time

Builder.io logo
Contact Sales
Platform
Developers
Contact Sales

Blog

Home

Resources

Blog

Forum

Github

Login

Signup

×

Visual CMS

Drag-and-drop visual editor and headless CMS for any tech stack

Theme Studio for Shopify

Build and optimize your Shopify-hosted storefront, no coding required

Resources

Blog

Get StartedLogin

Builder complies with General Data Protection Regulation (GDPR) and with current US data protection laws, such as California Consumer Privacy Act (CCPA), Virginia Consumer Data Protection Act (VCDPA), and others.

When using the Builder SDK or HTML on your website, Builder sets cookies and localStorage items in order to provide content analytics and A/B testing functionality.

Cookie or local storage namePurpose

builderSessionId

Content analytics (such as impressions and clicks)

builderVisitorId

Content analytics (such as impressions and clicks)

builderio.variations.<some-id>

AB testing functionality

builder.tests.<some-id>

AB testing functionality

When builder tracking is enabled (it is on by default), Builder automatically tracks impressions and clicks for content entries. Customers can call the Builder track() function from their code to track conversions and other arbitrary events. When track() is called, we send information to Builder's backend that includes:

  • content ID of the Builder content entry
  • A/B test variation ID (if any)
  • type of event (such as a click or impression)
  • date and time
  • Space ID (Public API Key)
  • URL path
  • device type
  • click location for heatmaps
  • session ID
  • visitor ID
  • any metadata that the user provides to the Builder.track() call, which can be anything depending on what customers want to send; however, for automatic events it consists of the Builder SDK version and full URL (path and query string).

If you give your customers a UI to opt-in to cookies and tracking, you can listen for their response and change tracking preferences. This toggles Builder cookies and tracking on or off accordingly.

With the HTML API, set a window variable to window.builderNoTrack = true. In this way, Builder does not make any tracking requests to our backend, meaning we do not record visitor ids or any information about the site visitor.

If you are using a Builder Gen 1 SDK, you can set builder.canTrack = false to disable any tracking and setting of cookies or local storage items.

You can use either window.builderNoTrack or builder.canTrack to toggle tracking, cookies, and local storage.

For Gen 2 SDKs, use canTrack={false} in the Content component, for example, <Content canTrack={false} />. For more information on canTrack, visit its entry in Using the Content Component.

For details on the differences between the SDKs, visit SDK Comparison.

For more information, see the following:

Was this article helpful?

Product

Visual CMS

Theme Studio for Shopify

Sign up

Login

Featured Integrations

React

Angular

Next.js

Gatsby

Get In Touch

Chat With Us

Twitter

Linkedin

Careers

© 2020 Builder.io, Inc.

Security

Privacy Policy

Terms of Service

Newsletter

Get the latest from Builder.io

By submitting, you agree to our Privacy Policy

Product

Platform Overview

Integrations

What's New

Open Source

Builder

Builder

Mitosis

Mitosis

Mitosis

AI Shell

Mitosis

Micro Agent

Mitosis

GPT Crawler

Qwik

Qwik

Partytown

Partytown

Popular Guides

From Design to Code Guide

Composable Commerce Guide

Headless CMS Guide

Headless Commerce Guide

Composable DXP Guide

Design to Code

Resources

Blog

Knowledge Base

Community Forum

Partners

Templates

Success Stories

Showcase

Resource Center

Frameworks

React

React

Next

Next.js

Qwik

Qwik

Gatsby

Gatsby

Angular

Angular

Vue

Vue

Svelte

Svelte

Remix logo

Remix

Nuxt

Nuxt

Hydrogen

Hydrogen

See All

© 2024 Builder.io, Inc.

Security

Privacy Policy

SaaS Terms

Security & Compliance

Cookie Preferences

Gartner Cool Vendor 2024