Skip to main content

Terminology

This page defines the key terms you will encounter across the Click documentation. If you are new to Click, read Core Concepts first to understand how these pieces fit together.

Core Objects​

Template: The agreement you create in Click — its content, appearance, and behavior. A template is your source document. You create it once and can deploy it to as many locations as needed. See Templates.

Version: A saved snapshot of a template at a point in time. Every time you publish a change, a new version is created. Previous versions are preserved, so you always have a record of exactly what users were shown. See Template Versioning.

Deployment: The connection between a published template and a specific location in your product (a domain and URL path). A deployment controls when and how the agreement appears. See Deployments.

Session: The record Click creates each time a user encounters a deployed agreement. Sessions are created automatically — you do not manage them directly. See Core Concepts.

Evidence Bundle: The compliance record generated automatically when a user accepts an agreement. This is the record you would produce in an audit or legal review. See Evidence & Compliance.

Template Types​

Static Clickwrap: A fixed agreement shown identically to every user. Used for Terms of Service, Privacy Policies, and other standard agreements that do not vary by user.

Generated Clickwrap: An agreement personalized for each user using variables (for example, {{userName}} or {{startDate}}). Each user sees the agreement rendered with their own data. Used for NDAs, onboarding contracts, and personalized agreements.

Consent Management: A category-based opt-in/opt-out experience for GDPR, CCPA, and similar requirements. Users make individual choices per category (such as analytics or marketing) rather than accepting a single document. See Consent Management.

Template Lifecycle States​

Draft: The template is being edited and is not yet available for deployment.

Published: The template content is locked and ready to deploy. You cannot edit a published template — any changes create a new version while the current one continues serving users.

Archived: The template is no longer in active use and cannot be deployed. Existing acceptance records remain accessible.

note

Only Published templates can be deployed.

Deployment Concepts​

Environment: The context a deployment runs in — Production, Staging, or Development. Each environment is fully isolated: sessions and evidence in Staging or Development do not appear in Production. See Environments.

Display mode: How the agreement widget appears to users: modal (centered overlay that blocks the page), inline (embedded directly in your layout), or popup (overlay prompt that doesn't block the page).

Variant: An optional label on a deployment used for A/B testing. Multiple variants can run on the same location at once, each showing a different version of the agreement. Click tracks acceptance rates per variant. See A/B Testing.

Active: A deployment is active when it is live and serving users. Only one deployment can be active per domain, path, and environment at a time. Activating a new deployment at the same location automatically deactivates the previous one.

Priority: When multiple deployments target overlapping paths (for example, one for / and one for /signup), priority controls which one is shown. Higher priority wins.

Session Outcomes​

Accepted: The user confirmed the agreement. An evidence bundle is generated. This outcome cannot be changed.

Declined: The user explicitly rejected the agreement. Only possible if decline is enabled in the template configuration.

Expired: The session window passed before the user responded. The session is preserved for audit purposes.

Evidence Terms​

Receipt: The confirmation your application receives immediately when a user accepts, via the onAccept SDK callback. It contains IDs and a timestamp so your application can record the acceptance in your own database and link it back to Click's evidence records. The receipt arrives right away; the full evidence bundle is assembled seconds later.

Evidence Bundle: The complete compliance record for an acceptance — what the user saw, when they saw it, and verification that the content has not changed. This is what you produce in an audit. See Evidence & Compliance.

PDF Certificate: A human-readable summary of an evidence bundle, generated automatically for every acceptance. Suitable for sharing with legal counsel or auditors who do not have dashboard access.

TermWhen it's createdWhat it containsUse for
ReceiptImmediately on acceptanceIDs, timestamp, statusCross-referencing in your own database
Evidence BundleSeconds after acceptanceFull compliance recordAudits and legal review
PDF CertificateWith the evidence bundleHuman-readable summarySharing with counsel or regulators

Category: A named grouping of data uses that a user can opt into or out of — for example, "Analytics", "Marketing", or "Functional". Each category has a key, a label, and a default state.

ConsentChoice: An individual category decision record. One record is created per category each time a user changes their preference. Old records are never overwritten, so you can reconstruct the full consent history for any user.

UserConsentState: The current snapshot of a user's preferences across all categories. Use this to gate features in real time; use ConsentChoice records for compliance audits.

Re-consent: Prompting a user to accept a new version of an agreement they have already accepted. Triggered when the policy version of a template changes. See Template Versioning for current status.