Analytics Platform Design
This document is the consolidated design for the Percus analytics platform. It covers what we capture, where it lives, how it is queried and reported, the privacy posture, the cost envelope at startup scale, and the compatibility strategy for clients migrating from Individeo.
Athena Query Examples
Ad-hoc and dashboard queries run against the curated zone through the Glue table
Identity Model
Percus analytics never stores viewer PII. Viewers are identified by an
SDK Lazy Load & Consent Gate
The Percus embed SDK ships as two separate bundles so that no tracking code reaches the viewer's page until consent is granted. This is the foundation of the platform's privacy posture (GDPR, Ley 19.628, LGPD): the default is no collection.
Event Transport
How analytics events travel from the Percus Player iframe, through the host SDK, to the ingest endpoint. The path is loss-tolerant, ad-blocker–aware, and gated by consent.