Plausible Install / Embed Tag or SDK

Delivery Options to Evaluate

• Summarize which tag managers, CMS injectors, or hard-coded placements are allowed for Plausible.
• Note any governance rules from the client (e.g., consent gating, load order restrictions).
• Track separate installation notes for production versus staging environments.

Tag Manager Deployment

• Identify the container name, workspace, and publish process.
• List required triggers, blocking rules, and variable dependencies.
• Capture how the install is validated (preview mode, network calls, vendor debugger).

Direct Embed or Hard-Coded Scripts

• Document header/footer snippets, script attributes, and asset hosting requirements.
• Include bundling or build-step considerations for frameworks (Next.js, Astro, React Native Web).
• Define ownership for keeping the snippet updated when Plausible releases changes.

Mobile & OTT SDKs

• Track minimum OS versions, dependency managers, and modules that must be enabled.
• Outline initialization parameters, environment flags, and consent prompts.
• Record build verification steps (simulators, TestFlight, internal QA suites).

Server-Side Collection

• Note when server-side forwarding, cloud functions, or edge workers are required.
• List credentials, API endpoints, and transformation logic that broker data into Plausible.
• Capture monitoring hooks (logs, alerts, dashboards) to ensure jobs keep running.

Validation Checklist

• Confirm events, identities, and metadata appear in the Plausible debugger or API explorer.
• Screenshot or export proof of installation for compliance archives.
• Assign remediation owners if blockers or failures are discovered.

Open Decisions & Follow-Ups

• Record outstanding questions about install paths, environments, or deprecated libraries.
• Note upcoming releases that might alter the recommended deployment pattern.