Consent Management
Tell Logspot what each event is allowed to be used for, from your CMP or a single API call.
Logspot is consent-native: every event is stamped, at the moment it happens, with the permissions that applied to it. That stamp travels with the event for its whole life, so downstream reports, audiences, exports, and automated Actions all know what a given event is allowed to be used for.
Logspot is not a consent management platform (CMP). It consumes consent — from your existing CMP, from browser privacy signals, or from a single API call — and enforces it. If you already run a CMP, Logspot trusts its decisions; you don't configure consent rules in two places.
Quick Start
If you manage consent yourself, tell Logspot the current state with setConsent:
Logspot.setConsent({
analytics: true,
functional: true,
marketing: false,
doNotSellShare: true,
});All fields are optional — send only the categories you've decided. Call it again whenever the user's choice changes; Logspot records the change and stamps subsequent events accordingly.
Connect Your CMP Instead
If you use a CMP, point Logspot at it and skip the manual calls. Logspot reads the CMP's decisions directly:
Logspot.init({
publicKey: 'YOUR_PUBLIC_KEY',
consentSources: ['concord'],
});Supported sources: concord (the preferred integration), onetrust, usercentrics, cookiebot, and gcm (a read-only Google Consent Mode reader for sites already running Consent Mode). List more than one if you need to.
With the CDN snippet, use the data-consent-source attribute (comma-separated):
<script
src="https://cdn.logspot.io/v2.js"
data-logspot-pk="YOUR_PUBLIC_KEY"
data-consent-source="onetrust"
></script>When several sources are present, the most authoritative one wins, in this order: an explicit setConsent call, then Concord, then a third-party CMP (OneTrust / Usercentrics / Cookiebot), then the Google Consent Mode reader, then your organization's defaults. Logspot never re-interprets a CMP's decision — the CMP is the source of truth.
Categories
Logspot uses three consent categories:
- Analytics — measuring product and site usage.
- Functional — features that remember the user (preferences, session continuity).
- Marketing (Advertising) — audience building, retargeting, ad measurement, and ad personalization.
These map to the standard categories your CMP already exposes, so no translation is needed.
Default Behavior
If you never send consent, an organization-level setting decides the default. Set it under Settings → Privacy → User Consent:
- Not required (default) — analytics, functional, and marketing are all allowed. Best for standalone analytics where you don't gate on consent.
- Implied — all categories are allowed until the user declines.
- Express — all categories are denied until the user grants them.
- Custom — choose the default per category.
The same screen controls what happens to an event when analytics is not allowed: drop it at ingestion (the default) or anonymize it (store it with all identifiers removed so aggregate counts still work).
Browser Privacy Signals
Logspot automatically detects Global Privacy Control (GPC) and Global Privacy Platform (GPP) signals and records them alongside the event, separate from the consent categories. When no CMP is connected, a GPC signal sets Do Not Sell/Share and turns marketing off. When a CMP is connected, the signal is recorded but the CMP's decision still stands.
What the Stamp Unlocks
Because every event carries its permissions, you can:
- Segment by consent — built-in filters for Analytics Allowed, Functional Allowed, Marketing (Advertising) Allowed, Do Not Sell Enabled, GPC Detected, and Advertising Eligible.
- Gate Actions and exports — an Action that needs marketing consent won't run for events that don't carry it. See Actions.
- Audit with confidence — each identity keeps a full consent history (who, what, when, and which source decided), for compliance reviews and investigations.