How conviva/conviva-js-appanalytics works
Project type and purpose
• This is a client-side JavaScript SDK (an open-source tool/library) named “Conviva JavaScript ECO SDK.”
• Purpose: to be embedded into web applications (MPAs or SPAs) to auto-collect UX and performance events, track custom events, errors, page views, device metadata, and then send that data to the Conviva backend (Pulse).
File structure
• Top-level files only—no “src/” or “lib/” directories:
• conviva-js-appanalytics.js — the compiled SDK bundle (ES5/UMD)
• conviva-js-appanalytics.d.ts — TypeScript definitions
• package.json — SDK metadata, dependencies, build scripts
• README.md, CHANGELOG.md, ConvivaLegalNotice.txt — docs and legal
• There is no “frontend/” or “backend/” directory since this is a library, not an application with UI or server components.
• No tests or examples in this tree, so the focus is purely on the runtime behavior of the distributed bundle.
README for additional insights
• Public API surface: convivaAppTracker(), setUserId(), trackPageView(), trackCustomEvent(), setCustomTags(), unsetCustomTags(), trackError(), getClientId(), setClientId()
• Core modules implied: Initialization & Config, Event Collection (auto-collected and custom), Storage (localStorage + optional cookies), Network (XHR/Fetch), Metadata management, Error handling
• External service: Conviva Pulse backend must be called by the SDK