Analytics & BI
Piwik
SaaS API (REST)
Managed auth, retries, and throttling
Export coverage
Know exactly what Vern pulls before you migrate.
Objects Vern extracts
Vern extracts the full set of queryable Piwik objects (14 total), including: Access Control Actions, Access Control Meta Site Permission User, Apps, Apps Details, Audit Log Entries, Container Settings Settings, Meta Sites, Meta Sites Apps, Meta Sites Apps With Meta Sites, Modules, Tracker Settings, User Groups, Users, and Users Me.
Output schema
Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.
Where it can land
Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another analytics & bi system (Appfigures, Appfollow, Chartmogul) when a user is switching tools.
Source details
Built for the source type shown above, with extractor content refreshed from the collection record.
Managed by Vern
The details you normally have to build yourself.
Authentication
OAuth 2.0 (Authorization Code flow). Your new user authorizes Piwik once during onboarding — their credentials never touch your code. Piwik access tokens are short-lived and refresh tokens roll on the provider's own schedule, so Vern manages the full token lifecycle and refresh and the import never drops midway. See Piwik's authentication guide.
Pagination
Vern detects and handles Piwik's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.
Rate limits and gotchas
Piwik enforces its own API rate limits. Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.
OAuth-based sources expire access tokens frequently and require a working refresh flow — a dropped refresh is the most common cause of a half-finished import. Vern owns the refresh loop so a new user's onboarding completes even on a long extraction.
API quickstart
A cleaner way to extract without rebuilding source-specific plumbing.
View docs
Common questions
Can I keep a user's Piwik data in sync after the first import? Vern supports re-running an import on demand; incremental change tracking depends on what Piwik's API exposes for each object.
Can I move a user from Piwik to Appfigures? Yes — Vern normalizes the Piwik data model into typed tables that map cleanly onto Appfigures and into your own product.
What does it cost to read the Piwik API? Piwik's own API access follows Piwik's pricing/plan; Vern is billed separately per import. Check Piwik's developer docs for their current limits.