This page describes how Default works. It is not legal advice. How you classify each item,
and which laws apply to your visitors, is a decision for your own privacy or legal team.
At a glance
The Pixel sets its cookies on your own domain (for example
.yourcompany.com), so they are
first-party cookies. Items marked sessionStorage live only in that browser tab and are gone
when the tab closes. Items marked localStorage stay in the browser until they expire or are cleared.
To find the right domain, the first time a page writes a cookie the Pixel or Forms SDK briefly sets
and immediately deletes a test cookie named __dflt_cookie_scope_ followed by random characters. It
holds no visitor information and is gone before the page continues, but a cookie scanner may list it.
Which script sets what
A new copy from Settings → Domains is two pieces: the forms snippet and an optional Analytics tag. Sites that already loadindex.js keep that one file, which does both.
With analytics consent, a submission from
core.js reads the visitor ID and live session that
analytics.js stores, so it joins that visitor’s page views. core.js never writes those itself.
Without analytics consent, each submission gets a new ID that is not stored.
Strictly necessary
These make the thing the visitor asked for work. Without them, a visitor who submits a form would not see the scheduler.Form capture: no tracking cookie required
When a visitor fills in your form and selects submit, they choose to send you that information so you can respond. Default captures the submission, runs your workflow, and uses what they typed to show them the right scheduler with their details filled in. This needs no cookie. It works the same whether the visitor accepted or declined tracking.The scheduler after a form
Default only writes
__default_pending_scheduler_handoff__ when your workflow opens the scheduler
on another page, for example after your form sends the visitor to a thank-you page (Redirect to
scheduler page on the Display Scheduler step). It holds the link to the scheduler the visitor is
about to see, nothing about the visitor. When the scheduler opens on the same page as the form, that
item is not stored.
__default_configured_scheduler_link__ is written whenever the page receives a scheduler link, including
when the scheduler opens on the same page as the form. It holds only the link’s origin and path, nothing
about the visitor. See How Default books a meeting from a form submission.
Remembering the visitor’s consent choice
_dflt_consent holds the analytics and marketing choices, a format version, and the same count of
analytics withdrawals. Default writes it only after your consent banner tells Default the visitor’s
answer. The Forms SDK writes _dflt_core_rev on every page, including when the visitor declined
analytics, so it is not consent-gated. The analytics bundles do the same under their own
_dflt_rev_* keys. If an old consent cookie remains readable after a failed write, the tab
fallback also records that unchanged cookie so it cannot override the newer choice. A
new readable cookie choice supersedes that fallback. When both cookies and tab storage are blocked,
co-loaded bundles share the choice in page memory until that page unloads; no durable
entry is written.
If the browser refuses to erase an old identity cookie, co-loaded scripts remember that
value for the rest of the page and do not reuse it after consent is granted again. Fresh
cookie values remain eligible. This record stays in page memory and creates no
browser-storage entry.
Analytics
These let Default recognize the same visitor across pages and visits. They are optional.
What they power:
- Page views and sessions for your website, so you can see which pages a lead read before they submitted.
- The Account Signal in Reveal: the real-time lookup of the company behind a visit. It runs from the start of a session, so it cannot run without analytics consent. It also needs marketing consent. A visitor who allows analytics and refuses marketing is still recorded, and the company lookup does not run unless they grant marketing later in the same session, which runs it once.
_dflt_attr is written only when the visitor arrives with campaign parameters or from another
website, and only on your own origin: www.yourcompany.com and yourcompany.com do not share it.
Both the Pixel and the Forms SDK write it. Default reads it back to attach the visitor’s latest
campaign and first outside referrer to a form submission, and to fill in a scheduler link that has
none. The first campaign landing is stored alongside the latest one but is not used for that today.
When a visitor declines analytics, the Pixel writes none of these, deletes any it wrote before,
and does not run the fingerprint. Forms and the scheduler keep working.
The Forms SDK (sdk-core.js) never writes the cookies above. It does write _dflt_attr, with
analytics allowed, and it keeps these two items in the tab only (it also keeps the withdrawal count
_dflt_core_rev, listed under Remembering the visitor’s consent choice):
If the Pixel has already stored
_dflt_aid, the SDK sends that ID with the submission instead, so
the submission joins the visitor’s page views. It only reads it. When a visitor declines
analytics, the SDK keeps neither ID and sends a new random ID with each submission. It still keeps
_dflt_core_rev, the withdrawal count, which is part of honoring that choice.
When the SDK sees analytics consent withdrawn (a choice made through its own setConsent, through the
install snippet’s queue, or a denial already stored when the page loads), it deletes _dflt_attr, its
own tab IDs, and the Pixel’s _dflt_aid, _dflt_sid, and _dflt_la, so granting consent again later
starts a new visitor ID instead of resuming the withdrawn one. A withdrawal the SDK could not watch,
for example one made in another tab and reversed before the SDK next checked, leaves only a changed
withdrawal count. The SDK then drops its own tab IDs and _dflt_attr, but not the Pixel’s
_dflt_aid, _dflt_sid, and _dflt_la; the Pixel removes those itself when the withdrawal goes
through it, and it does not hand out a stored visitor ID while analytics is withheld, however the
choice was made. A damaged cookie is read as if it were absent, so it never stops a form submission.
Marketing
These identify visitors who have not filled in a form. They are optional. The People Signal in Reveal uses Default’s partner Vector to identify a visitor as a person, by name, title, and email, so your team can follow up with people who showed interest but never filled in a form. Results arrive in batches, about every 30 minutes, and can start a workflow. Vector must be on under Settings → Connections. Each website’s People Signal choice sets the pages: Off never starts Vector, Every page starts it on every eligible Pixel page, and Same pages as Reveal starts it only on pages with Reveal on. See Vector.
When a visitor declines marketing before Vector loads, the Pixel does not load it, so none of
these are set. If a visitor withdraws marketing consent after Vector has already loaded, the
Pixel stops loading Vector on later pages, but it cannot remove the script from the open page or
delete the cookies Vector already set. Send the visitor’s answer before tracking starts (see
Recommended setup) so this does not happen.
If you don’t use the People Signal, turn Vector off and the Pixel stops loading it for every
visitor. To stop it on one website only, set that website’s People Signal to Off.
The scheduler page
The scheduler itself is a Default page atbook.default.com. When it opens on your site, it
shows inside a frame, so what it stores belongs to Default’s domain, not yours. It stores these
items itself.
The scheduler page honors the same analytics choice as the Pixel for its visitor IDs. It reads the _dflt_consent
cookie your banner’s answer is remembered in. When analytics is withheld, it does not run the
fingerprint, does not write _dflt_aid, _dflt_sid or _dflt_la, and removes any it finds. The
booking then carries IDs that exist only for that visit and are gone when the page unloads. With no
stored choice, analytics counts as allowed, as it does for the Pixel. The scheduler can only act on
a choice it can read: when it opens inside your site from another domain, the browser does not
show it your _dflt_consent cookie, so it applies that default. The reservation item and the
ph_ product analytics items in the table below do not follow the visitor’s choice.
The ph_ items have a workspace switch instead. An admin can turn off Booking page analytics
in Settings → Privacy. Then the booking, reschedule, cancel and confirmation pages of your
workspace do not load product analytics for any visitor, so no ph_ item is set. The change
reaches your booking pages within two minutes. Turning it off also removes session recording links
from your workflow logs.
When the scheduler opens inside your site, most browsers block its analytics cookies, because
they belong to another domain. The scheduler then keeps the same IDs in the browser’s storage
for that frame instead. A visitor who opens a booking link directly, for example from an email,
gets the cookies as listed.
Recommended setup
1
Install the Pixel outside your consent gate
Load the Pixel on every page, for every visitor. Don’t wait for consent before loading it.
Your banner controls what the Pixel tracks; it should not control whether the Pixel loads. If
the Pixel only loads after consent, a visitor who declines, or ignores the banner, submits your
form and never sees the scheduler.
2
Send a no before tracking starts, where you need opt-in
Out of the box, the Pixel allows analytics and marketing until it hears otherwise. If your
visitors must opt in first (for example under GDPR), tell the Pixel “no” on the visitor’s first
page, right after the install snippet and before they have made a choice. A call made before the
Pixel finishes loading is applied before it starts any tracking:The check means you only send it while no usable choice is stored. A damaged or outdated
_dflt_consent cookie, including one whose analytics or marketing value is not true or false,
counts as no choice, the same way the Pixel treats it, and the Pixel then allows analytics and marketing
until it hears otherwise. Don’t send “no” on every page load
while your banner is still loading; that clears the visitor’s ID on every page. Your forms and
the scheduler keep working while the answer is “no”.3
Tell Default what the visitor chose
When the visitor answers your banner, pass the answer on:Default remembers it in
_dflt_consent for later pages and visits. See
Wiring up your consent banner.4
Treat a browser privacy signal as a no
Some browsers, such as Brave, send Global Privacy Control (a “do not sell or share my data”
signal) by default. If your site honors it, keep loading the Pixel and send a no for both
categories:The visitor’s form submission and the scheduler keep working. On your pages, the Pixel stores
no visitor ID, does not run the fingerprint, and does not load Vector. The scheduler page follows
the same choice where it can read it (see The scheduler page). Don’t skip the
Pixel for these visitors: that also stops the scheduler. Send this before tracking starts, the
same way as the opt-in “no” above.
5
Classify the items in your cookie tool
Add the items on this page to your consent tool under the categories in
At a glance. Most tools, such as Cookiebot and OneTrust, let you add an item
by name and pick its category.
6
Mention Default in your privacy policy
Name Default as the service that captures your form submissions and runs your scheduler. If you
use the People Signal, also say that a partner identifies visitors on your site.