invokationYour analytics choice
Understand necessary website storage, optional Google Analytics, consent withdrawal, and campaign attribution on the Invokation website.
The waitlist works without optional analytics
The site stores your analytics choice in localStorage under inv_consent_v1. This preference is necessary to honor your choice across visits. It contains only accepted or rejected, not a browsing history.
A short-lived __session HttpOnly cookie authorizes optional qualification after a signup. It lasts 30 minutes, is scoped to the API, and is Secure in production with SameSite Strict. It contains no raw email. Necessary tab session storage holds a random, scoped submission key and completion flags for that flow. It permits safe network retries and avoids repeated accepted-submission events. It contains no email and is never sent to analytics; it expires with the tab. Starting a later signup creates a new flow.
What accepting analytics enables
If a valid GA4 measurement ID is configured, accepting analytics loads the direct Google tag. It sends manually controlled pageviews and the explicit interaction events described in this site's measurement documentation. No Google Analytics script request, analytics cookie, event, or pre-consent analytics queue is created before acceptance.
Google Analytics may set first-party cookies such as _ga and stream-specific _ga_* cookies. Their expiry and processing depend on the owner's GA4 configuration. Advertising storage and personalization are denied by the site's tag configuration. Automatic history pageviews and automatic form measurements must be disabled in the owner's GA4 stream.
Campaign information
Only after acceptance, optional session storage records a known landing route and bounded campaign values from utm_source, utm_medium, utm_campaign, and optional term/content. The first touch remains fixed for that tab session; the last touch changes when a new valid campaign arrives. This can be included with a consented signup. Refusing analytics prevents this attribution storage.
Tracked locations use known public routes and approved campaign values. Arbitrary queries and hashes are omitted. External referrers are reduced to their origin. Never put a person's email, confidential customer data, or tokens in any URL.
Change or withdraw your choice
Rejecting optional analytics stops future site tracking, clears accessible first-party GA cookies on applicable domain scopes, and removes optional attribution. If the tag was already loaded, the page reloads to remove its active runtime. Changes in another tab also trigger a reload.
Cookie deletion cannot reverse completed network requests or delete data already processed by Google. Browsers can restrict storage access, and cookies with inaccessible paths or domains may need browser controls. If preference storage is unavailable, the site asks again on a later page load instead of assuming consent.
Keep your form data separate
Waitlist submissions go to the same-origin API independently of the analytics choice. Email addresses and free-text research answers are not analytics parameters. No automatic email is sent. See the privacy policy for retention and the operator contact.