Integrations

Credentials for external systems. Secrets are encrypted and never shown again.

UTC +00:00
Loading integrations…

Matomo

Matomo is the traffic source: pageviews, visits, visitors and on-site behaviour. Outbound clicks (Click Service) and conversions (Postback) are different sources and are not shown here.

The Matomo URL, Site ID and API token are stored only server-side — never in a template, a release or the frontend. The panel shows whether they are set, never their values.
Loading Matomo status…
Matomo URL
Not available
Matomo Site ID
Not available
API token
Not available

Not a global field: Matomo idsite is created per site automatically (SitesManager.addSite) and kept in the site binding. The list of bindings is below.

Saving credentials is not available in the API yet: the provider “matomo” is not registered in the integrations API, so PUT /integrations/matomo answers 404. Until then the values above show what the analytics layer resolved — environment or database — and no URL or token is displayed.

Tracking reports

Page viewsSessions / visitorsReferrersCampaignsCountries / regionsDevices / browsersInternal site searchDownloadsUX events

The API does not report the enabled tracking set yet, so this is the list SiteForge expects, not checkboxes with made-up state. The real set will come from the API when the backend exposes it.

Matomo sites are created automatically: every SiteForge site gets its own idsite (SitesManager.addSite). The analytics code is placed into published pages of new builds, and Install tracking code backfills it for sites that are already live.

Tracking code

Every SiteForge site gets its own Matomo idsite automatically, and the analytics code is inserted into the published pages when the site is created or published. No site list is needed here: the state of a particular site lives in that site’s card.

Loading tracking state…