Matomo native, cloud or self-hosted

Matomo·Analytics

matomo on every wordpress site, GDPR friendly.

paste your Matomo instance URL and site ID. the snippet renders gated against analytics consent. works against Matomo Cloud or your own self-hosted instance — no plugin required, no PHP overhead.

Start free trial See pricing

free trial. no credit card. all 30 integrations included on every plan.

includedYovale WordPress Hosting — Matomo

yovale.com/en/integrations/matomo

Matomo · analytics consent

Matomo layers inside every wordpress site.

Matomo is the GDPR-friendly choice when you don't want Google Analytics. The catch: most WordPress hosts add the Matomo plugin which embeds an ENTIRE Matomo install inside your site — slow, vulnerable, hard to update.

save-time validation

URL + site ID regex enforced in dashboard

render-time mirror

same checks re-run in PHP before emission

consent gate

fires only after analytics consent granted

head injection

tracker `<script>` emitted in `wp_head`

Matomo URL + site ID injector

cloud or self-hosted

GDPR-friendly defaults

no Matomo plugin needed

status panel

self-host

your instance or Matomo Cloud

0 plugins

no Matomo plugin needed

GDPR ok

anonymized IPs by default

two boxes, one tracker

WordPress here, Matomo over there.

Matomo plugins embed the entire analytics engine inside WordPress — same database, same PHP runtime. Yovale keeps WordPress thin and points the tracker at your dedicated Matomo instance, wherever it lives.

WP container only renders the tracker — no embedded engine

Matomo Cloud OR self-hosted — both via the URL field

data ownership stays with you, not Google

Yovale WP container

nginx + PHP-FPM

WordPress 6.9

mariadb (WP only)

tracker only

Your Matomo instance

your-instance.matomo.cloud

site_id = 7

anonymize_ip = on

processing + storage here

your servers

POST /matomo.php?idsite=7204 No Content

setup

paste URL + site ID. tracker live.

Yovale validates the Matomo URL and site ID at save. the MU-plugin renders the tracker against your instance, gated by analytics consent.

1
Open Tracking → Analytics
Find Matomo in the tracking panel.
2
Paste your Matomo URL
Format: `your-instance.matomo.cloud` or your self-hosted hostname (no scheme, no path).
3
Paste your site ID
1–8 digit numeric ID from Matomo Admin → Websites.

Matomo

enabled

matomo_url

your-instance.matomo.cloud

site_id

7

two fields: instance hostname (cloud or self-hosted) and the numeric site ID for this WordPress site within Matomo.

why bother

Matomo on your terms — data ownership.

GDPR-friendly defaults

anonymize-IP, DoNotTrack honoring, no third-party data sharing.

Self-host first-class

URL field accepts your own infrastructure — Matomo Cloud isn't required.

No embedded engine

WP renders only the tracker — no Matomo PHP running inside WordPress.

Cloud or own VPS

same install path either way. switch later by editing one URL field.

faq

questions before you switch hosts for Matomo.

Can I use Matomo Cloud with this integration?

Yes. Paste `your-instance.matomo.cloud` as the URL and the site ID from your Matomo dashboard. The integration works identically against Cloud and self-hosted.

Why not use the Matomo for WordPress plugin?

That plugin embeds an entire Matomo install inside WordPress — sharing the database, the PHP runtime, and the security surface. Yovale's approach keeps the tracker thin and runs Matomo wherever you choose.

Does Matomo's IP anonymization still work?

Yes. IP anonymization is a Matomo server-side setting and isn't affected by how the tracker is injected. Set it in Matomo Admin → Privacy.

Can I run Matomo with GA4?

Yes — many EU teams do, with Matomo as the primary system of record and GA4 for benchmarking + Google Ads attribution.

Will the page cache strip Matomo?

No. The script tag is part of the cached HTML. Your Matomo instance handles request processing, which is independent of WordPress page caching.

also in analytics